Pacman Problem - Pamac too

error: Failed to execute pacman-conf: error: config file /etc/pacman.conf, line 35: invalid value for 'ParallelDownloads' : '5 <== This fella here is apparently the problem. But its under the options section.'
error parsing '/etc/pacman.conf'

Any idea how to fix this issue ?

2nd issue: i still can not launch Garuda Boot-options. Not meaning grub this works i mean the tool in the OS !

What is pacman-conf ?

2 Likes

i solved it now i made a # at "maximal downloads 5 " and it works !

Garuda boot options i mean not Grub i mean the tool in Garuda which is not working.

Start it from terminal and post what the output comes.

pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY HOME=$HOME garuda-boot-options -style kvantum
2 Likes

It launches from commandline but requires now sudo. It works. But it does not works when i call it from menue then i enter my password and it does not apear.

Copy this and paste in terminal.

Note

Whenever you are asked to launch a GUI application from terminal, you should look the appropriate .desktop file for Exec menu. This depends on the DE you're using, most likely you can right-click on the app in application menu and then chose "Edit Application..." or something.

And also post the output of inxi -Faz.

2 Likes

Please edit this post and add "~~~" above and below the output, to make it easier to read.

What about this?

1 Like

there it opens !

I think you should reboot your PC once and then try again. If it opens from terminal it should also open from desktop icon too. I'm not using XFCE, so not sure much about how it handles.

i rebooted several times - because there is also linux-lts 510.x not working but linux amd 5.12.10 is working fine. I just compiled the kernel 5.12.11 and will reboot soon and report you.

Before that, change your text as you were asked. Please :slight_smile:

What!!

3 Likes

Also reboot did not help. @SGS what do you mean ?

inxi -Faz
System:
Kernel: 5.12.10-AMD x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-amd
root=UUID=8ec56438-695c-4eae-9826-03cc1c9b63ca rw [email protected]
cryptdevice=UUID=eca22f66-1c08-4587-8830-078cea0cda44:luks-eca22f66-1c08-4587-8830-078cea0cda44
root=/dev/mapper/luks-eca22f66-1c08-4587-8830-078cea0cda44 splash
rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1
resume=/dev/mapper/luks-e477e418-9e35-4dec-bf77-e59036af670f loglevel=3
Desktop: Xfce 4.16.0 tk: Gtk 3.24.29 info: xfce4-panel wm: xfwm4 vt: 7
dm: LightDM 1.30.0 Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: MAG B550 TOMAHAWK (MS-7C91) v: 2.0
serial: UEFI: American Megatrends LLC. v: A.61 date: 02/26/2021
CPU:
Info: 6-Core model: AMD Ryzen 5 PRO 4650G with Radeon Graphics bits: 64
type: MT MCP arch: Zen 2 family: 17 (23) model-id: 60 (96) stepping: 1
microcode: 8600106 cache: L2: 3 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 88662
Speed: 3774 MHz min/max: 1400/3700 MHz boost: enabled Core speeds (MHz):
1: 3774 2: 3783 3: 4184 4: 2888 5: 3748 6: 3849 7: 3863 8: 3692 9: 3952
10: 3329 11: 3673 12: 4044
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Renoir driver: amdgpu v: kernel bus-ID: 30:00.0
chip-ID: 1002:1636 class-ID: 0300
Device-2: Microdia Webcam Vitade AF type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 5-1:2 chip-ID: 0c45:6366
class-ID: 0102 serial:
Display: x11 server: [X.Org](http://X.Org) 1.20.11 driver: loaded: amdgpu,ati
unloaded: modesetting alternate: fbdev,vesa display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 3600x1200 s-dpi: 96 s-size: 952x317mm (37.5x12.5")
s-diag: 1003mm (39.5")
Monitor-1: HDMI-A-0 res: 1680x1050 hz: 60 dpi: 90
size: 474x297mm (18.7x11.7") diag: 559mm (22")
Monitor-2: DisplayPort-0 res: 1920x1200 hz: 60 dpi: 94
size: 518x324mm (20.4x12.8") diag: 611mm (24.1")
OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.12.10-AMD LLVM 12.0.0)
v: 4.6 Mesa 21.1.2 direct render: Yes
Audio:
Device-1: AMD driver: snd_hda_intel v: kernel bus-ID: 30:00.1
chip-ID: 1002:1637 class-ID: 0403
Device-2: AMD Family 17h HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 30:00.6 chip-ID: 1022:15e3
class-ID: 0403
Device-3: Microdia Webcam Vitade AF type: USB
driver: snd-usb-audio,uvcvideo bus-ID: 5-1:2 chip-ID: 0c45:6366
class-ID: 0102 serial:
Sound Server-1: ALSA v: k5.12.10-AMD running: yes
Sound Server-2: JACK v: 0.125.0 running: no
Sound Server-3: PulseAudio v: 14.2 running: yes
Sound Server-4: PipeWire v: 0.3.30 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel port: e000 bus-ID: 21:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: enp33s0 state: down mac:
Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
v: kernel port: d000 bus-ID: 2a:00.0 chip-ID: 10ec:8125 class-ID: 0200
IF: enp42s0 state: up speed: 1000 Mbps duplex: full mac:
Drives:
Local Storage: total: 10.94 TiB used: 265.37 GiB (2.4%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Gigabyte
model: GP-GSM2NE3100TNTD size: 953.87 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial:
rev: EDFM00.5 scheme: GPT
ID-2: /dev/sda maj-min: 8:0 type: USB model: QPXT U3 Quickport XT USB3
size: 2.73 TiB block-size: physical: 4096 B logical: 512 B
serial: rev: 8104 scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 type: USB vendor: Western Digital
model: WD Elements 25A3 size: 7.28 TiB block-size: physical: 4096 B
logical: 512 B serial: rev: 1030 scheme: GPT
Partition:
ID-1: / raw-size: 921.27 GiB size: 921.27 GiB (100.00%)
used: 265.37 GiB (28.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-eca22f66-1c08-4587-8830-078cea0cda44
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
used: 682 KiB (0.3%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 921.27 GiB size: 921.27 GiB (100.00%)
used: 265.37 GiB (28.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-eca22f66-1c08-4587-8830-078cea0cda44
ID-4: /var/log raw-size: 921.27 GiB size: 921.27 GiB (100.00%)
used: 265.37 GiB (28.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-eca22f66-1c08-4587-8830-078cea0cda44
ID-5: /var/tmp raw-size: 921.27 GiB size: 921.27 GiB (100.00%)
used: 265.37 GiB (28.8%) fs: btrfs dev: /dev/dm-0 maj-min: 254:0
mapped: luks-eca22f66-1c08-4587-8830-078cea0cda44
Swap:
Kernel: swappiness: 10 (default 60) cache-pressure: 75 (default 100)
ID-1: swap-1 type: partition size: 32.33 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/dm-1 maj-min: 254:1
mapped: luks-e477e418-9e35-4dec-bf77-e59036af670f
ID-2: swap-2 type: zram size: 2.28 GiB used: 0 KiB (0.0%) priority: 32767
dev: /dev/zram0
ID-3: swap-3 type: zram size: 2.28 GiB used: 0 KiB (0.0%) priority: 32767
dev: /dev/zram1
ID-4: swap-4 type: zram size: 2.28 GiB used: 0 KiB (0.0%) priority: 32767
dev: /dev/zram2
ID-5: swap-5 type: zram size: 2.28 GiB used: 0 KiB (0.0%) priority: 32767
dev: /dev/zram3
ID-6: swap-6 type: zram size: 2.28 GiB used: 0 KiB (0.0%) priority: 32767
dev: /dev/zram4
ID-7: swap-7 type: zram size: 2.28 GiB used: 0 KiB (0.0%) priority: 32767
dev: /dev/zram5
ID-8: swap-8 type: zram size: 2.28 GiB used: 0 KiB (0.0%) priority: 32767
dev: /dev/zram6
ID-9: swap-9 type: zram size: 2.28 GiB used: 0 KiB (0.0%) priority: 32767
dev: /dev/zram7
ID-10: swap-10 type: zram size: 2.28 GiB used: 0 KiB (0.0%)
priority: 32767 dev: /dev/zram8
ID-11: swap-11 type: zram size: 2.28 GiB used: 0 KiB (0.0%)
priority: 32767 dev: /dev/zram9
ID-12: swap-12 type: zram size: 2.28 GiB used: 0 KiB (0.0%)
priority: 32767 dev: /dev/zram10
ID-13: swap-13 type: zram size: 2.28 GiB used: 0 KiB (0.0%)
priority: 32767 dev: /dev/zram11
Sensors:
System Temperatures: cpu: 67.9 C mobo: 0 C gpu: amdgpu temp: 46.0 C
Fan Speeds (RPM): fan-1: 2230 fan-2: 0 fan-3: 0 fan-4: 0 fan-5: 0 fan-6: 0
fan-7: 0 fan-8: 0 fan-9: 0 fan-10: 0
Info:
Processes: 387 Uptime: 5h 45m wakeups: 0 Memory: 27.32 GiB
used: 6.59 GiB (24.1%) Init: systemd v: 248 tool: systemctl Compilers:
gcc: 11.1.0 clang: 12.0.0 Packages: pacman: 1659 lib: 502 Shell: Bash
v: 5.1.8 running-in: xfce4-terminal inxi: 3.3.04

Edit your Post!

You broke it you fix it.

1 Like

The fact that garuda boot options do not work did not me break.

I do not know how to change this into that this looks like this - and when i think so close when i would not have new hardware i very fast had installed my long years used Distro linux Mint where all works.
But sadly i had to change my favorite Distro due to hardware changes and i have been using Garuda XFCE since march and i was quiet happy with it until there was the issue starting with problems with pamac, now boot options do not work and now i am blamed that it is my fault...... just by the fact i found a workaround for pamac in manjaro forum.
And yes Manjaro i tried also some years ago it had terrible problems after each update so that i banned it.
I hoped that Garuda is a bit more stable when it comes to an update.

What he means is probably this:

You saw it coming @petsam :crazy_face:

4 Likes

pamac i could fix already this was realy my fault probaly but it was easy to fix. I ask more about this " boot option tool " which works when i call it from command line but not when i call it in menue.

This is off-topic here in this thread.

Garuda is stable, use last snapshot if some apps failed.
Wait until it is fixed.


Soon Garuda is to blame for everything that goes wrong in the world because the news about it appears in the browser that Garuda has made available.

3 Likes

okay i wait :slight_smile:

Yes it is stable and yes i was realy exited i use it in the begin of march with almost zero issues.
Just now there was a problem with pamac and this i found just out by the fact that i did not recieve updates what wondered me. Because i was used to it that pamac apears with his blue bubble as every day almost.
I see this incident as very critical because security updates are very important nowdays.