[SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

mcloaked · 2024-04-02 13:39:53

Since yesterday (when my system was running without any issue) I ran pacman -Syu today, and my Plasma 6 Wayland session no longer logs out, whether selected from the right click menu or from the kicker. Selecting logout does nothing at all, and then trying a second time the window that has 'logout' as an option no longer displays either. I have been trying to identify which package update is responsible and have downgraded various individual packages, but I still can't find which is the package update that made the change that prevents logout from the Plasma 6 session.

The list of packages updated today was:

[2024-04-02T10:06:29+0100] [ALPM] upgraded curl (8.7.1-3 -> 8.7.1-4)
[2024-04-02T10:06:29+0100] [ALPM] upgraded exiv2 (0.28.2-2 -> 0.28.2-3)
[2024-04-02T10:06:29+0100] [ALPM] upgraded libgirepository (1.80.0-1 -> 1.80.1-1)
[2024-04-02T10:06:29+0100] [ALPM] upgraded gobject-introspection-runtime (1.80.0-1 -> 1.80.1-1)
[2024-04-02T10:06:29+0100] [ALPM] upgraded gjs (2:1.80.2-1 -> 2:1.80.2-2)
[2024-04-02T10:06:29+0100] [ALPM] upgraded gobject-introspection (1.80.0-1 -> 1.80.1-1)
[2024-04-02T10:06:29+0100] [ALPM] upgraded jansson (2.14-2 -> 2.14-3)
[2024-04-02T10:06:29+0100] [ALPM] upgraded libxkbcommon (1.7.0-1 -> 1.7.0-2)
[2024-04-02T10:06:29+0100] [ALPM] upgraded libxkbcommon-x11 (1.7.0-1 -> 1.7.0-2)
[2024-04-02T10:06:29+0100] [ALPM] upgraded mesa (1:24.0.4-1 -> 1:24.0.4-2)
[2024-04-02T10:06:29+0100] [ALPM] upgraded sdl2 (2.30.1-1 -> 2.30.2-1)
[2024-04-02T10:06:29+0100] [ALPM] upgraded kirigami-addons (1.0.1-1 -> 1.1.0-1)
[2024-04-02T10:06:29+0100] [ALPM] upgraded libindi (2.0.6-1 -> 2.0.7-1)
[2024-04-02T10:06:29+0100] [ALPM] upgraded tdb (1.4.10-1 -> 1.4.10-2)
[2024-04-02T10:06:29+0100] [ALPM] upgraded tracker3 (3.7.1-1 -> 3.7.1-2)
[2024-04-02T10:06:30+0100] [ALPM] upgraded kstars (1:3.6.9-1 -> 1:3.7.0-1)
[2024-04-02T10:06:30+0100] [ALPM] upgraded tevent (1:0.16.1-1 -> 1:0.16.1-2)
[2024-04-02T10:06:30+0100] [ALPM] upgraded ldb (2:2.9.0-1 -> 2:2.9.0-2)
[2024-04-02T10:06:30+0100] [ALPM] upgraded libva-mesa-driver (1:24.0.4-1 -> 1:24.0.4-2)
[2024-04-02T10:06:30+0100] [ALPM] upgraded libwbclient (4.20.0-1 -> 4.20.0-2)
[2024-04-02T10:06:30+0100] [ALPM] upgraded mesa-vdpau (1:24.0.4-1 -> 1:24.0.4-2)
[2024-04-02T10:06:30+0100] [ALPM] upgraded mutter (46.0-1 -> 46.0-2)
[2024-04-02T10:06:31+0100] [ALPM] upgraded node-gyp (10.1.0-1 -> 10.1.0-2)
[2024-04-02T10:06:31+0100] [ALPM] upgraded pstoedit (4.01-1 -> 4.01-2)
[2024-04-02T10:06:32+0100] [ALPM] upgraded rust (1:1.77.1-1 -> 1:1.77.1-2)
[2024-04-02T10:06:32+0100] [ALPM] upgraded smbclient (4.20.0-1 -> 4.20.0-2)
[2024-04-02T10:06:33+0100] [ALPM] upgraded samba (4.20.0-1 -> 4.20.0-2)
[2024-04-02T10:06:33+0100] [ALPM] upgraded vulkan-intel (1:24.0.4-1 -> 1:24.0.4-2)
[2024-04-02T10:06:33+0100] [ALPM] upgraded vulkan-mesa-layers (1:24.0.4-1 -> 1:24.0.4-2)
[2024-04-02T10:06:33+0100] [ALPM] upgraded vulkan-radeon (1:24.0.4-1 -> 1:24.0.4-2)
[2024-04-02T10:06:33+0100] [ALPM] upgraded vulkan-swrast (1:24.0.4-1 -> 1:24.0.4-2)
[2024-04-02T10:06:33+0100] [ALPM] upgraded whois (5.5.21-1 -> 5.5.22-1)

and

[2024-04-02T10:24:12+0100] [ALPM] upgraded xz (5.6.1-2 -> 5.6.1-3)
[2024-04-02T10:24:12+0100] [ALPM] upgraded libarchive (3.7.2-1 -> 3.7.2-2)
[2024-04-02T10:24:12+0100] [ALPM] upgraded util-linux-libs (2.40-1 -> 2.40-2)
[2024-04-02T10:24:12+0100] [ALPM] upgraded util-linux (2.40-1 -> 2.40-2)

plus

[2024-04-02T14:03:20+0100] [ALPM] upgraded sdl2 (2.30.1-1 -> 2.30.2-1)

Has anyone else come across this issue, and if so found a workaround or specific downgrade of a package to bring back logout capability?

Last edited by mcloaked (2024-04-08 08:58:30)

mcloaked · 2024-04-02 19:45:46

I found that the latest updates seemed to have affected my custom sddm theme - which was basically a copy of the files in the breeze sddm theme, and with small changes to reflect the different background and name only. However the plasma session occasionally will logout when the system is first booted and logged into the Plasma Wayland session, but subsequent attempt to logout either via the right click menu, or selecting logout from the bottom right of the kicker then do nothing - if I restart sddm I can log back in via the greeter, but the logout problem persists.

The section of the journal log when I tried to logout may hold a clue to the problem but I can't relate the information to something I can change to fix the problem:

Apr 02 20:49:29 incus systemd[888]: Created slice Slice /app/dbus-:1.2-org.kde.LogoutPrompt.
Apr 02 20:49:29 incus systemd[888]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service.
Apr 02 20:49:30 incus ksmserver-logout-greeter[2246]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
Apr 02 20:49:31 incus systemd[888]: Created slice Slice /app/dbus-:1.2-org.kde.Shutdown.
Apr 02 20:49:31 incus systemd[888]: Started dbus-:1.2-org.kde.Shutdown@0.service.
Apr 02 20:49:31 incus systemd[888]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Main process exited, code=exited, status=1/FAILURE
Apr 02 20:49:31 incus systemd[888]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'.
Apr 02 20:49:31 incus systemd[888]: Stopped target plasma-workspace-wayland.target.
Apr 02 20:49:31 incus systemd[888]: Stopped target KDE Plasma Workspace.
Apr 02 20:49:31 incus systemd[888]: Requested transaction contradicts existing jobs: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction).
Apr 02 20:49:31 incus systemd[888]: graphical-session.target: Failed to enqueue stop job, ignoring: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction).
Apr 02 20:49:31 incus systemd[888]: Stopped target KDE Plasma Workspace Core.
Apr 02 20:49:31 incus systemd[888]: Stopped target Startup of XDG autostart applications.
Apr 02 20:49:31 incus systemd[888]: Stopped target Session services which should run early before the graphical session is brought up.
Apr 02 20:49:31 incus qterminal[2166]: virtual KPtyProcess::~KPtyProcess() the terminal process is still running, trying to stop it by SIGHUP
Apr 02 20:49:33 incus systemd-timesyncd[647]: Contacted time server 162.159.200.1:123 (0.pool.ntp.org).
Apr 02 20:49:33 incus systemd-timesyncd[647]: Initial clock synchronization to Tue 2024-04-02 20:49:33.431065 BST.
Apr 02 20:49:35 incus systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Apr 02 20:49:36 incus plasmashell[1149]: kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/file" not found
Apr 02 20:49:36 incus systemd[888]: Started QTerminal - Terminal emulator.
Apr 02 20:49:36 incus qterminal[2296]: Using a variable-width font in the terminal.  This may cause performance degradation and display/alignment errors.
Apr 02 20:49:36 incus systemd[1]: systemd-localed.service: Deactivated successfully.

The lines referring to stopping target seem may not be related to the attempt to logout since I then had to restart sddm via a console command. If anyone can point me to a way to get more diagnostics to find a solution it would be appreciated.

Last edited by mcloaked (2024-04-02 19:58:02)

mcloaked · 2024-04-03 12:56:51

I have made some progress with this. Checking the files in the sddm theme directory, and making sure the metadata file is sane, as well as checking the background image files are referenced correctly and exist in the specified path - by going to the plasma settings, and under Colours and Themes -> Login Screen (SDDM), and then choosing Apply Plasma Settings from the top right, as well as clicking the icon to change the background image and selecting and saving. The four systems have now all logged out once these changes have been saved and the systems restarted. So this needs testing to check whether the logout now works consistently or not over a period of days. Initially I reverted to the default breeze them and the logout problem was the same as with the custom (breeze-based) theme. However it is possible that particularly the selection of the background image and using 'Apply Plasma Settings' to the chosen theme may have been the change that seems to have made a difference, since this may clean up the data associated with the theme being used in the plasma cache directories. If this turns out to work consistently then I will mark this thread as solved after a few days.

mcloaked · 2024-04-03 19:44:09

Interesting find - there is a console command that will bring up the logout window. If the system is behaving it works, and selecting logout does log out and go back to the sddm greeter. But when the right click to select logout is not working then this command gives this error message:

$ /usr/lib/ksmserver-logout-greeter --windowed
kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11

So now this might point to where there is a problem?

This bug may be related: https://bugs.kde.org/show_bug.cgi?id=482020

Last edited by mcloaked (2024-04-03 21:24:45)

UrbenLegend · 2024-04-04 05:16:46

I am having the exact same issue as you on one of my KDE systems. I see some commonalities between our logs, mainly the `graphical-session.target/stop` and `LogoutPrompt service` messages:

Apr 03 21:52:46 arch-nas systemd[1]: Stopping User Runtime Directory /run/user/972...
Apr 03 21:52:46 arch-nas systemd[1]: run-user-972.mount: Deactivated successfully.
Apr 03 21:52:46 arch-nas systemd[1]: user-runtime-dir@972.service: Deactivated successfully.
Apr 03 21:52:46 arch-nas systemd[1]: Stopped User Runtime Directory /run/user/972.
Apr 03 21:52:46 arch-nas systemd[1]: Removed slice User Slice of UID 972.
Apr 03 21:52:46 arch-nas systemd[1]: user-972.slice: Consumed 1.564s CPU time.
Apr 03 21:52:47 arch-nas systemd[1]: dbus-:1.2-org.kde.kded.smart@0.service: Deactivated successfully.
Apr 03 21:52:47 arch-nas systemd[1]: dbus-:1.2-org.kde.powerdevil.discretegpuhelper@0.service: Deactivated successfully.
Apr 03 21:52:47 arch-nas systemd[1]: dbus-:1.2-org.kde.powerdevil.backlighthelper@0.service: Deactivated successfully.
Apr 03 21:52:48 arch-nas systemd[1]: dbus-:1.2-org.kde.powerdevil.chargethresholdhelper@0.service: Deactivated successfully.
Apr 03 21:52:54 arch-nas systemd[4500]: Created slice Slice /app/dbus-:1.2-org.kde.LogoutPrompt.
Apr 03 21:52:54 arch-nas systemd[4500]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service.
Apr 03 21:52:54 arch-nas ksmserver-logout-greeter[5553]: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
Apr 03 21:52:54 arch-nas ksmserver-logout-greeter[5553]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
Apr 03 21:52:54 arch-nas plasmashell[5079]: qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0
Apr 03 21:52:55 arch-nas systemd[4500]: Created slice Slice /app/dbus-:1.2-org.kde.Shutdown.
Apr 03 21:52:55 arch-nas systemd[4500]: Started dbus-:1.2-org.kde.Shutdown@0.service.
Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target plasma-workspace-wayland.target.
Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target KDE Plasma Workspace.
Apr 03 21:52:55 arch-nas systemd[4500]: Requested transaction contradicts existing jobs: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction).
Apr 03 21:52:55 arch-nas systemd[4500]: graphical-session.target: Failed to enqueue stop job, ignoring: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction).
Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target KDE Plasma Workspace Core.
Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target Startup of XDG autostart applications.
Apr 03 21:52:55 arch-nas systemd[4500]: Stopped target Session services which should run early before the graphical session is brought up.
Apr 03 21:52:55 arch-nas systemd[4500]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Main process exited, code=exited, status=1/FAILURE
Apr 03 21:52:55 arch-nas systemd[4500]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'.

I do not think the bug you linked is related as the necessary files are in /usr/share/dbus-1/services

UrbenLegend · 2024-04-04 05:28:57

I've filed an upstream bug for this: https://bugs.kde.org/show_bug.cgi?id=485011

mcloaked · 2024-04-04 07:03:30

It is useful filing a new bug on this. I have four systems - with all set up the same way for sddm and Plasma 6 and the logout issue is sometimes present and sometimes not - any one machine sometimes allows the logout normally and other times just does nothing and stays logged in. Also sometimes the logout window opens and clicking logout simply goes back to the normal Plasma desktop without logging out. At other times the logout window opens and does logout, and other times the logout window does not appear at all. I don't know if that inconsistency in response also has information about the problem. I can't see any particular set of conditions that triggers logging out OK, opening the logout window but then not logging out, or not opening the logout window at all. Maybe the journal contains enough information for a developer to see where the underlying problem is. However I have been using 'systemctl restart sddm' to get logged out, which is not ideal.

UrbenLegend · 2024-04-04 17:16:31

For me the behavior is pretty consistently triggerable:

Wayland:
1. First click on log out will show the log out window. Clicking OK does nothing and just goes back to desktop.
2. Doing this repeatedly will eventually cause the log out window to not appear at all. The log out button essentially does nothing at this point.

X11:
1. Clicking log out and then OK will always lead to a black screen. I have to restart SDDM in order to completely log out.

Also, in Wayland, I don't think restarting SDDM completely logs you out. I usually can't log back in if I do so, indicating that there's some user session left over.

EDIT: Okay, I was able to log out ONCE in Wayland, so you are right that it could be inconsistent. It happens very rarely for me though.

Last edited by UrbenLegend (2024-04-04 17:29:23)

mcloaked · 2024-04-06 15:37:44

After I updated my machines later on the 4th April, I have not had any exhibit the failure to log out from Plasma, and I did not change anything in my setups. I will continue to test over the next few days, but at this point I am presuming that there was a bug that has been 'fixed' by one of the packages that updated. There have been various updates on the graphics package sets including mesa, but I can't know if that was the 'fix' that now makes logging out of the Plasma (Wayland) now work consistently OK, or something else.

UrbenLegend · 2024-04-06 17:16:20

Hmm I am still seeing the issues and I am completely up to date. I was able to log out once, but trying again exhibited the same behavior.

mzhao · 2024-04-07 02:28:44

I have two up to date machines running sddm with Plasma 6 - I haven't been able to log out on either of them.

seth · 2024-04-07 07:13:32

Sanity check: since KDE/SDDM had issues w/ shutting down the system out of the session, did any of you mitigate that by replacing sddm w/ sddm-git from the AUR and are sitting on a dated version of the latter now?

UrbenLegend · 2024-04-07 07:14:34

I am using the sddm 0.21 that's available from the main repos and I am not using the AUR sddm-git.

mcloaked · 2024-04-07 08:58:42

Seth, I didn't try sddm-git, but my systems all continue to logout without issue the past few days. I don't know if it is worth looking at the list of pacman packages that updated three days ago on my systems to see if any of those may be relevant to how Plasma Wayland may behave, but it is puzzling as to why the issue was there, and also why it was intermittent for me and then resolved (for me) without making any changes.

mcloaked · 2024-04-07 09:37:35

A quarter of an hour after I posed the above, my wife logged in to one machine that I had had no issues logging out - but from her account she could not log out, and I had to restart sddm. When I logged in I can now also no longer logout from Plasma - so clearly something has now changed in the sddm files (somewhere). So now I also have to restart sddm with the loss of ability to use either right click to access the logout or from the kicker, and neither of those work any longer on this machine. So it looks like something gets triggered to be wrongly set in the sddm files, but what that is and what is then needed to get it going again I cannot find. I may try to go through the setting of the plasma desktop settings with the greeter on the System settings from the Plasma desktop to see if that resets sddm - when I can get back to the machine later today. So this remains a puzzle - and if there is any suggestion of how to get some diagnostics to point to where the bug lies that would be useful.

seth · 2024-04-07 09:48:16

Visual explanation of what's likely going on: https://geek-and-poke.com/geekandpoke/2 … ading.html

This here is likely critical/representative of the issue (and does not appear for the "good" logouts)?

Apr 02 20:49:29 incus systemd[888]: Created slice Slice /app/dbus-:1.2-org.kde.LogoutPrompt.
Apr 02 20:49:29 incus systemd[888]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service.
Apr 02 20:49:30 incus ksmserver-logout-greeter[2246]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
Apr 02 20:49:31 incus systemd[888]: Created slice Slice /app/dbus-:1.2-org.kde.Shutdown.
Apr 02 20:49:31 incus systemd[888]: Started dbus-:1.2-org.kde.Shutdown@0.service.
Apr 02 20:49:31 incus systemd[888]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Main process exited, code=exited, status=1/FAILURE
Apr 02 20:49:31 incus systemd[888]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'.

Have you checked

systemctl status dbus-:1.2-org.kde.LogoutPrompt@0.service

?
Since that thing is autogenerated by dbus-broker, what if you replace dbus-broker-units w/ dbus-daemon-units?

mcloaked · 2024-04-07 12:41:19

$ pacman -Q dbus-broker-units
dbus-broker-units 35-2
$ systemctl status dbus-:1.2-org.kde.LogoutPrompt@0.service
Unit dbus-:1.2-org.kde.LogoutPrompt@0.service could not be found.

I had switched to dbus broker when Arch made that transition and there were no issues until the recent Plasma 6 Wayland logout problems in the last week or so.

The list of dbus related units on systemd are:

$ systemctl list-units | grep dbus
  dbus-broker.service                                                                       loaded active running   D-Bus System Message Bus
  system-dbus\x2d:1.2\x2dorg.kde.kded.smart.slice                                           loaded active active    Slice /system/dbus-:1.2-org.kde.kded.smart
  system-dbus\x2d:1.2\x2dorg.kde.powerdevil.backlighthelper.slice                           loaded active active    Slice /system/dbus-:1.2-org.kde.powerdevil.backlighthelper
  system-dbus\x2d:1.2\x2dorg.kde.powerdevil.chargethresholdhelper.slice                     loaded active active    Slice /system/dbus-:1.2-org.kde.powerdevil.chargethresholdhelper
  system-dbus\x2d:1.2\x2dorg.kde.powerdevil.discretegpuhelper.slice                         loaded active active    Slice /system/dbus-:1.2-org.kde.powerdevil.discretegpuhelper
  dbus.socket                                                                               loaded active running   D-Bus System Message Bus Socket

So there is no LogoutPrompt related service listed.

Also possibly interesting is that on a different machine (a laptop) where I can apparently logout normally, I looked at the journal for the previous boot, where I had logged out and powered off normally - and find this in the journal:

 sudo journalctl -b -1 | grep Logout
Apr 07 10:26:57 ryzen1 systemd[893]: Created slice Slice /app/dbus-:1.2-org.kde.LogoutPrompt.
Apr 07 10:26:57 ryzen1 systemd[893]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service.
Apr 07 10:26:59 ryzen1 systemd[893]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Main process exited, code=exited, status=1/FAILURE
Apr 07 10:26:59 ryzen1 systemd[893]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'.
Apr 07 10:27:04 ryzen1 systemd[893]: Removed slice Slice /app/dbus-:1.2-org.kde.LogoutPrompt.

So even though I apparently logged out back to the sddm greeter, and then shut down, the journal suggests that the logout was not normal. So there is clearly a bug here, even for the occasions when I can logout from the Plasma desktop since the logs are showing unexpected output.

Oh - and neat cartoon, Seth!

This report is also related: https://www.reddit.com/r/kde/comments/1 … _plasma_6/

Also is there anything in the sddm 0.21 changelog at https://github.com/sddm/sddm/blob/v0.21.0/ChangeLog that might indicate a change that is relevant?

Last edited by mcloaked (2024-04-07 13:03:43)

mcloaked · 2024-04-07 13:10:56

I have also discovered this set of directories/files and wonder if exploring their content might yield a few clues:

$ sudo ls -lh /var/lib/sddm/.local
total 8.0K
drwxr-xr-x 5 sddm sddm 4.0K Apr  2 18:05 share
drwx------ 3 sddm sddm 4.0K Mar 18 16:44 state
$ sudo ls -lh /var/lib/sddm/.cache
total 17M
-rw-------  1 sddm sddm 9.9K Apr  7 10:38 ksvg-elements
drwx------ 42 sddm sddm 4.0K Apr  7 10:39 mesa_shader_cache
-rw-r--r--  1 sddm sddm  17M Apr  7 13:38 plasma_theme_breeze-dark.kcache
drwxr-xr-x  2 sddm sddm 4.0K Apr  7 10:38 qtshadercache-x86_64-little_endian-lp64
drwxr-xr-x  5 sddm sddm 4.0K Apr  7 10:38 sddm-greeter-qt6

seth · 2024-04-07 14:41:44

So there is no LogoutPrompt related service listed.

Because it gets created on the fly, you should still be able to query the status?

Though w/

So even though I apparently logged out back to the sddm greeter, and then shut down, the journal suggests that the logout was not normal.

that's probably a red herring anyway.

Also is there anything in the sddm 0.21 changelog

I'd first ensure that this is an SDDM problem
=> No problems when replacing it eg. w/ lightdm?

Progressing to the next item

Apr 02 20:49:31 incus systemd[888]: Requested transaction contradicts existing jobs: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction).
Apr 02 20:49:31 incus systemd[888]: graphical-session.target: Failed to enqueue stop job, ignoring: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction).
Apr 02 20:49:31 incus systemd[888]: Stopped target KDE Plasma Workspace Core.
Apr 02 20:49:31 incus systemd[888]: Stopped target Startup of XDG autostart applications.
Apr 02 20:49:31 incus systemd[888]: Stopped target Session services which should run early before the graphical session is brought up.
Apr 02 20:49:31 incus qterminal[2166]: virtual KPtyProcess::~KPtyProcess() the terminal process is still running, trying to stop it by SIGHUP
Apr 02 20:49:33 incus systemd-timesyncd[647]: Contacted time server 162.159.200.1:123 (0.pool.ntp.org).
Apr 02 20:49:33 incus systemd-timesyncd[647]: Initial clock synchronization to Tue 2024-04-02 20:49:33.431065 BST.
Apr 02 20:49:35 incus systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Apr 02 20:49:36 incus plasmashell[1149]: kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/file" not found
Apr 02 20:49:36 incus systemd[888]: Started QTerminal - Terminal emulator.
Apr 02 20:49:36 incus qterminal[2296]: Using a variable-width font in the terminal.  This may cause performance degradation and display/alignment errors.

There seems an issue w/ drkonqi (ironically the KDE crash handler) and esp. qterminal - the latter doesn't quit on the logout to respond w/ a restart on SIGHUP?
Can you properly logout if you first kill all qterminal instances?

(Sidebar: non-fixed witdth fonts in a terminal are a bad idea)

mcloaked · 2024-04-07 14:47:24

OK I should use konsole instead of qterminal bearing in mind your notes on qterminal kill all processes. I will get back to more testing later.

mzhao · 2024-04-07 17:54:21

I installed sddm-git on both my computers. On one, I can consistently log out now, but I still see in the journal:

Apr 07 13:19:18 kaori-arch systemd[731]: Created slice Slice /app/dbus-:1.2-org.kde.LogoutPrompt.
Apr 07 13:19:18 kaori-arch systemd[731]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service.
Apr 07 13:19:18 kaori-arch ksmserver-logout-greeter[3028]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
Apr 07 13:19:18 kaori-arch ksmserver-logout-greeter[3028]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
Apr 07 13:19:18 kaori-arch ksmserver-logout-greeter[3028]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
Apr 07 13:19:18 kaori-arch ksmserver-logout-greeter[3028]: The cached device pixel ratio value was stale on window expose.  Please file a QTBUG which explains how to reproduce.
Apr 07 13:19:19 kaori-arch systemd[731]: Created slice Slice /app/dbus-:1.2-org.kde.Shutdown.
Apr 07 13:19:20 kaori-arch systemd[731]: Started dbus-:1.2-org.kde.Shutdown@0.service.
Apr 07 13:19:20 kaori-arch systemd[731]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Main process exited, code=exited, status=1/FAILURE
Apr 07 13:19:20 kaori-arch systemd[731]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'.
Apr 07 13:19:20 kaori-arch systemd[731]: Stopped target plasma-workspace-wayland.target.
Apr 07 13:19:20 kaori-arch systemd[731]: Stopped target KDE Plasma Workspace.
Apr 07 13:19:20 kaori-arch systemd[731]: Stopped target Startup of XDG autostart applications.

On the other, logging out is still broken. Journal:

Apr 07 13:29:14 rpi-thinkpad systemd[1120]: Created slice Slice /app/dbus-:1.2-org.kde.LogoutPrompt.
Apr 07 13:29:14 rpi-thinkpad systemd[1120]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service.
Apr 07 13:29:14 rpi-thinkpad ksmserver-logout-greeter[2193]: kf.windowsystem: static bool KX11Extras::compositingActive() may only be used on X11
Apr 07 13:29:15 rpi-thinkpad systemd[1120]: Created slice Slice /app/dbus-:1.2-org.kde.Shutdown.
Apr 07 13:29:15 rpi-thinkpad systemd[1120]: Started dbus-:1.2-org.kde.Shutdown@0.service.
Apr 07 13:29:16 rpi-thinkpad systemd[1120]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Main process exited, code=exited, status=1/FAILURE
Apr 07 13:29:16 rpi-thinkpad systemd[1120]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'.
Apr 07 13:29:16 rpi-thinkpad plasmashell[1325]: error creating screencast "Could not find window id {ab190c50-b01f-406b-851e-00bd648f3081}"
Apr 07 13:29:16 rpi-thinkpad systemd[1120]: Stopped target plasma-workspace-wayland.target.
Apr 07 13:29:16 rpi-thinkpad systemd[1120]: Stopped target KDE Plasma Workspace.
Apr 07 13:29:16 rpi-thinkpad systemd[1120]: Requested transaction contradicts existing jobs: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction).
Apr 07 13:29:16 rpi-thinkpad systemd[1120]: graphical-session.target: Failed to enqueue stop job, ignoring: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction).
Apr 07 13:29:16 rpi-thinkpad systemd[1120]: Stopped target KDE Plasma Workspace Core.
Apr 07 13:29:16 rpi-thinkpad systemd[1120]: Stopped target Startup of XDG autostart applications.
Apr 07 13:29:16 rpi-thinkpad systemd[1120]: Stopped target Session services which should run early before the graphical session is brought up.

Seems like the logout greeter error is a red herring.

mcloaked · 2024-04-07 19:29:09

There is an interesting comment in https://bugs.kde.org/show_bug.cgi?id=485011 suggesting a deadlock in systemd caused by drkonqi-coredump-processor. So I checked the journal for drkonqi and find:

$ sudo journalctl -b | grep konqi
Apr 07 19:43:44 incus systemd[753]: Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/var/lib/sddm/.cache/drkonqi/sentry-envelopes/*).
Apr 07 19:43:53 incus systemd[895]: Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/mike/.cache/drkonqi/sentry-envelopes/*).
Apr 07 19:43:53 incus systemd[895]: Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/mike/.cache/drkonqi/sentry-envelopes/*).
Apr 07 19:44:14 incus systemd[895]: Requested transaction contradicts existing jobs: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction).
Apr 07 19:44:14 incus systemd[895]: graphical-session.target: Failed to enqueue stop job, ignoring: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction).
Apr 07 19:44:23 incus systemd[1]: Created slice Slice /system/drkonqi-coredump-processor.
Apr 07 19:44:24 incus drkonqi-coredump-processor[2496]: "/usr/bin/plasmashell" 2484 "/var/lib/systemd/coredump/core.plasmashell.1000.cb3246552e594a3489e2966cf6dde677.2484.1712515463000000.zst"
Apr 07 19:44:24 incus systemd[1]: drkonqi-coredump-processor@0-2492-0.service: Deactivated successfully.
Apr 07 19:44:24 incus drkonqi-coredump-launcher[2524]: Unable to find file for pid 2484 expected at "kcrash-metadata/plasmashell.cb3246552e594a3489e2966cf6dde677.2484.ini"
Apr 07 19:44:24 incus drkonqi-coredump-launcher[2524]: Nothing handled the dump :O
Apr 07 19:44:24 incus systemd[2533]: Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/var/lib/sddm/.cache/drkonqi/sentry-envelopes/*).
Apr 07 19:44:24 incus drkonqi-coredump-processor[2523]: "/usr/lib/org_kde_powerdevil" 2507 "/var/lib/systemd/coredump/core.org_kde_powerde.1000.cb3246552e594a3489e2966cf6dde677.2507.1712515464000000.zst"
Apr 07 19:44:24 incus systemd[1]: drkonqi-coredump-processor@1-2513-0.service: Deactivated successfully.
Apr 07 19:44:24 incus drkonqi-coredump-launcher[2566]: Unable to find file for pid 2507 expected at "kcrash-metadata/org_kde_powerdevil.cb3246552e594a3489e2966cf6dde677.2507.ini"
Apr 07 19:44:24 incus drkonqi-coredump-launcher[2566]: Nothing handled the dump :O
Apr 07 19:44:24 incus drkonqi-coredump-processor[2549]: "/usr/bin/plasmashell" 2525 "/var/lib/systemd/coredump/core.plasmashell.1000.cb3246552e594a3489e2966cf6dde677.2525.1712515464000000.zst"
Apr 07 19:44:24 incus systemd[1]: drkonqi-coredump-processor@2-2543-0.service: Deactivated successfully.
Apr 07 19:44:24 incus drkonqi-coredump-launcher[2599]: Unable to find file for pid 2525 expected at "kcrash-metadata/plasmashell.cb3246552e594a3489e2966cf6dde677.2525.ini"
Apr 07 19:44:24 incus drkonqi-coredump-launcher[2599]: Nothing handled the dump :O
Apr 07 19:44:24 incus drkonqi-coredump-processor[2616]: "/usr/lib/org_kde_powerdevil" 2604 "/var/lib/systemd/coredump/core.org_kde_powerde.1000.cb3246552e594a3489e2966cf6dde677.2604.1712515464000000.zst"
Apr 07 19:44:24 incus systemd[1]: drkonqi-coredump-processor@3-2612-0.service: Deactivated successfully.
Apr 07 19:44:24 incus drkonqi-coredump-launcher[2663]: Unable to find file for pid 2604 expected at "kcrash-metadata/org_kde_powerdevil.cb3246552e594a3489e2966cf6dde677.2604.ini"
Apr 07 19:44:24 incus drkonqi-coredump-launcher[2663]: Nothing handled the dump :O
Apr 07 19:44:25 incus drkonqi-coredump-processor[2686]: "/usr/lib/org_kde_powerdevil" 2680 "/var/lib/systemd/coredump/core.org_kde_powerde.1000.cb3246552e594a3489e2966cf6dde677.2680.1712515464000000.zst"
Apr 07 19:44:25 incus systemd[1]: drkonqi-coredump-processor@4-2682-0.service: Deactivated successfully.
Apr 07 19:44:25 incus drkonqi-coredump-launcher[2699]: Unable to find file for pid 2680 expected at "kcrash-metadata/org_kde_powerdevil.cb3246552e594a3489e2966cf6dde677.2680.ini"
Apr 07 19:44:25 incus drkonqi-coredump-launcher[2699]: Nothing handled the dump :O
Apr 07 19:44:25 incus drkonqi-coredump-processor[2707]: "/usr/lib/org_kde_powerdevil" 2695 "/var/lib/systemd/coredump/core.org_kde_powerde.1000.cb3246552e594a3489e2966cf6dde677.2695.1712515465000000.zst"
Apr 07 19:44:25 incus systemd[1]: drkonqi-coredump-processor@5-2703-0.service: Deactivated successfully.
Apr 07 19:44:25 incus drkonqi-coredump-launcher[2719]: Unable to find file for pid 2695 expected at "kcrash-metadata/org_kde_powerdevil.cb3246552e594a3489e2966cf6dde677.2695.ini"
Apr 07 19:44:25 incus drkonqi-coredump-launcher[2719]: Nothing handled the dump :O
Apr 07 19:44:26 incus drkonqi-coredump-processor[2731]: "/usr/lib/org_kde_powerdevil" 2723 "/var/lib/systemd/coredump/core.org_kde_powerde.1000.cb3246552e594a3489e2966cf6dde677.2723.1712515465000000.zst"
Apr 07 19:44:26 incus systemd[1]: drkonqi-coredump-processor@6-2727-0.service: Deactivated successfully.
Apr 07 19:44:26 incus drkonqi-coredump-launcher[2740]: Unable to find file for pid 2723 expected at "kcrash-metadata/org_kde_powerdevil.cb3246552e594a3489e2966cf6dde677.2723.ini"
Apr 07 19:44:26 incus drkonqi-coredump-launcher[2740]: Nothing handled the dump :O
Apr 07 19:44:33 incus systemd[895]: drkonqi-coredump-pickup.service: Control process exited, code=killed, status=15/TERM
Apr 07 19:44:33 incus systemd[895]: drkonqi-coredump-pickup.service: Failed with result 'signal'.
Apr 07 19:51:48 incus systemd[2792]: Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/mike/.cache/drkonqi/sentry-envelopes/*).
Apr 07 19:53:51 incus systemd[2844]: Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/mike/.cache/drkonqi/sentry-envelopes/*).
Apr 07 20:21:50 incus systemd[2904]: Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/mike/.cache/drkonqi/sentry-envelopes/*).

So possibly this is relevant?

seth · 2024-04-07 19:30:42

I installed sddm-git on both my computers.

Sorry if that was confusing, but that wasn't the suggestion at all (the idea was rather that you maybe had a, now dated, sddm-git installation around)

Apr 07 13:29:16 rpi-thinkpad systemd[1120]: Requested transaction contradicts existing jobs: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction).
Apr 07 13:29:16 rpi-thinkpad systemd[1120]: graphical-session.target: Failed to enqueue stop job, ignoring: Transaction for graphical-session.target/stop is destructive (drkonqi-coredump-pickup.service has 'start' job queued, but 'stop' is included in transaction).

is maybe significant because you share it w/ mcloaked

There's no qterminal, though - the closest thing for the drkonqi invocation would be

Apr 07 13:29:16 rpi-thinkpad plasmashell[1325]: error creating screencast "Could not find window id {ab190c50-b01f-406b-851e-00bd648f3081}"

Your log snippet stops a bit earlier than mcloaked's, though.

Sooo… what if you just remove drkonqi ?
The theory would be that something™ crashes on exit, drkonqi activates and that start breaks the session stop.

Edit: since I obviously didn't write the above in one minute, we've two paths to the same conclusion => try to remove drkonqi

Last edited by seth (2024-04-07 19:32:07)

mcloaked · 2024-04-07 20:56:58

It seems this issue is also seen in SUSE - one user reports he is using gdm and not sddm and sees the same problem with logout: https://forums.opensuse.org/t/unable-to … 6/173931/3 so this seems to rule out sddm as behind the problem.

seth · 2024-04-07 21:03:28

seth wrote:

Sooo… what if you just remove drkonqi ?
The theory would be that something™ crashes on exit, drkonqi activates and that start breaks the session stop.

Arch Linux

#1 2024-04-02 13:39:53

[SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#2 2024-04-02 19:45:46

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#3 2024-04-03 12:56:51

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#4 2024-04-03 19:44:09

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#5 2024-04-04 05:16:46

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#6 2024-04-04 05:28:57

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#7 2024-04-04 07:03:30

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#8 2024-04-04 17:16:31

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#9 2024-04-06 15:37:44

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#10 2024-04-06 17:16:20

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#11 2024-04-07 02:28:44

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#12 2024-04-07 07:13:32

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#13 2024-04-07 07:14:34

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#14 2024-04-07 08:58:42

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#15 2024-04-07 09:37:35

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#16 2024-04-07 09:48:16

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#17 2024-04-07 12:41:19

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#18 2024-04-07 13:10:56

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#19 2024-04-07 14:41:44

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#20 2024-04-07 14:47:24

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#21 2024-04-07 17:54:21

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#22 2024-04-07 19:29:09

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#23 2024-04-07 19:30:42

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#24 2024-04-07 20:56:58

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

#25 2024-04-07 21:03:28

Re: [SOLVED] Plasma 6 Wayland no longer acts to logout after pacman update

Board footer