[SOLVED] Cant start KDE-wayland anymore after update

Moonveil · 2025-09-20 19:48:29

Yesterday everything worked flawless and updated my device but today I booted up but I can't start from SDDM or through tty at all. I tried everything I could think of, searched online, tried various solutions and I even reinstalled KDE but nothing helps. I use AMD not nvidia. When I try to start from SDDM the screen flashes and returns me to the SDDM. If I start from tty with startplasma-wayland it says:

org.kde.startup: "kdeinit5_shutdown" Qlist() exited with code 255
startplasma-wayland: Shutting down
startplasmacompositor: Shutting down
startplasmacompositor: Done

I have no access to any desktop environment. I have to use the forum on my phone. Please help me, I don't know what to do anymore and I have no idea how I could fix this

Last edited by Moonveil (2025-09-21 12:55:24)

arojas · 2025-09-20 20:22:30

Post the jounal logs during the failed login

Moonveil · 2025-09-20 20:32:50

arojas wrote:

Post the jounal logs during the failed login

Do you want them from a SDDM or startplasma-wayland
How can I upload those? I have internet in terminal

--- Already found and a way to upload logs

Last edited by Moonveil (2025-09-20 20:56:16)

Moonveil · 2025-09-20 20:55:24

I made a log trying both startplasmawayland and SDDM login https://0x0.st/KTkY.txt

seth · 2025-09-20 21:40:10

Sep 20 22:51:45 winstation-arch kwin_wayland[30040]: kwin_wayland_drm: No suitable DRM devices have been found
Sep 20 22:51:45 winstation-arch kwin_wayland[30040]: QThreadStorage: entry 8 destroyed before end of thread 0x5637a1a0a7e0
Sep 20 22:51:45 winstation-arch kwin_wayland[30040]: QThreadStorage: entry 1 destroyed before end of thread 0x5637a1a0a7e0
Sep 20 22:51:45 winstation-arch kwin_wayland[30040]: QThreadStorage: entry 0 destroyed before end of thread 0x5637a1a0a7e0
Sep 20 22:51:46 winstation-arch kwin_wayland[30043]: No backend specified, automatically choosing drm
Sep 20 22:51:46 winstation-arch kwin_wayland[30043]: kwin_core: Failed to activate /org/freedesktop/login1/session/_34 session. Maybe another compositor is running?
Sep 20 22:51:46 winstation-arch kwin_wayland[30043]: kwin_wayland_drm: failed to open drm device at "/dev/dri/card1"
Sep 20 22:51:46 winstation-arch kwin_wayland[30043]: kwin_wayland_drm: No suitable DRM devices have been found
Sep 20 22:51:46 winstation-arch kwin_wayland[30043]: QThreadStorage: entry 8 destroyed before end of thread 0x564f3fa407e0
Sep 20 22:51:46 winstation-arch kwin_wayland[30043]: QThreadStorage: entry 1 destroyed before end of thread 0x564f3fa407e0
Sep 20 22:51:46 winstation-arch kwin_wayland[30043]: QThreadStorage: entry 0 destroyed before end of thread 0x564f3fa407e0
Sep 20 22:51:46 winstation-arch systemd[2889]: plasma-kwin_wayland.service: Consumed 1.413s CPU time, 12.3M memory peak.
Sep 20 22:51:46 winstation-arch systemd[2889]: Requested transaction contradicts existing jobs: Transaction for plasma-workspace.target/stop is destructive (plasma-workspace-wayland.target has 'start' job queued, but 'stop' is included in transaction).
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: qt.qpa.wayland: "wl-shell" is a deprecated shell extension, prefer using "xdg-shell" if supported by the compositor by setting the environment variable QT_WAYLAND_SHELL_INTEGRATION
Sep 20 22:51:46 winstation-arch ksplashqml[30005]: qt.qpa.wayland: "wl-shell" is a deprecated shell extension, prefer using "xdg-shell" if supported by the compositor by setting the environment variable QT_WAYLAND_SHELL_INTEGRATION
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: qt.qpa.wayland: Loading shell integration failed.
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: qt.qpa.wayland: Attempted to load the following shells QList("xdg-shell", "wl-shell", "ivi-shell", "qt-shell")
Sep 20 22:51:46 winstation-arch ksplashqml[30005]: qt.qpa.wayland: Loading shell integration failed.
Sep 20 22:51:46 winstation-arch ksplashqml[30005]: qt.qpa.wayland: Attempted to load the following shells QList("xdg-shell", "wl-shell", "ivi-shell", "qt-shell")
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Sep 20 22:51:46 winstation-arch ksplashqml[30005]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: qt.qpa.xcb: could not connect to display :1
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

But this looks recursive, do you try to autostart KDE in your bashrc or something like that?
Can you log in w/ a fresh user account?
https://wiki.archlinux.org/title/Users_ … management

Moonveil · 2025-09-20 22:04:48

seth wrote:

Sep 20 22:51:45 winstation-arch kwin_wayland[30040]: kwin_wayland_drm: No suitable DRM devices have been found
Sep 20 22:51:45 winstation-arch kwin_wayland[30040]: QThreadStorage: entry 8 destroyed before end of thread 0x5637a1a0a7e0
Sep 20 22:51:45 winstation-arch kwin_wayland[30040]: QThreadStorage: entry 1 destroyed before end of thread 0x5637a1a0a7e0
Sep 20 22:51:45 winstation-arch kwin_wayland[30040]: QThreadStorage: entry 0 destroyed before end of thread 0x5637a1a0a7e0
Sep 20 22:51:46 winstation-arch kwin_wayland[30043]: No backend specified, automatically choosing drm
Sep 20 22:51:46 winstation-arch kwin_wayland[30043]: kwin_core: Failed to activate /org/freedesktop/login1/session/_34 session. Maybe another compositor is running?
Sep 20 22:51:46 winstation-arch kwin_wayland[30043]: kwin_wayland_drm: failed to open drm device at "/dev/dri/card1"
Sep 20 22:51:46 winstation-arch kwin_wayland[30043]: kwin_wayland_drm: No suitable DRM devices have been found
Sep 20 22:51:46 winstation-arch kwin_wayland[30043]: QThreadStorage: entry 8 destroyed before end of thread 0x564f3fa407e0
Sep 20 22:51:46 winstation-arch kwin_wayland[30043]: QThreadStorage: entry 1 destroyed before end of thread 0x564f3fa407e0
Sep 20 22:51:46 winstation-arch kwin_wayland[30043]: QThreadStorage: entry 0 destroyed before end of thread 0x564f3fa407e0
Sep 20 22:51:46 winstation-arch systemd[2889]: plasma-kwin_wayland.service: Consumed 1.413s CPU time, 12.3M memory peak.
Sep 20 22:51:46 winstation-arch systemd[2889]: Requested transaction contradicts existing jobs: Transaction for plasma-workspace.target/stop is destructive (plasma-workspace-wayland.target has 'start' job queued, but 'stop' is included in transaction).
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: qt.qpa.wayland: "wl-shell" is a deprecated shell extension, prefer using "xdg-shell" if supported by the compositor by setting the environment variable QT_WAYLAND_SHELL_INTEGRATION
Sep 20 22:51:46 winstation-arch ksplashqml[30005]: qt.qpa.wayland: "wl-shell" is a deprecated shell extension, prefer using "xdg-shell" if supported by the compositor by setting the environment variable QT_WAYLAND_SHELL_INTEGRATION
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: qt.qpa.wayland: Loading shell integration failed.
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: qt.qpa.wayland: Attempted to load the following shells QList("xdg-shell", "wl-shell", "ivi-shell", "qt-shell")
Sep 20 22:51:46 winstation-arch ksplashqml[30005]: qt.qpa.wayland: Loading shell integration failed.
Sep 20 22:51:46 winstation-arch ksplashqml[30005]: qt.qpa.wayland: Attempted to load the following shells QList("xdg-shell", "wl-shell", "ivi-shell", "qt-shell")
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Sep 20 22:51:46 winstation-arch ksplashqml[30005]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: qt.qpa.xcb: could not connect to display :1
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Sep 20 22:51:46 winstation-arch kcminit_startup[30006]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

But this looks recursive, do you try to autostart KDE in your bashrc or something like that?
Can you log in w/ a fresh user account?
https://wiki.archlinux.org/title/Users_ … management

No, I installed SDDM and let that handle if. I do not have anything from KDE set up to autostart.
I tried to manually run start using the command startplasmawayland from tty because it didn't work through SDDM.

I added a test user and tried to log in with SDDM but the same thing happens, it flashes a black screen and returns to SDDM.

seth · 2025-09-20 22:08:24

Please avoid bloating the thread with pointless full quotes and then please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Moonveil · 2025-09-20 22:23:43

seth wrote:

Please avoid bloating the thread with pointless full quotes and then please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

You asked me a question and I answered your questions, I'm sorry for doing so. I was rebooting and uploading the log... Which is not easy because my VPN is still running and if doesn't let me shut it down on startup but 0x0 blocks nearly every IP...

https://0x0.st/KTdt.txt

johan.cb · 2025-09-20 22:33:25

Are you using the kde-unstable repos by any chance?

I faced the exact same issue today and had to revert stable KDE.

seth · 2025-09-20 22:33:45

You asked me a question and I answered your questions, I'm sorry for doing so.

What??
Again, there's no reason to completely quote the previous post - it's visible right above your post.
Maybe https://deepl.com/

Sep 21 00:11:28 winstation-arch auditd[2665]: Missing equal sign for line 17 in /etc/audit/auditd.conf
Sep 21 00:11:28 winstation-arch kernel: audit: audit_lost=7546 audit_rate_limit=0 audit_backlog_limit=64
Sep 21 00:11:28 winstation-arch auditd[2665]: Not processing any more lines in /etc/audit/auditd.conf
Sep 21 00:11:28 winstation-arch kernel: audit: kauditd hold queue overflow
Sep 21 00:11:28 winstation-arch auditd[2665]: The audit daemon is exiting.
Sep 21 00:11:28 winstation-arch kernel: audit: type=1300 audit(1758406288.125:1891): arch=c000003e syscall=257 success=yes exit=9 a0=8 a1=7ff3927afd86 a2=b0800 a3=0 items=0 ppid=880 pid=2662 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-userwor" exe="/usr/lib/systemd/systemd-userwork" subj=systemd-userwork key=(null)
Sep 21 00:11:28 winstation-arch kernel: audit: audit_lost=7547 audit_rate_limit=0 audit_backlog_limit=64
Sep 21 00:11:28 winstation-arch kernel: audit: kauditd hold queue overflow
Sep 21 00:11:28 winstation-arch kernel: audit: type=1327 audit(1758406288.125:1891): proctitle=73797374656D642D75736572776F726B3A2070726F63657373696E672E2E2E
Sep 21 00:11:28 winstation-arch kernel: audit: audit_lost=7548 audit_rate_limit=0 audit_backlog_limit=64
Sep 21 00:11:28 winstation-arch kernel: audit: kauditd hold queue overflow
Sep 21 00:11:28 winstation-arch kernel: audit: audit_lost=7549 audit_rate_limit=0 audit_backlog_limit=64
Sep 21 00:11:28 winstation-arch systemd[1]: auditd.service: Control process exited, code=exited, status=6/NOTCONFIGURED
Sep 21 00:11:28 winstation-arch systemd[1]: auditd.service: Failed with result 'exit-code'.
Sep 21 00:11:28 winstation-arch systemd[1]: Failed to start Security Audit Logging Service.

There's some bogus stuff in /etc/audit/auditd.conf

Sep 21 00:11:28 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 21 00:11:28 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/inhibit/1' into place: No such file or directory
Sep 21 00:11:29 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/967' into place: No such file or directory
Sep 21 00:11:29 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/967' into place: No such file or directory
Sep 21 00:11:29 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 21 00:11:29 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/c1' into place: No such file or directory
Sep 21 00:11:29 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/967' into place: No such file or directory
Sep 21 00:11:29 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 21 00:11:29 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/967' into place: No such file or directory
Sep 21 00:11:29 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/c1' into place: No such file or directory
Sep 21 00:11:29 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/967' into place: No such file or directory
Sep 21 00:11:29 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/1' into place: No such file or directory
Sep 21 00:11:29 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/967' into place: No such file or directory
Sep 21 00:11:30 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/967' into place: No such file or directory
Sep 21 00:11:30 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/c1' into place: No such file or directory
Sep 21 00:11:30 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/967' into place: No such file or directory
Sep 21 00:11:49 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 21 00:11:49 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/967' into place: No such file or directory
Sep 21 00:11:49 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/c1' into place: No such file or directory
Sep 21 00:11:55 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 21 00:11:55 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 21 00:11:55 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 21 00:11:55 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/2' into place: No such file or directory
Sep 21 00:11:55 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 21 00:11:55 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 21 00:11:55 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 21 00:11:55 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/2' into place: No such file or directory
Sep 21 00:11:55 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 21 00:11:55 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/3' into place: No such file or directory
Sep 21 00:11:55 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 21 00:11:55 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 21 00:11:55 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/2' into place: No such file or directory
Sep 21 00:11:55 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 21 00:12:31 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 21 00:12:31 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 21 00:12:31 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/2' into place: No such file or directory
Sep 21 00:12:31 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/c1' into place: No such file or directory
Sep 21 00:12:31 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/967' into place: No such file or directory
Sep 21 00:12:32 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 21 00:12:32 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/967' into place: No such file or directory
Sep 21 00:12:32 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/c1' into place: No such file or directory
Sep 21 00:12:45 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 21 00:12:45 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/4' into place: No such file or directory
Sep 21 00:12:45 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 21 00:12:45 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/seats/seat0' into place: No such file or directory
Sep 21 00:12:45 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/4' into place: No such file or directory
Sep 21 00:12:45 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/1000' into place: No such file or directory
Sep 21 00:12:45 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/sessions/4' into place: No such file or directory
Sep 21 00:12:45 winstation-arch systemd-logind[2738]: Failed to move '/run/systemd/users/1000' into place: No such file or directory

and some massive problem w/ your runfs - disable apparmor, does that change anything about this?

Moonveil · 2025-09-20 22:44:01

johan.cb wrote:

Are you using the kde-unstable repos by any chance?
I faced the exact same issue today and had to revert stable KDE.

I'm using the stable repo as far as I know.

Seth wrote:

What??
Again, there's no reason to completely quote the previous post - it's visible right above your post.

My apologies, I misread your post. I will direct quote parts of the post.

Maybe https://deepl.com/

Native English speaker, believe it or not xD

There's some bogus stuff in /etc/audit/auditd.conf

Idk what that would be, I simply turned it on the way it is written on the wiki. I disabled the service for now.

and some massive problem w/ your runfs - disable apparmor, does that change anything about this?

I don't think so, apparmor is using the same config as it did a few weeks ago, I didn't change anything. Everything is still in complain, not enforced. The system was fine yesterday before I turned it off.

Last edited by Moonveil (2025-09-20 22:48:12)

seth · 2025-09-20 22:51:19

Line 17, in doubt post the file.
Don't think, test

mount | grep run
ls -l /run /run/systemd

You can

(mount | grep run; ls -l /run /run/systemd) | curl -F 'file=@-' 0x0.st

Fwwi, this isn't a KDE problem, the broken runfs breaks logind.

Moonveil · 2025-09-20 22:57:30

seth wrote:

Line 17, in doubt post the file.
Don't think, test

True, and now I broke the system
I can't get into TTY anymore after disabling apparmor and audit. It's just a blinking cursor.

D-Bus system message bus failed
Bluetooth service failed
User Login manager failed

Is there a way to get back into TTY? XD

Last edited by Moonveil (2025-09-20 23:00:56)

seth · 2025-09-20 23:04:21

You could re-enable them at the bootloaders commandline editor, but I doubt this is the cause, can you still boot the rescue.target? (2nd link below)

Moonveil · 2025-09-20 23:07:19

seth wrote:

You could re-enable them at the bootloaders commandline editor, but I doubt this is the cause, can you still boot the rescue.target? (2nd link below)

No, I can't get into terminal at all. I'm booting from Arch install USB now to see if I can get into the system.

I was able to mount and chroot

Last edited by Moonveil (2025-09-20 23:14:30)

Moonveil · 2025-09-20 23:26:54

seth wrote:

can you still boot the rescue.target? (2nd link below)

In chroot su my user

sudo systemctl set-default systemd.unit=rescue.target
Invalid unit name "systemd.unit=rescue.target" escaped as "systems.unit\x3drescue.target" (maybe you should use systemd-escape?)

I was able to enable apparmor again after trying this, I could try to reboot.

Rebooted with apparmor enabled and I'm back in tty.
Auditd.service is disabled and stopped but kauditd is still holding queue overflow

Last edited by Moonveil (2025-09-20 23:33:01)

seth · 2025-09-20 23:34:58

Are audit and the audit daemons disabled?
Are there files in /mnt/run when not chrooted in?

Edit: set "audit=0" in the kernel command line.

Last edited by seth (2025-09-20 23:36:48)

Moonveil · 2025-09-20 23:57:53

seth wrote:

Are audit and the audit daemons disabled?

I forgot the auditd.service. I turned it off.

Are there files in /mnt/run when not chrooted in?

no, /mnt/run: no such file or directory when logged into tty.

Edit: set "audit=0" in the kernel command line.

I will.

The logs you asked for https://0x0.st/KTnf.txt

seth · 2025-09-21 00:06:13

Is https://0x0.st/KTnf.txt from the installed system? Not the install iso?
Are the "Failed to move '/run/*' into place: No such file or directory" errors still in the journal?

Moonveil · 2025-09-21 00:27:14

seth wrote:

Is https://0x0.st/KTnf.txt from the installed system?

yes, I did a normal boot, switched from SDDM and created these logs.

Are the "Failed to move '/run/*' into place: No such file or directory" errors still in the journal?

They are still there

systemd-logind[2681]: Failed to move 'run/systemd/user/967' into place: no such file or Directory

That's one of the run errors.

There are still a lot of KDE failures in the log too but at least audit is disabled and the system is able to get into tty again with apparmor enabled.

I don't understand what caused this. The only thing I did yesterday was update, it worked fine when I turned it off.

Edit: if I ls -l /run/systems/users/ the directory does exist but is empty. ls -l /run/user/ does exist and contains 967 sddm with the classes manager-early and greeter and 1000 which contains my username with the classes user and greeter according to loginctl list-sessions.

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

seth · 2025-09-21 06:57:38

pacman -Qikk systemd

sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files' | grep -v backup

Edit: if I ls -l /run/systems/users/ the directory does exist but is empty.

That should be /run/systemd/users/, can you

sudo touch /run/systemd/users/fubar

Moonveil · 2025-09-21 08:52:08

seth wrote:

pacman -Qikk systemd

sudo LC_ALL=C pacman -Qkk | grep -v ', 0 altered files' | grep -v backup

Warning: firejail: /etc/apparmor.d/firejail-default (Modification time mismatch)
Warning: firejail: /etc/apparmor.d/firejail-default (Size mismatch)
Warning: firejail: /etc/apparmor.d/firejail-default (SHA256 checksum mismatch)
Warning: libutempter: /usr/lib/utempter/utempter (GID Mismatch)
Warning: libutempter: /usr/lib/utempter/utempter (Permissions Mismatch)
Warning: libvlc: /usr/lib/vlc/plugins/plugins.dat (Modification time mismatch)
Warning: libvlc: /usr/lib/vlc/plugins/plugins.dat  (Size mismatch)
Warning: libvlc: /usr/lib/vlc/plugins/plugins.dat (SHA256 checksum mismatch)
Warning: mullvad-vpn-bin: /usr/bin/mullvad-exclude (Permissions Mismatch)
Warning: opensnitch: /etc/opensnitchd/system-fw.json (Permissions Mismatch)
Warning: python-fangfrisch: /etc/fangfrisch/fangfrisch-has-news.sh (GID mismatch)
firejail: 1463 total files, 1 altered file
libutempter: 20 total files, 1 altered file 
libvlc: 120 total files, 1 altered file
mullvad-vpn-bin; 144 total files, 1 altered file
opensnitch: 414 total files, 1 altered file
Warning: shadow: /usr/bin/groupmems (GID mismatch)
Warning: shadow: /usr/bin/groupmems (Permissions mismatch)
Warning: systemd: /var/log/journal (GID mismatch)
python-fangfrisch: 80 total files, 1 altered file
shadow: 576 total files, 1 altered file
systemd:  1669 total files, 1 altered file

Fangfrisch is the last thing I installed and configured before the system broke down.

sudo touch /run/systemd/users/fubar

That worked without errors, autocorrect on my phone turned systemd into systems.

Last edited by Moonveil (2025-09-21 09:02:02)

seth · 2025-09-21 09:02:43

The Qikk for systems is missing.
Make sure it's 258-2 and in doubt downgrade to that last 257 version.

Moonveil · 2025-09-21 09:24:29

seth wrote:

The Qikk for systems is missing.
Make sure it's 258-2 and in doubt downgrade to that last 257 version.

How do I do that? You lost me there, I didn't know what I was looking at so I don't know what I'm looking for now, I'm still learning, sorry

Edit: I think I understand.

pacman -Q systemd
Systemd 258-2

Do I need to downgrade? If I have to, how do I do that?

Last edited by Moonveil (2025-09-21 09:32:25)

seth · 2025-09-21 09:50:14

https://wiki.archlinux.org/title/Arch_Linux_Archive

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

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.

Arch Linux

#1 2025-09-20 19:48:29

[SOLVED] Cant start KDE-wayland anymore after update

#2 2025-09-20 20:22:30

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

#3 2025-09-20 20:32:50

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

#4 2025-09-20 20:55:24

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

#5 2025-09-20 21:40:10

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

#6 2025-09-20 22:04:48

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

#7 2025-09-20 22:08:24

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

#8 2025-09-20 22:23:43

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

#9 2025-09-20 22:33:25

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

#10 2025-09-20 22:33:45

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

#11 2025-09-20 22:44:01

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

#12 2025-09-20 22:51:19

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

#13 2025-09-20 22:57:30

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

#14 2025-09-20 23:04:21

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

#15 2025-09-20 23:07:19

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

#16 2025-09-20 23:26:54

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

#17 2025-09-20 23:34:58

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

#18 2025-09-20 23:57:53

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

#19 2025-09-21 00:06:13

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

#20 2025-09-21 00:27:14

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

#21 2025-09-21 06:57:38

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

#22 2025-09-21 08:52:08

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

#23 2025-09-21 09:02:43

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

#24 2025-09-21 09:24:29

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

#25 2025-09-21 09:50:14

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

Board footer