Arch Linux

Moonveil

Member

Registered: 2025-08-26

Posts: 35

Re: [SOLVED] Cant start KDE-wayland anymore after update

pacman -U https://archive.archlinux.org/packages/s/systemd/systemd-257.9-1-x86_64.pkg.tar.zst https://archive.archlinux.org/packages/s/systemd-libs/systemd-libs-257.9-1-x86_64.pkg.tar.zst

 Warning: downgrading package systemd (258-2 => 257.9-1)
Warning: downgrading package systemd-libs (258-2 => 257.9-1)
Resolving dependencies...
Looking for conflicting packages...
Error: failed to prepare transaction (could not be satisfy dependencies)
:: installing systemd (257.9-1) breaks dependency 'systemd=258' required by systemd-sysvcompat

I don't remember an available update of systemd in the last few days before the system broke down. I don't know if it will resolve anything but I can try.

Though even the fact that you *have* to enable apparmor to be able to boot at all makes the problem to be more likely around that.

I don't know what's wrong with that either, I installed it the way the wiki tells you to. The only change I made is that I downloaded the AUR for apparmor.d which contains extra profiles but I did that weeks ago and everything is still in complain mode.

Edit: I tried disabling the apparmor.service again and rebooted. I did get into sddm but was locked out of the tty because it likely did not load. I had to chroot from the iso to turn it back on and now I'm able to get into tty again but the system is still broken.

Last edited by Moonveil (2025-09-21 10:58:56)

Moonveil

Member

Registered: 2025-08-26

Posts: 35

Re: [SOLVED] Cant start KDE-wayland anymore after update

I'm able to get into KDE again! The problem was caused by apparmor profiles as you suspected. I think that somehow the AUR package of apparmor.d got corrupted or that a configuration was overwritten. I don't know how healthy my system is now but I did get into KDE.

yay -S apparmor.d-git

Then I rebuilt the package with the latest commit. It had one conflicting package, I think it was named just-go but I'm not sure. I ignored the conflict and built the package with the latest git comment and rebooted. Afterwards I was able to get into KDE through SDDM.

Should I check anything else to make sure my system is healthy and won't break again?

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 69,138

Re: [SOLVED] Cant start KDE-wayland anymore after update

\o/
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

In general, you're required to update/maintain all AUR packages yourself, also such AUR packages w/ wide ranging impact would also always be the primary suspects if things go south after an update.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Moonveil

Member

Registered: 2025-08-26

Posts: 35

Re: [SOLVED] Cant start KDE-wayland anymore after update

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

I will marked it as resolved now if there is nothing else that I need to do. Thanks for your help and hopefully someone with the same problem will find a quick solution because of this

In general, you're required to update/maintain all AUR packages yourself, also such AUR packages w/ wide ranging impact would also always be the primary suspects if things go south after an update.

Yes, I check yay -S for updates often and that does pick up Brave and mullvad but it is odd that it did not pick up on this package and that nothing notified me of it breaking.