You are not logged in.
Hi forum,
I am following up on problem I posted to KDE's bugtracker which didn't get me far in terms of help for finding out what the problem actually is.
On Plasma 6.3.3+, the KScreen OSD (Meta+P shortcut by default) doesn't open anymore. I'm getting errors like this:
Apr 03 00:40:13 ppocket-msi systemd[986]: app-org.kde.kscreen@b99843d02a0b4c0a8db56cfdcd39c370.service: Failed with result 'exit-code'.
Apr 03 00:40:13 ppocket-msi systemd[986]: app-org.kde.kscreen@b99843d02a0b4c0a8db56cfdcd39c370.service: Main process exited, code=exited, status=1/FAILUREFollowing the discussion over at KDE, the KScreen OSD gets opened using a D-BUS call when the shortcut is pressed. I am a software developer but by no means an expert in debugging things like this. D-BUS outputs the following exactly 25 seconds after the keypress:
Apr 03 00:40:13 ppocket-msi dbus-send[4139]: Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.KDE's people told me this is a downstrem issue and my D-BUS is broken. I am not sure if that is true.
Do you guys have any pointers for me which can help me narrow down the origin of this issue? Is there another way to trigger the OSD which doesn't use D-BUS and would let me attach with GDB?
I also have to say that this is the case on all three of my machines. So I assume it's not a hardware thing. Also, there are no core dumps as nothing actually crashes as it seems.
I suspect that an update to Qt 6.8.3 might be the problem. I tried downgrading Qt but obviously, that breaks a number of things.
Last edited by poljpocket (2025-04-17 21:12:35)
Offline
Someone else filed the same bug and it just got fixed:
Offline