[Solved] Screen remains black after screensaver, system is responsive

shuruper · 2022-09-22 17:08:37

Hi there,

I'm experiencing the following issue:
leave my laptop for a while (locked or logged in to plasma X11 session - doesn't matter), screensaver goes on and when I'm back and do something to activate it back - I do see cursor (so it is not about brightness), but nothing else - screen remains black. I can start terminal and do a reboot to get everything working again, but how do I solve this?

here some logs from journalctl -b -1 where I can't see anything but idling pc which then reboots after I start konsole.

Sep 22 12:42:14 ganjArch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=auto_share comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? te>
Sep 22 12:42:14 ganjArch kernel: audit: type=1130 audit(1663864934.671:283): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=auto_share comm="systemd" exe="/usr/lib/systemd/s>
Sep 22 12:43:00 ganjArch rtkit-daemon[1145]: Supervising 8 threads of 5 processes of 1 users.
Sep 22 12:43:00 ganjArch rtkit-daemon[1145]: Supervising 8 threads of 5 processes of 1 users.
Sep 22 12:43:01 ganjArch systemd[1]: Starting Automount NFS shares...
Sep 22 12:43:15 ganjArch systemd[1]: auto_share.service: Main process exited, code=exited, status=32/n/a
Sep 22 12:43:15 ganjArch systemd[1]: auto_share.service: Failed with result 'exit-code'.
Sep 22 12:43:15 ganjArch systemd[1]: Failed to start Automount NFS shares.
Sep 22 12:43:15 ganjArch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=auto_share comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? te>
Sep 22 12:43:15 ganjArch kernel: audit: type=1130 audit(1663864995.165:284): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=auto_share comm="systemd" exe="/usr/lib/systemd/s>
Sep 22 12:43:42 ganjArch rtkit-daemon[1145]: Supervising 8 threads of 5 processes of 1 users.
Sep 22 12:43:42 ganjArch rtkit-daemon[1145]: Supervising 8 threads of 5 processes of 1 users.
Sep 22 12:44:01 ganjArch systemd[1]: Starting Automount NFS shares...
Sep 22 12:44:15 ganjArch systemd[1]: auto_share.service: Main process exited, code=exited, status=32/n/a
Sep 22 12:44:15 ganjArch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=auto_share comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? te>
Sep 22 12:44:15 ganjArch systemd[1]: auto_share.service: Failed with result 'exit-code'.
Sep 22 12:44:15 ganjArch systemd[1]: Failed to start Automount NFS shares.
Sep 22 12:44:15 ganjArch kernel: audit: type=1130 audit(1663865055.173:285): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=auto_share comm="systemd" exe="/usr/lib/systemd/s>
Sep 22 12:44:16 ganjArch rtkit-daemon[1145]: Supervising 8 threads of 5 processes of 1 users.
Sep 22 12:44:16 ganjArch rtkit-daemon[1145]: Supervising 8 threads of 5 processes of 1 users.
Sep 22 12:44:59 ganjArch dbus-daemon[326]: [system] Activating service name='org.kde.powerdevil.backlighthelper' requested by ':1.68' (uid=1000 pid=928 comm="/usr/lib/org_kde_powe>
Sep 22 12:44:59 ganjArch dbus-daemon[326]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
Sep 22 12:45:00 ganjArch systemd[1]: Starting Automount NFS shares...
Sep 22 12:45:14 ganjArch systemd[1]: auto_share.service: Main process exited, code=exited, status=32/n/a
Sep 22 12:45:14 ganjArch systemd[1]: auto_share.service: Failed with result 'exit-code'.
Sep 22 12:45:14 ganjArch systemd[1]: Failed to start Automount NFS shares.
Sep 22 12:45:14 ganjArch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=auto_share comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? te>
Sep 22 12:45:14 ganjArch kernel: audit: type=1130 audit(1663865114.424:286): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=auto_share comm="systemd" exe="/usr/lib/systemd/s>
Sep 22 12:45:36 ganjArch kstart5[11470]: Omitting both --window and --windowclass arguments is not recommended
Sep 22 12:45:36 ganjArch kglobalaccel5[11470]: 11473
Sep 22 12:45:36 ganjArch systemd[725]: Started Konsole - Terminal.
Sep 22 12:45:36 ganjArch kwin_x11[882]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50678, resource id: 67108874, major code: 18 (ChangeProperty), minor code: 0
Sep 22 12:45:36 ganjArch kwin_x11[882]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 50690, resource id: 67108875, major code: 18 (ChangeProperty), minor code: 0
Sep 22 12:45:39 ganjArch systemd-logind[329]: System is rebooting.
Sep 22 12:45:39 ganjArch plasmashell[901]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x5557a2ce6600) QQmlContext(0x5557a0cda040) QUrl("file:///usr/share/plasma/plasmoid>
Sep 22 12:45:39 ganjArch systemd[1]: Stopping Session 2 of User ganja...
Sep 22 12:45:39 ganjArch plasmashell[901]: Could not find the Plasmoid for Plasma::FrameSvgItem(0x5557a2ce6600) QQmlContext(0x5557a0cda040) QUrl("file:///usr/share/plasma/plasmoid>
Sep 22 12:45:39 ganjArch bluetoothd[424]: Terminating

Last edited by shuruper (2022-09-23 18:10:54)

seth · 2022-09-22 21:38:41

What if you suspend the compositor (SHIFT+alt+F12)?

I can start terminal

You mean konsole? How? Can you see the terminal or do you operate it blindly?
Are the plasmashell and kwin_x11 processes still running when this happens?

shuruper · 2022-09-23 14:05:32

I'll try SHIFT+alt+F12 next time this happens.

Regarding konsole - yes, I do operate it blindly and all the processes are running. It just looks like as if I turned my screen off and that's it. Which is not the case, however, since I can see cursor running on the screen.

seth · 2022-09-23 15:11:32

Symptoms raise my confidence that it's an issue w/ the compositor.
I assume what happens is that the output unregisters, the GL context shrinks into 0x0 and when the output re-appears, the GL context doesn't get grown.
Depending on the cause for the latter you might have to kill the kwin_x11 process (if it's stuck in a live-lock)

shuruper · 2022-09-23 18:10:35

Seems like you were right (as far as I can tell), but the problem was coming from a different source - xf86-video-intel driver, which is removed now and after a few tests my screen is always able to get back.
Thanks!

Arch Linux

#1 2022-09-22 17:08:37

[Solved] Screen remains black after screensaver, system is responsive

#2 2022-09-22 21:38:41

Re: [Solved] Screen remains black after screensaver, system is responsive

#3 2022-09-23 14:05:32

Re: [Solved] Screen remains black after screensaver, system is responsive

#4 2022-09-23 15:11:32

Re: [Solved] Screen remains black after screensaver, system is responsive

#5 2022-09-23 18:10:35

Re: [Solved] Screen remains black after screensaver, system is responsive

Board footer