Since a few months I noticed that the manjaro updater (pamac) has gotten very unstable. Usually I start the system update, it begins working and after some time the updater window just disappears without any error.
I know it’s not much to go on, but I don’t even know ho to start debugging this one. There seems to be no trace of an error anywhere. journalctl -b -g pamac comes back without any error.
I’m using Manjaro with KDE.
Please give us some information about your system…
inxi -zv8
would be a good start… and have you tried opening pamac-manager from the CLI, so that when it crashes it reports errors to the CLI.
Open a Terminal and type
pamac-manager
Please post any results using the </> button and pasting the results between the multiple back ticks.
Also, if you are using KDE Plasma, you should be using pamac-gtk3, not pamac-gtk. There are two versions, and pamac-gtk is the gtk4 version.
I recall seeing a few similar reports in recent weeks. While I’m not aware of the specific cause, it’s possible the issue was resolved in a recent update.
Thus the importance of making sure your system has been updated successfully.
To this end, I suggest using pacman in the meantime;
1. Refresh your mirrors (should be performed regularly):
sudo pacman-mirrors --continent
2. Perform the sync/update (using pacman):
sudo pacman -Syu
Use only if you build packages from the AUR:
3. Rebuild any AUR packages used (using pamac):
pamac update --aur
A reboot is preferable dependent upon what was updated.
Please provide the system information previously requested.
Regards.
Have to revive this thread, since the problem still occurs (but it took me some time to catch a crash while remembering to run it from terminal beforehand). Running pamac-manager via terminal only returns:
pamac-manager ✔
(pamac-manager:3302): IBUS-WARNING **: 18:02:58.261: Unable to connect to ibus: The given address is empty
zsh: terminated pamac-manager
(while the IBUS-warning appears right after launching). It seems to be only the GUI that is crashing, because if I re-launch pamac-manager (or any other package manger) it is complaining that anothe rupdate is still running. And on the next day most of the updates are installed.
✔
System:
Kernel: 6.12.37-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
root=/dev/mapper/VolumeGroup-root rw systemd.show_status=1 apparmor=1
security=apparmor udev.log_priority=5 intel_iommu=on
vfio-pci.ids=10de:21c4,10de:1aeb,10de:1aec,10de:1aed kvm.ignore_msrs=1
Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.16.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: H170-PRO v: Rev X.0x
serial: <superuser required> part-nu: SKU uuid: <superuser required>
UEFI: American Megatrends v: 3805 date: 05/16/2018
Battery:
Message: No system battery data found. Is one present?
Memory:
System RAM: total: 64 GiB available: 62.72 GiB used: 10.1 GiB (16.1%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 64 GiB slots: 4 modules: 4 EC: None
max-module-size: 16 GiB note: est.
Device-1: DIMM_A1 type: DDR4 detail: synchronous size: 16 GiB
speed: 2133 MT/s volts: curr: 1 width (bits): data: 64 total: 64
manufacturer: Team Group Inc. part-no: TEAMGROUP-UD4-3000 serial: <filter>
Device-2: DIMM_A2 type: DDR4 detail: synchronous size: 16 GiB
speed: 2133 MT/s volts: curr: 1 width (bits): data: 64 total: 64
manufacturer: Team Group Inc. part-no: TEAMGROUP-UD4-3000 serial: <filter>
Device-3: DIMM_B1 type: DDR4 detail: synchronous size: 16 GiB
speed: 2133 MT/s volts: curr: 1 width (bits): data: 64 total: 64
manufacturer: Team Group Inc. part-no: TEAMGROUP-UD4-3000 serial: <filter>
Device-4: DIMM_B2 type: DDR4 detail: synchronous size: 16 GiB
speed: 2133 MT/s volts: curr: 1 width (bits): data: 64 total: 64
manufacturer: Team Group Inc. part-no: TEAMGROUP-UD4-3000 serial: <filter>
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: model: Intel Core i7-6700 bits: 64 type: MT MCP arch: Skylake-S
gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6
model-id: 0x5E (94) stepping: 3 microcode: 0xF0
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 1000 min/max: 800/4000 scaling: driver: intel_pstate
governor: powersave cores: 1: 1000 2: 1000 3: 1000 4: 1000 5: 1000 6: 1000
7: 1000 8: 1000 bogomips: 54417
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
dtherm dts ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr
mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge
pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good sdbg sep
smap smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic
xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
Vulnerabilities:
Type: gather_data_sampling status: Vulnerable: No microcode
Type: indirect_target_selection status: Not affected
Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional;
RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsa status: Not affected
Type: tsx_async_abort mitigation: TSX disabled
Graphics:
Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: Micro-Star MSI
driver: nvidia v: 575.64.03 non-free: 550-570.xx+ status: current (as of
2025-04; EOL~2026-12-xx) arch: Pascal code: GP10x process: TSMC 16nm
built: 2016-2021 pcie: gen: 3 speed: 8 GT/s lanes: 4 ports: active: none
off: DP-1 empty: HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:1d01
class-ID: 0300
Device-2: NVIDIA TU116 [GeForce GTX 1660 SUPER] vendor: Gigabyte
driver: vfio-pci v: N/A non-free: 550-570.xx+ status: current (as of
2025-04; EOL~2026-12-xx) arch: Turing code: TUxxx process: TSMC 12nm FF
built: 2018-2022 pcie: gen: 3 speed: 8 GT/s lanes: 4 link-max: lanes: 16
bus-ID: 08:00.0 chip-ID: 10de:21c4 class-ID: 0300
Device-3: Microdia USB Live camera driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-9.1.2:7
chip-ID: 0c45:636b class-ID: 0102 serial: <filter>
Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x342mm (23.70x13.46")
s-diag: 692mm (27.26")
Monitor-1: DP-1 mapped: DP-0 note: disabled model: Dell U2713HM
serial: <filter> built: 2013 res: mode: 2560x1440 hz: 60 scale: 100% (1)
dpi: 109 gamma: 1.2 chroma: red: x: 0.655 y: 0.337 green: x: 0.294
y: 0.639 blue: x: 0.145 y: 0.039 white: x: 0.314 y: 0.329
size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9
modes: 2560x1440, 1920x1200, 1920x1080, 1600x1200, 1680x1050, 1280x1024,
1280x800, 1152x864, 1280x720, 1024x768, 800x600, 720x576, 720x480,
640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 575.64.03
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce GT 1030/PCIe/SSE2
memory: 1.95 GiB
API: Vulkan v: 1.4.313 layers: 6 device: 0 type: discrete-gpu
name: NVIDIA GeForce GT 1030 driver: nvidia v: 575.64.03
device-ID: 10de:1d01 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 100 Series/C230 Series Family HD Audio
vendor: ASUSTeK H110I-PLUS driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
chip-ID: 8086:a170 class-ID: 0403
Device-2: NVIDIA GP108 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 4
bus-ID: 01:00.1 chip-ID: 10de:0fb8 class-ID: 0403
Device-3: C-Media CMI8788 [Oxygen HD Audio] vendor: ASUSTeK CMI8786
driver: snd_oxygen v: kernel bus-ID: 03:04.0 chip-ID: 13f6:8788
class-ID: 0401
Device-4: NVIDIA TU116 High Definition Audio vendor: Gigabyte
driver: vfio-pci pcie: speed: Unknown lanes: 63 link-max: gen: 6
speed: 64 GT/s bus-ID: 08:00.1 chip-ID: 10de:1aeb class-ID: 0403
Device-5: Microdia USB Live camera driver: snd-usb-audio,uvcvideo
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-9.1.2:7
chip-ID: 0c45:636b class-ID: 0102 serial: <filter>
API: ALSA v: k6.12.37-1-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
Server-2: JACK v: 1.9.22 status: off tools: N/A
Server-3: PipeWire v: 1.4.6 status: off with: pipewire-media-session
status: active tools: pw-cat,pw-cli
Server-4: PulseAudio v: 17.0-43-g3e2bb status: active
with: pulseaudio-alsa type: plugin tools: pacat,pactl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: ASUSTeK RTL8111H driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: c000 bus-ID: 07:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp7s0 state: up speed: 100 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
IF-ID-1: br0 state: down mac: <filter>
IF-ID-2: virbr0 state: down mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IF-ID-3: virbr1 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IF-ID-4: virbr2 state: up speed: 10000 Mbps duplex: unknown mac: <filter>
IF-ID-5: virbr3 state: down mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IF-ID-6: vnet0 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
IP v6: <filter> virtual: proto kernel_ll scope: link
IF-ID-7: vnet1 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
IP v6: <filter> virtual: proto kernel_ll scope: link
IF-ID-8: vnet2 state: unknown speed: 10000 Mbps duplex: full mac: <filter>
IP v6: <filter> virtual: proto kernel_ll scope: link
Info: services: httpd, NetworkManager, systemd-timesyncd
WAN IP: <filter>
Bluetooth:
Message: No bluetooth data found.
Logical:
Message: Unable to run lvs. Root privileges required.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 9.1 TiB used: 4.4 TiB (48.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST4000DM000-1F2168
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5900 serial: <filter> fw-rev: CC54 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 860 QVO 2TB
size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 1B6Q scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST4000DM000-1F2168
size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: HDD rpm: 5900 serial: <filter> fw-rev: CC54 scheme: GPT
Optical-1: /dev/sr0 vendor: ASUS model: BC-12D2HT rev: 1.00
dev-links: cdrom
Features: speed: 1 multisession: yes audio: yes dvd: yes
rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
ID-1: / raw-size: 180 GiB size: 176.11 GiB (97.84%) used: 93.11 GiB (52.9%)
fs: ext4 dev: /dev/dm-1 maj-min: 254:1 mapped: VolumeGroup-root label: N/A
uuid: N/A
ID-2: /boot/efi raw-size: 401 MiB size: 400.2 MiB (99.79%)
used: 340 KiB (0.1%) fs: vfat dev: /dev/sdb2 maj-min: 8:18 label: N/A
uuid: 7B90-C820
ID-3: /home raw-size: 1.28 TiB size: 1.26 TiB (98.35%)
used: 830.06 GiB (64.4%) fs: ext4 dev: /dev/dm-0 maj-min: 254:0
mapped: VolumeGroup-home label: N/A uuid: N/A
ID-4: /home/<filter>/backups raw-size: 2.31 TiB size: 2.27 TiB (98.39%)
used: 1.83 TiB (80.9%) fs: ext4 dev: /dev/sdc1 maj-min: 8:33 label: Backup
uuid: 6a4a8faf-3b9d-435e-ac58-8f7ad273b102
ID-5: /run/media/VolumeGroups/downloads raw-size: 1.91 TiB
size: 1.88 TiB (98.42%) used: 1.43 TiB (76.1%) fs: ext4 dev: /dev/dm-4
maj-min: 254:4 mapped: VolumeGroup3-downloads label: N/A uuid: N/A
ID-6: /run/media/VolumeGroups/server raw-size: 437.62 GiB
size: 430.56 GiB (98.39%) used: 33.86 GiB (7.9%) fs: ext4 dev: /dev/dm-2
maj-min: 254:2 mapped: VolumeGroup2-server label: N/A uuid: N/A
ID-7: /run/media/VolumeGroups/videos raw-size: 927.73 GiB
size: 912.1 GiB (98.31%) used: 205.59 GiB (22.5%) fs: ext4 dev: /dev/dm-3
maj-min: 254:3 mapped: VolumeGroup2-videos label: N/A uuid: N/A
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: partition size: 24.22 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sdb8 maj-min: 8:24 label: N/A
uuid: 9486fb7e-a0c2-42ae-ba32-171a0c28c293
Unmounted:
ID-1: /dev/sda1 maj-min: 8:1 size: 1.73 TiB fs: ntfs label: Win_Daten
uuid: 5971FDA10442A372
ID-2: /dev/sdb1 maj-min: 8:17 size: 350 MiB fs: ntfs label: Recovery
uuid: C218DCFC18DCF101
ID-3: /dev/sdb6 maj-min: 8:22 size: 348.08 GiB fs: ntfs
label: Win_Programme uuid: 33B0857F0E3DF308
USB:
Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-2: 1-9:2 info: Terminus Hub ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
chip-ID: 1a40:0101 class-ID: 0900
Hub-3: 1-9.1:3 info: Huasheng USB2.0 HUB ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
chip-ID: 214b:7250 class-ID: 0900
Hub-4: 1-9.1.1:5 info: Huasheng USB2.0 HUB ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
chip-ID: 214b:7250 class-ID: 0900
Device-1: 1-9.1.2:7 info: Microdia USB Live camera type: video,audio
driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
chip-ID: 0c45:636b class-ID: 0102 serial: <filter>
Device-2: 1-9.2:4 info: Microdia Foot Switch type: keyboard,mouse
driver: hid-generic,usbhid interfaces: 2 rev: 2.0
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
chip-ID: 0c45:7403 class-ID: 0301
Device-3: 1-9.3:6 info: Microdia Foot Switch type: keyboard,mouse
driver: hid-generic,usbhid interfaces: 2 rev: 2.0
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
chip-ID: 0c45:7403 class-ID: 0301
Hub-5: 2-0:1 info: super-speed hub ports: 8 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-6: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-7: 3-2:2 info: Terminus Hub ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
chip-ID: 1a40:0101 class-ID: 0900
Device-1: 3-2.2:3 info: Microdia Foot Switch type: keyboard,mouse
driver: hid-generic,usbhid interfaces: 2 rev: 2.0
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
chip-ID: 0c45:7403 class-ID: 0301
Device-2: 3-2.3:4 info: Microdia Foot Switch type: keyboard,mouse
driver: hid-generic,usbhid interfaces: 2 rev: 2.0
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 100mA
chip-ID: 0c45:7403 class-ID: 0301
Hub-8: 4-0:1 info: super-speed hub ports: 2 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-9: 5-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-10: 6-0:1 info: super-speed hub ports: 4 rev: 3.1
speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
class-ID: 0900
Sensors:
System Temperatures: cpu: 38.0 C mobo: N/A
Fan Speeds (rpm): N/A
Repos:
Packages: pm: pacman pkgs: 2030 libs: 365 tools: pamac pm: flatpak pkgs: 0
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://mirror.dkm.cz/manjaro/stable/$repo/$arch
2: https://mirror.it4i.cz/manjaro/stable/$repo/$arch
3: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
4: http://mirror.datacenter.by/pub/mirrors/manjaro/stable/$repo/$arch
5: https://mirror.zetup.net/manjaro/stable/$repo/$arch
6: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
7: https://muug.ca/mirror/manjaro/stable/$repo/$arch
8: https://mirrors.jlu.edu.cn/manjaro/stable/$repo/$arch
Processes:
CPU top: 5 of 338
1: cpu: 57.0% command: qemu-system-x86_64 pid: 2767 mem: 3218.5 MiB (5.0%)
2: cpu: 25.5% command: firefox pid: 2250 mem: 722.0 MiB (1.1%)
3: cpu: 11.4% command: qemu-system-x86_64 pid: 1930 mem: 1394.8 MiB (2.1%)
4: cpu: 11.0% command: firefox pid: 4068 mem: 298.1 MiB (0.4%)
5: cpu: 9.8% command: firefox pid: 36709 mem: 277.3 MiB (0.4%)
Memory top: 5 of 338
1: mem: 3218.5 MiB (5.0%) command: qemu-system-x86_64 pid: 2767 cpu: 57.0%
2: mem: 1394.8 MiB (2.1%) command: qemu-system-x86_64 pid: 1930 cpu: 11.4%
3: mem: 722.0 MiB (1.1%) command: firefox pid: 2250 cpu: 25.5%
4: mem: 611.8 MiB (0.9%) command: plasmashell pid: 1698 cpu: 9.2%
5: mem: 380.3 MiB (0.5%) command: firefox pid: 2386 cpu: 1.6%
Info:
Processes: 338 Power: uptime: 30m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 25.06 GiB services: org_kde_powerdevil,upowerd
Init: systemd v: 257 default: graphical tool: systemctl
Compilers: clang: 20.1.7 gcc: 15.1.1 alt: 13/14 Shell: Zsh v: 5.9
default: Bash v: 5.3.0 running-in: konsole inxi: 3.3.38
Could you please provide the output of:
pacman -Qi pamac
Do you also experience this issue when using Wayland?
Name : pamac-gtk
Version : 11.7.3-3
Description : A Package Manager based on libalpm with AUR and Appstream support (GTK4)
Architecture : x86_64
URL : https://github.com/manjaro/pamac
Licenses : GPL-3.0-or-later
Groups : None
Provides : pamac libpamac-gtk.so=libpamac-gtk.so-64
Depends On : archlinux-appstream-data gtk3 gtk4 libadwaita libnotify libpamac>=11.7.0 pamac-cli>=11.7.0
Optional Deps : pamac-gnome-integration: for integration into GNOME
libpamac-flatpak-plugin: for Flatpak support [installed]
libpamac-snap-plugin: for Snap support [installed]
Required By : manjaro-application-utility pamac-tray-icon-plasma
Optional For : None
Conflicts With : pamac-gtk3
Replaces : None
Installed Size : 547,37 KiB
Packager : Philip Mueller <philm@manjaro.org>
Build Date : Do 19 Jun 2025 09:35:26 CEST
Install Date : Di 15 Jul 2025 19:16:20 CEST
Install Reason : Explicitly installed
Install Script : Yes
Validated By : Signature
Haven’t tried it with Wayland yet. Problem is that I always have to wait for some major updates to run one of those experiments. Or can you think of an alternative? Is there some dry-run or something I could try. I would prefer not to constantly meddle with real upgrades - who knows what problems this would bring.
As you are still on Plasma 6.3.6 you should be able to select Wayland when logging in, this option should be displayed at the bottom by your display manager.
pamac-gtk3 usually works better with Plasma, as it does not rely on the Gnome-specific Adwaita libraries. To replace pamac-gtk with pamac-gtk3, run the following command in a terminal:
sudo pacman -Syu pamac-gtk3
This is indeed what I was leading to. Please try as @scotty65 suggests, and report back whether or not the issue remains.
Regards.
Thanks, I’ll try it and report back. Any reason why pamac-gtk3 isn’t included by default with the KDE-Version of Manjaro?
It should be, but I’ve heard from one of the Manjaro packagers that pamac-gtk3 is scheduled to be phased out in favor of pamac-gtk.
One reason for that could be the difference in design, i.e. pamac-gtk uses plugin modules for things like Snaps and FlatPaks, while pamac-gtk3 does not. So apart from the gtk4 user interface, pamac-gtk is of a newer application design and more future-proof.
Back when I installed Manjaro — late in April 2019 — the default graphical package manager in the Plasma edition was actually octopi, which is qt-based, and which is significantly more reliable, as it uses pacman directly in the background, and an AUR helper (if installed) for AUR access. It does however not support Snaps or FlatPaks.
It is included. 
Right. That’s due to upstream phasing out Libsoup and Gtk 3 in favor of Libadwaita and Gtk 4–which pamac-gtk uses.
pamac-gtk3 has been effectively in maintenance mode for quite some time now. It is advised to use pamac-gtk. Reporting issues for either are welcome either way, however keep in mind there is only one developer with limited time.
Having said all that, there’s always…
