[Testing Update] 2025-11-10 - Kernels, Systemd, Mkinitcpio, KDE Gear, Plasma

Announcements Testing Updates
21

I experience a couple of issues with kernel 6.17.7 an GNOME. General question: Should I report this here at all or is this the wrong place?

Issues

  • Workspace switching is not possible after hitting a workspace with a a fullscreen window
  • Super key is dead

All this works with 6.12.57

1 Like
23

@wezea @nazgul77

Please create a new Support thread for further troubleshooting.

1 Like
24

I am on the testing update train, using the Manjaro Gnome edition.

My latest update 2 days ago left my system booting into the console login prompt, instead of the graphical display manager GDM.

Examining the system journal reveals this dependency cycle

Nov 13 22:35:20 rivendell systemd[1]: sockets.target: Found ordering cycle: systemd-machined.socket/start after sysinit.target/start after systemd-binfmt.service/start after local-fs.target/start after space.automount/start after netwo>
Nov 13 22:35:20 rivendell systemd[1]: sockets.target: Job systemd-machined.socket/start deleted to break ordering cycle starting with sockets.target/start
Nov 13 22:35:20 rivendell systemd[1]: sockets.target: Found ordering cycle: gpg-agent-ssh@etc-pacman.d-gnupg.socket/start after sysinit.target/start after systemd-binfmt.service/start after local-fs.target/start after space.automount/s>
Nov 13 22:35:20 rivendell systemd[1]: sockets.target: Job gpg-agent-ssh@etc-pacman.d-gnupg.socket/start deleted to break ordering cycle starting with sockets.target/start
Nov 13 22:35:20 rivendell systemd[1]: sockets.target: Found ordering cycle: dbus.socket/start after sysinit.target/start after systemd-binfmt.service/start after local-fs.target/start after space.automount/start after network-online.ta>
Nov 13 22:35:20 rivendell systemd[1]: sockets.target: Job dbus.socket/start deleted to break ordering cycle starting with sockets.target/start

So dbus socket was not brought up, which in turn lets systemd-logind down, which leads to unhappy GDM

Nov 13 22:35:22 rivendell systemd-logind[901]: Failed to connect to system bus: No such file or directory
Nov 13 22:35:22 rivendell systemd-logind[901]: Failed to fully start up daemon: No such file or directory
Nov 13 22:35:22 rivendell systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
Nov 13 22:35:22 rivendell systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
...
Nov 13 22:35:22 rivendell systemd[1]: Failed to start User Login Management.

However, on the CLI prompt I logged in and I was able to start display-manager.service just fine without (re)starting dbus or doing any other magic.

25