Plasma crash-restart loop on login after update

Hi good people:

One of the following package upgrades causes Plasma to get into a crash-restart loop on login:

bluez-git 1:5.64.r145.g7f92f75e8-1 -> 1:5.64.r147.g65f7faf5a-1
kaccounts-integration-git 20.12.0_r1260.g722c934-1 -> 20.12.0_r1261.gf26f043-1
kconfig-git 5.96.0_r960.ga83e1f50-1 -> 5.96.0_r961.g5ce3f9eb-1
kcoreaddons-git 5.96.0_r1509.gdfcfb606-1 -> 5.96.0_r1510.g4e944878-1 ⬅️(I suspect this one)🟠
kio-git 5.96.0_r5511.g5936ee748-1 -> 5.96.0_r5514.g6d47b5869-1
knewstuff-git 5.96.0_r1357.g6b109259-1 -> 5.96.0_r1358.g5278e9be-1
kparts-git 5.96.0_r588.gbab4543-1 -> 5.96.0_r589.g86b6137-1
kwallet-git 5.96.0_r1153.ge70f9f2-1 -> 5.96.0_r1154.g9c84b47-1

(All the GIT packages are from chaotic-aur)

I am hoping someone can give a little guidance as to figuring which, and maybe a what to do about it.

inxi Output

Kernel: 5.18.6-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.1.0
Desktop: KDE Plasma v: 5.25.1 Distro: Garuda Linux base: Arch Linux
Type: Desktop System: ASUS product: N/A v: N/A serial:
Mobo: ASUSTeK model: PRIME Z390-A v: Rev 1.xx
serial: UEFI: American Megatrends v: 1802
date: 12/01/2020
Info: 6-core model: Intel Core i7-8700K bits: 64 type: MT MCP
arch: Coffee Lake rev: A cache: L1: 384 KiB L2: 1.5 MiB L3: 12 MiB
Speed (MHz): avg: 4243 high: 4495 min/max: 800/4700 cores: 1: 4414
2: 4379 3: 4317 4: 4352 5: 4184 6: 4495 7: 4438 8: 4274 9: 3845 10: 3999
11: 4316 12: 3904 bogomips: 88796
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen9.5 bus-ID: 00:02.0
Device-2: AMD Vega 10 XL/XT [Radeon RX 56/64] vendor: Micro-Star MSI
driver: amdgpu v: kernel arch: GCN 5 bus-ID: 03:00.0
Display: x11 server: X.Org v: 21.1.3 with: Xwayland v: 22.1.2 driver: X:
loaded: amdgpu,intel unloaded: modesetting gpu: amdgpu,i915 resolution:
1: 1920x1080 2: 1920x1080 3: N/A
renderer: AMD Radeon RX Vega (vega10 LLVM 13.0.1 DRM 3.46 5.18.6-zen1-1-zen)
v: 4.6 Mesa 22.1.2 direct render: Yes
Device-1: Intel Cannon Lake PCH cAVS vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 1-6.2:6 bus-ID: 00:1f.3
Device-2: AMD Vega 10 HDMI Audio [Radeon 56/64] driver: snd_hda_intel
v: kernel bus-ID: 03:00.1
Device-3: C-Media Audio Adapter (Unitek Y-247A) type: USB
driver: cmedia_hs100b,snd-usb-audio,usbhid
Sound Server-1: ALSA v: k5.18.6-zen1-1-zen running: yes
Sound Server-2: JACK v: 1.9.21 running: no
Sound Server-3: PulseAudio v: 16.1 running: yes
Sound Server-4: PipeWire v: 0.3.52 running: yes
Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
port: N/A bus-ID: 00:1f.6
IF: eno1 state: up speed: 1000 Mbps duplex: full mac:
Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8
bus-ID: 1-3:4
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address:
Local Storage: total: 1.59 TiB used: 348.98 GiB (21.4%)
ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP500 size: 111.79 GiB
temp: 50.9 C
ID-2: /dev/nvme1n1 vendor: Sabrent model: N/A size: 476.94 GiB
temp: 32.9 C
ID-3: /dev/sda vendor: Western Digital model: WD10EZEX-08WN4A0
size: 931.51 GiB
ID-4: /dev/sdb vendor: A-Data model: SU650 size: 111.79 GiB
ID-1: / size: 35 GiB used: 18.79 GiB (53.7%) fs: btrfs dev: /dev/nvme0n1p2
ID-2: /boot/efi size: 974.1 MiB used: 584 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1
ID-3: /home size: 466.94 GiB used: 101.29 GiB (21.7%) fs: btrfs
dev: /dev/nvme1n1p1
ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) dev: /dev/sdb1
System Temperatures: cpu: 34.0 C mobo: N/A gpu: amdgpu temp: 37.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 1626
Processes: 373 Uptime: 9m Memory: 15.47 GiB used: 3.06 GiB (19.8%)
Init: systemd Compilers: gcc: 12.1.0 clang: 13.0.1 Packages: 1770
Shell: Zsh v: 5.9 inxi: 3.3.19

Can you provide your


Instead of your inxi output

Did you update with


1 Like

No such package. This install is several yeas old. (Stat says: 2020-07-28)


When was the last time it was updated???? its a rolling release

1 Like

What is with the excess of question marks?

I update roughly once every other day.

If "garuda-inxi" is an alias, that doesn't get updated. Tell me what it's aliased to and I will gladly run that to get the info you need.

New packages, not replacing old ones, as garuda-update likely is, don't get installed.

Surely you know this? Surely you are not suggesting I am this ignorant of Garuda? I fled this board quite some time ago because I was looked down on for needing help now and again, despite being able to help others. Has nothing improved?

This is so frustrating. All I hoped for was a little help figuring out what package had the crash. Maybe get lucky and find someone's already been through this and has a solution.

sudo pacman -Syu garuda-update
1 Like

What have you tried so far?
Have you ignored packages to see after update which one it is?

Doesn't have anything to install, seems to be a meta-package in support of an alias.

I am currently updating one package at a time. It's rather time consuming and tedious, which is why I hoped for a better way.

Install garuda-common-settings

1 Like

Should be part of garuda-common-settings :thinking:

According to kernel and kde version it's recent :slight_smile:

I'm also on KDE-git, updating daily and I'm not facing crashes. What makes you think it's that rather than something else? :eyes:
Maybe also observe journalctl from another tty for further insight. Often errors also get displayed there :slight_smile:


It wasn't a big update, none of the other stuff that got updated runs at login, so…

No idea why I didn't think of doing this. Thank you! (Probably because Garuda is such a rock of stability that my diagnosis skills are decaying.)


For garuda-common-settings, no packages match search.


HoldPkg      = pacman glibc garuda-system
Include = /etc/pacman.d/chaotic-mirrorlist

BIG thank you for this.

Why this, please?

IDK, sorry, i trust the garuda developers and thought it was relevant :slight_smile:

HoldPkg = package … If a user tries to --remove a package that's listed in HoldPkg, pacman will ask for confirmation before proceeding.

1 Like

I can't remember or simply don't know how to update signatures for this repo :crying_cat_face:
(I am looking this up on this forum because of course :smiley_cat:)

1 Like

pacman -Syu chaotic-keyring should do the trick :slight_smile:

Nice to see you back btw! :penguin:


OK this has uncovered much.

I have apparently mangled my plasma install. It's part mainstream, part git.
Garuda has changed a lot since I last looked. It may be in my best interests to install fresh from the most recent image - which would fix the above, too (albeit in the nuclear option kind of way)

One more try at isolating the problem, and if no success then I take my computer outside and set it ablaze. I mean… plan on a fresh install.


Welp, reinstall it is.

1 Like