Can't load Add/Remove software (pamac)

When I try to load the Add/Remove software app, I get the following err report in a Notification pop-up:

Plasma Desktop Workspace
Launching Add/Remove Software failed
Could not activate remote peer ‘org.manjaro.pamac.manager’:unit failed

The above error message is all I know. This issue has been ongoing for many weeks, or I’d wait for an update to fix the issue. Is there a fix from upstream?

Ernie

Output of garuda-inxi:

System: 
Kernel: 6.18.3-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1 
clocksource: tsc avail: acpi_pm 
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen 
root=UUID=9f9ca6d5-23e0-4c6f-b767-cefe9d263cf0 rw rootflags=subvol=@ 
vt.default_red=30,243,166,249,137,245,148,186,88,243,166,249,137,245,148,166 
vt.default_grn=30,139,227,226,180,194,226,194,91,139,227,226,180,194,226,173 
vt.default_blu=46,168,161,175,250,231,213,222,112,168,161,175,250,231,213,200 
quiet loglevel=3 intel_iommu=on iommu=pt 
Desktop: KDE Plasma v: 6.5.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM 
Distro: Garuda base: Arch Linux 
Machine: 
Type: Laptop System: LENOVO product: 82AU v: Lenovo Legion 5 15IMH05 
serial: <filter> Chassis: type: 10 v: Lenovo Legion 5 15IMH05 
serial: <filter> 
Mobo: LENOVO model: LNVNB161216 v: SDK0R32862 WIN serial: <filter> 
part-nu: LENOVO_MT_82AU_BU_idea_FM_Legion 5 15IMH05 
uuid: 50ef4d03-a18c-11eb-80ef-38f3ab90854a Firmware: UEFI vendor: LENOVO 
v: EFCN59WW date: 06/09/2023 
Battery: 
ID-1: BAT0 charge: 53.8 Wh (95%) condition: 56.7/60 Wh (94.4%) volts: 15.07 
min: 15.4 model: Celxpert L19C4PC0 type: Li-poly serial: <filter> charging: 
status: not charging type: long_life avail: long_life,standard cycles: 19 
CPU: 
Info: model: Intel Core i7-10750H socket: U3E1 bits: 64 type: MT MCP 
arch: Comet Lake gen: core 10 level: v3 note: check built: 2020 
process: Intel 14nm family: 6 model-id: 0xA5 (165) stepping: 2 
microcode: 0x100 
Topology: cpus: 1x dies: 1 clusters: 6 cores: 6 threads: 12 tpc: 2 
smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB 
desc: 6x256 KiB L3: 12 MiB desc: 1x12 MiB 
Speed (MHz): avg: 800 min/max: 800/5000 base/boost: 2475/5000 scaling: 
driver: intel_pstate governor: powersave volts: 0.8 V ext-clock: 100 MHz 
cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 
10: 800 11: 800 12: 800 bogomips: 62399 
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
Vulnerabilities: <filter> 
Graphics: 
Device-1: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] vendor: Lenovo 
driver: nvidia v: 590.48.01 alternate: nouveau,nvidia_drm 
non-free: 550-580.xx+ status: current (as of 2025-11; EOL~2026-12-xx) 
arch: Turing code: TUxxx process: TSMC 12nm FF built: 2018-2022 pcie: 
gen: 3 speed: 8 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1,HDMI-A-1 
bus-ID: 01:00.0 chip-ID: 10de:1f99 class-ID: 0300 
Device-2: EMEET HD Webcam C960 driver: snd-usb-audio,uvcvideo type: USB 
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4:4 chip-ID: 328f:006d 
class-ID: 0102 serial: <filter> 
Device-3: Bison Integrated Camera driver: uvcvideo type: USB rev: 2.0 
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6:6 chip-ID: 5986:2137 
class-ID: 0e02 
Display: unspecified server: X.Org v: 24.1.9 with: Xwayland v: 24.1.9 
compositor: kwin_wayland driver: gpu: nv_platform,nvidia,nvidia-nvswitch 
display-ID: :0 screens: 1 
Screen-1: 0 s-res: 1536x864 s-dpi: 96 s-size: 406x229mm (15.98x9.02") 
s-diag: 466mm (18.35") 
Monitor-1: eDP-1 model: BOE Display 0x0900 built: 2019 res: mode: 1536x864 
hz: 60 scale: 100% (1) dpi: 113 gamma: 1.2 size: 344x194mm (13.54x7.64") 
diag: 395mm (15.5") ratio: 16:9 modes: 1920x1080 
API: EGL v: 1.5 hw: drv: nvidia platforms: gbm: drv: nvidia 
API: OpenGL v: 4.6.0 vendor: nvidia v: 590.48.01 glx-v: 1.4 
direct-render: yes renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2 
memory: 3.91 GiB 
API: Vulkan v: 1.4.335 layers: 8 device: 0 type: discrete-gpu 
name: NVIDIA GeForce GTX 1650 driver: nvidia v: 590.48.01 
device-ID: 10de:1f99 surfaces: N/A device: 1 type: cpu name: llvmpipe 
(LLVM 21.1.6 256 bits) driver: mesa llvmpipe v: 25.3.3-arch1.1 (LLVM 
21.1.6) device-ID: 10005:0000 surfaces: N/A 
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo 
de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info 
x11: xdpyinfo, xprop, xrandr 
Audio: 
Device-1: Intel Comet Lake PCH cAVS vendor: Lenovo driver: snd_hda_intel 
v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 
chip-ID: 8086:06c8 class-ID: 0403 
Device-2: NVIDIA vendor: Lenovo driver: snd_hda_intel v: kernel pcie: 
gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:10fa 
class-ID: 0403 
Device-3: EMEET HD Webcam C960 driver: snd-usb-audio,uvcvideo type: USB 
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4:4 chip-ID: 328f:006d 
class-ID: 0102 serial: <filter> 
API: ALSA v: k6.18.3-zen1-1-zen status: kernel-api tools: N/A 
Server-1: PipeWire v: 1.4.9 status: n/a (root, process) with: 
1: pipewire-pulse status: active 2: wireplumber status: active 
3: pipewire-alsa type: plugin 4: pw-jack type: plugin 
tools: pactl,pw-cat,pw-cli,wpctl 
Network: 
Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel 
bus-ID: 00:14.3 chip-ID: 8086:06f0 class-ID: 0280 
IF: wlp0s20f3 state: up mac: <filter> 
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet 
vendor: Lenovo driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 
port: 3000 bus-ID: 07:00.0 chip-ID: 10ec:8168 class-ID: 0200 
IF: enp7s0 state: down mac: <filter> 
Device-3: Realtek 802.11ax WLAN Adapter driver: N/A type: USB rev: 2.0 
speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.1:5 chip-ID: 0bda:b832 
class-ID: 0000 serial: <filter> 
IF-ID-1: virbr0 state: down mac: <filter> 
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant 
Bluetooth: 
Device-1: Intel AX201 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0 
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:9 chip-ID: 8087:0026 
class-ID: e001 
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.2 
lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c010c 
Drives: 
Local Storage: total: 2.4 TiB used: 184.74 GiB (7.5%) 
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix 
model: HFM512GDHTNI-87A0B size: 476.94 GiB block-size: physical: 512 B 
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter> 
fw-rev: 11020C00 temp: 35.9 C scheme: GPT 
SMART: yes health: PASSED on: 283d 3h cycles: 12,559 
read-units: 360,137,412 [184 TB] written-units: 106,006,960 [54.2 TB] 
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital 
model: WD20SDZW-11JJ8S0 size: 1.82 TiB block-size: physical: 4096 B 
logical: 512 B type: USB rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 
sata: 3.1 speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter> 
fw-rev: 1026 drive-rev: 01.01A01 temp: 34 C scheme: MBR 
SMART: yes state: enabled health: PASSED on: 4y 3d 7h cycles: 14015 
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: Flash Drive FIT 
size: 119.51 GiB block-size: physical: 512 B logical: 512 B type: USB 
rev: 3.1 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: SSD serial: <filter> 
fw-rev: 1100 scheme: MBR 
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
Partition: 
ID-1: / raw-size: 137.47 GiB size: 137.47 GiB (100.00%) 
used: 21.34 GiB (15.5%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p5 
maj-min: 259:5 
ID-2: /boot/efi raw-size: 2 GiB size: 2 GiB (99.80%) used: 39.3 MiB (1.9%) 
fs: vfat block-size: 512 B dev: /dev/nvme0n1p1 maj-min: 259:1 
ID-3: /home raw-size: 100 GiB size: 100 GiB (100.00%) 
used: 81.07 GiB (81.1%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p6 
maj-min: 259:6 
ID-4: /var/log raw-size: 137.47 GiB size: 137.47 GiB (100.00%) 
used: 21.34 GiB (15.5%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p5 
maj-min: 259:5 
ID-5: /var/tmp raw-size: 137.47 GiB size: 137.47 GiB (100.00%) 
used: 21.34 GiB (15.5%) fs: btrfs block-size: 4096 B dev: /dev/nvme0n1p5 
maj-min: 259:5 
Swap: 
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no 
ID-1: swap-1 type: zram size: 31.25 GiB used: 0 KiB (0.0%) priority: 100 
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0 
Sensors: 
System Temperatures: cpu: 41.0 C pch: 43.0 C mobo: N/A 
Fan Speeds (rpm): N/A 
Info: 
Memory: total: 32 GiB available: 31.25 GiB used: 3.92 GiB (12.6%) 
Processes: 390 Power: uptime: 2h 34m states: freeze,mem,disk suspend: deep 
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot, 
suspend, test_resume image: 12.45 GiB services: org_kde_powerdevil, 
power-profiles-daemon, upowerd Init: systemd v: 259 default: graphical 
tool: systemctl 
Packages: 1664 pm: pacman pkgs: 1657 libs: 397 tools: octopi,pamac,paru 
pm: flatpak pkgs: 7 Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Bash (sudo) 
v: 5.3.9 running-in: konsole inxi: 3.3.40 
Garuda (2.11.1-1): 
System install date:     2025-11-30 
Garuda release:          251002 
Last full system update: 2026-01-07 ↻ 
Is partially upgraded:   No 
Relevant software:       snapper NetworkManager dracut nvidia-utils nvidia-open-dkms garuda-hardware-profile
-nvidia garuda-hardware-profile-standard garuda-hardware-profile-standard-x11 
Windows dual boot:       Yes 
Failed units: 
--- System Health Check Report --- 
26/26 checks run in 0.80 seconds ⌛  
Powered by garuda-health 🦅e 
 
--- INFO --- 
- A reboot is pending (update applied since last reboot) 
 
✅ System health check passed. No issues found.



Hi, don’t sign all your posts, please. Keep it tidy.
Garuda advises against using pamac. Just remove it.

6 Likes

Hi Ernie.

As @SGS has already mentioned, Garuda advises against using pamac.

If you absolutely require a graphical software center, then Octopi or Bauh would perhaps be options you may want to look at instead. Garuda highly discourages the use of graphical package managers for performing system updates. If you insist on using a graphical package manager, then it should only be used for package browsing.

Pacseek is another good option if you can get more comfortable using the terminal.

Using garuda-update through Rani or the terminal is the recommended method for performing system updates.

5 Likes

It’s not that I need pamac so much as it is that I’m comfortable using it to search for any apps I want to find. I’ve tried using Octopi, but it simply confuses me.

OK, I just think that if I put my name to whatever I post, it’s like I’m taking responsibility, but I’ll stop doing that here

Then this recommendation raises the question “Why is pamac in the Chaotic-AUR repository, which is supported/managed my Garuda then?”

I suspect multiple distributions use the Chaotic-AUR repo. Just because it’s in a repo that Garuda folks maintain, doesn’t mean that everything in that repo belongs on a Garuda system. That said, while it is discouraged to use pamac due to all sorts of legitimate reasons, you can still use it - at your own risk. For a less risky alternative, I’d suggest pacseek in your terminal if you wish to look up packages - it’s fairly simple to use and easy to understand/navigate - it’s just not a GUI, but a TUI and will need to be run in a terminal.

I agree that Octopi’s UI leaves a lot to be desired, but it’s decent enough in at least looking up packages, if you really wish to use a GUI. Bauh is also pretty decent.

5 Likes

Chaotic-AUR is not a Garuda project itself, but given a lot of maintainers are in both projects, and infra is shared.. it might seem so at first. Chaotic-AUR is essentially just a binary repository for AUR packages for everyone to use :grin:

6 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.