I'm running KDE libs 4.14.5-1 package on Arch linux (Konsole about claims I'm using KDE framework 5.7.0). Recently I've observed that If I suspend and resume my system very frequently the following happens * The kdeinit4 process stars using a large amount of CPU time and does not stop doing so * Global keyboard shortcuts stop working (.e.g CTRL+ ALT + T to open konsole doesn't work) * Trying to an open a KDE application like dolphin fails. See attached (dolphin.strace). It seems to it's trying to poll dbus and it's not getting a response. It eventually starts after the dbus timeout expires. * Trying to suspend again from KDE fails. Nothing seems to happen (running ``systemctl suspend`` works though. I also noticed in .xsession-error there is a message about dbus failing ``` Resource id: 0x2600b45 Error response: "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 reply timeout expired, or the network connection was broken." dolphin(25563)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "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 reply timeout expired, or the network connection was broken." ``` Reproducible: Sometimes Steps to Reproduce: 1. Suspend system from Lock/Logout widget on panel 2. Resume. 3. Try to launch dolphin Actual Results: Dolphin doesn't launch immediately launch (dbus problems) and other parts of KDE seem to misbehave. Expected Results: On resume KDE should function correctly I probably haven't provided enough information on how to debug this. If someone could provide guidance I'll happily look into this further.
Created attachment 91505 [details] Strace of trying to launch dolphin after resume
I've also observed when I just tried to upload the strace that the file selection dialog is broken after resume as well (presumably it is also trying to talk to dbus and timing out). My only solution right now after resume is to do ``` systemctl restart kdm.service ``` This kind of defeats the purpose of suspending though...
Sorry, for clarification. This bug always seems to happen on the second resume from suspend. The first time I do it kde seems to work fine but if I suspend and resume again then things start going wrong.
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported and confirmed, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!