Bug 443221 - 'sleep' sometimes fails to put laptop to sleep
Summary: 'sleep' sometimes fails to put laptop to sleep
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.22.90
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-02 11:50 UTC by Mariusz Libera
Modified: 2022-07-07 15:58 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mariusz Libera 2021-10-02 11:50:44 UTC
STEPS TO REPRODUCE
1. Press the power button.
2. Select 'sleep' on the logout screen.

OBSERVED RESULT
Sometimes the logout screen disappears and nothing happens.

EXPECTED RESULT
Laptop goes to sleep.


SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.22.90
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.14.7-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 19.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

ADDITIONAL INFORMATION
This started to happen with plasma 5.22 or one of its point releases and continues with the 5.23 beta.

'systemctl suspend' works each time.

Logs when selecting 'sleep' failed 4 times in a row:

paź 02 13:09:56 ideapad520 systemd-logind[402]: Power key pressed.
paź 02 13:09:57 ideapad520 systemd[985]: Started dbus-:1.2-org.kde.LogoutPrompt@12.service.
paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: <input>:406:376: Could not add child element to parent element because the types are incorrect.
paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: <input>:407:130: Could not add child element to parent element because the types are incorrect.
paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: <input>:408:130: Could not add child element to parent element because the types are incorrect.
paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: <input>:408:393: Could not add child element to parent element because the types are incorrect.
paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: <input>:409:130: Could not add child element to parent element because the types are incorrect.
paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: <input>:410:129: Could not add child element to parent element because the types are incorrect.
paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: <input>:411:129: Could not add child element to parent element because the types are incorrect.
paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: <input>:412:129: Could not add child element to parent element because the types are incorrect.
paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: <input>:413:129: Could not add child element to parent element because the types are incorrect.
paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: <input>:413:379: Could not add child element to parent element because the types are incorrect.
paź 02 13:09:57 ideapad520 ksmserver-logout-greeter[258366]: qt.svg: <input>:413:631: Could not add child element to parent element because the types are incorrect.
paź 02 13:09:58 ideapad520 kwin_x11[1047]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 57557, resource id: 90177582, major code: 18 (ChangeProperty), minor code: 0
paź 02 13:09:58 ideapad520 systemd[985]: dbus-:1.2-org.kde.LogoutPrompt@12.service: Main process exited, code=exited, status=1/FAILURE
paź 02 13:09:58 ideapad520 systemd[985]: dbus-:1.2-org.kde.LogoutPrompt@12.service: Failed with result 'exit-code'.
paź 02 13:10:02 ideapad520 systemd-logind[402]: Power key pressed.
paź 02 13:10:02 ideapad520 systemd[985]: Started dbus-:1.2-org.kde.LogoutPrompt@13.service.
paź 02 13:10:04 ideapad520 kwin_x11[1047]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 58982, resource id: 90177582, major code: 18 (ChangeProperty), minor code: 0
paź 02 13:10:04 ideapad520 systemd[985]: dbus-:1.2-org.kde.LogoutPrompt@13.service: Main process exited, code=exited, status=1/FAILURE
paź 02 13:10:04 ideapad520 systemd[985]: dbus-:1.2-org.kde.LogoutPrompt@13.service: Failed with result 'exit-code'.
paź 02 13:10:45 ideapad520 kioslave5[258408]: Qt: Session management error: networkIdsList argument is NULL
paź 02 13:10:47 ideapad520 kwin_x11[1047]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 65415, resource id: 50333889, major code: 3 (GetWindowAttributes), minor code: 0
paź 02 13:10:47 ideapad520 kwin_x11[1047]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 65416, resource id: 50333889, major code: 14 (GetGeometry), minor code: 0
paź 02 13:11:33 ideapad520 systemd-logind[402]: Power key pressed.
paź 02 13:11:33 ideapad520 systemd[985]: Started dbus-:1.2-org.kde.LogoutPrompt@14.service.
paź 02 13:11:34 ideapad520 kwin_x11[1047]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 8347, resource id: 98566190, major code: 18 (ChangeProperty), minor code: 0
paź 02 13:11:34 ideapad520 systemd[985]: dbus-:1.2-org.kde.LogoutPrompt@14.service: Main process exited, code=exited, status=1/FAILURE
paź 02 13:11:34 ideapad520 systemd[985]: dbus-:1.2-org.kde.LogoutPrompt@14.service: Failed with result 'exit-code'.
paź 02 13:11:39 ideapad520 systemd-logind[402]: Power key pressed.
paź 02 13:11:39 ideapad520 systemd[985]: Started dbus-:1.2-org.kde.LogoutPrompt@15.service.
paź 02 13:11:40 ideapad520 kwin_x11[1047]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 9706, resource id: 98566190, major code: 18 (ChangeProperty), minor code: 0
paź 02 13:11:40 ideapad520 systemd[985]: dbus-:1.2-org.kde.LogoutPrompt@15.service: Main process exited, code=exited, status=1/FAILURE
paź 02 13:11:40 ideapad520 systemd[985]: dbus-:1.2-org.kde.LogoutPrompt@15.service: Failed with result 'exit-code'.
Comment 1 David Edmundson 2021-10-03 20:02:12 UTC
Please test with  systemctl suspend
Comment 2 Mariusz Libera 2021-10-04 04:10:12 UTC
(In reply to David Edmundson from comment #1)
> Please test with  systemctl suspend

As I wrote in the report 'systemctl suspend' works every time. Is there something else I can do to help debug this?
Comment 3 Bug Janitor Service 2021-10-19 04:35:45 UTC
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!
Comment 4 Joe Breuer 2021-10-20 17:51:36 UTC
I'm experiencing a similar issue in gentoo intermittently, see:

https://bugs.gentoo.org/818124

It's specifically requesting sleep from the ksmserver-logout-greeter screen that does not cause sleep. Selecting sleep e.g. from the K Menu always works for me.

As detailed in the gentoo bug above, ksmserver-logout-greeter generates different diagnostics for me in the cases where it works vs those where it doesn't.

I do not see my particular culprit in Mariusz' log, though, FWIW.
Comment 5 Nate Graham 2022-07-06 17:35:01 UTC
A lot has changed since then. Can anyone still reproduce this issue in Plasma 5.25?
Comment 6 Mariusz Libera 2022-07-07 08:17:52 UTC
(In reply to Nate Graham from comment #5)
> A lot has changed since then. Can anyone still reproduce this issue in
> Plasma 5.25?

Tried it 10 time and it worked every time.
I'm on Plasma 5.25.2, don't know when it got fixed - I had this logout dialog disabled because of this bug.
Comment 7 Nate Graham 2022-07-07 15:58:58 UTC
Great news!