KDE

5238 readers

35 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago

MODERATORS

[email protected]

Anyone else unable to log out of Plasma 6? (lemmy.world)

submitted 6 months ago by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

On one of my machines, I am completely unable to log out. The behavior is slightly different depending on whether I am in Wayland or X11.

Wayland

Clicking log out and then OK in the log out window brings me back to the desktop.
Doing this again does the same thing
Clicking log out for a third time does nothing

X11

Clicking log out will lead me to a black screen with just my mouse cursor.

In my journalctl logs, I see:

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]: [email protected]: 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-:[email protected]: Deactivated successfully.
Apr 03 21:52:47 arch-nas systemd[1]: dbus-:[email protected]: Deactivated successfully.
Apr 03 21:52:47 arch-nas systemd[1]: dbus-:[email protected]: Deactivated successfully.
Apr 03 21:52:48 arch-nas systemd[1]: dbus-:[email protected]: 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-:[email protected].
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-:[email protected].
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  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-:[email protected]: Main process exited, code=exited, status=1/FAILURE
Apr 03 21:52:55 arch-nas systemd[4500]: dbus-:[email protected]: Failed with result 'exit-code'.graphical-session.target/stop

I've filed an upstream bug for this but I was wondering if anyone else here was also experiencing the same issue.

top 9 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 6 months ago (1 children)

Do you have a ~/.config/startkderc file?

If so, remove it. That fixed the issue for me.

I had this file because I used it at some point in the past to turn off systemd integration in an attempt to fix some other issue.

[–] [email protected] 1 points 6 months ago (1 children)

I do not have this file at all. I think yours was a different issue.

[–] [email protected] 1 points 6 months ago

Yeah, different issue then. Too bad, wish it could have helped.

[–] [email protected] 1 points 6 months ago (1 children)

Had the same issue, but it solved itself somehow. Now I am too afraid to look into it, in fear of triggering it again :D

[–] [email protected] 2 points 6 months ago

It will occasionally work so you may have just gotten lucky. It seems like its a drkonqi issue, see the linked upstream bug report for the workarounds. You can either uninstall drkonqi or just mask the systemd service for now.

[–] [email protected] 0 points 6 months ago (1 children)

@Molecular0079
I have not seen this with KDE 6 on arch.

[–] [email protected] 1 points 6 months ago (1 children)

Do you have drkonqi installed? According to this thread, it's an issue with drkonqi.

https://bbs.archlinux.org/viewtopic.php?pid=2163139#p2163139

[–] [email protected] 0 points 6 months ago (1 children)

@Molecular0079 Sorry for the late reply. No, I do not have it installed.

[–] [email protected] 1 points 6 months ago

Yeah that explains why you're not seeing the issue. Seems like drkonqi activates on logout and holds up the entire process.