Screen locker: Must switch to virtual console and back to get password dialog

Help
,
1

Hello!

I’ve just started to get a very weird behavior on the lock screen.

If I just lock the session from the K-menu and immediately move my mouse, the password dialog will be displayed as normal and I can login without any issue.

But If I start from suspend, or if the computer has been idling for a longer time, the screen starts up and I get the wallpaper + the clock, but no password dialog:

test
test1920×1080 86 KB

But if I switch to a virtual terminal (Ctrl + Alt +F1) and then back again, the password box appears as nothing has happened.

Here is the journal log from when I first moved the mouse, until I could login successfully:

jul 09 22:34:09 ThinkStation rtkit-daemon[845]: Supervising 5 threads of 3 processes of 1 users.
jul 09 22:34:09 ThinkStation rtkit-daemon[845]: Successfully made thread 6303 of process 928 owned by '1000' RT at priority 5.
jul 09 22:34:09 ThinkStation rtkit-daemon[845]: Supervising 6 threads of 3 processes of 1 users.
jul 09 22:34:09 ThinkStation kded6[863]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor"
jul 09 22:34:09 ThinkStation kmix[1096]: org.kde.kmix: No such icon "audio-card-pci"
jul 09 22:34:09 ThinkStation kmix[1096]: org.kde.kmix: No such icon "audio-card-pci"
jul 09 22:34:09 ThinkStation kmix[1096]: org.kde.kmix: No such icon "audio-card-pci"
jul 09 22:34:09 ThinkStation kmix[1096]: adding 4 mixers
jul 09 22:34:09 ThinkStation kmix[1096]: mixer "PulseAudio::Playback_Devices:1" "Playback Devices"
jul 09 22:34:09 ThinkStation kmix[1096]: PulseAudio adding 3 devices
jul 09 22:34:09 ThinkStation kmix[1096]: adding "alsa_output.pci-0000_00_1b.0.analog-stereo" "Built-in Audio Analog Stereo"
jul 09 22:34:09 ThinkStation kmix[1096]: adding "alsa_output.pci-0000_03_00.1.hdmi-stereo" "GM107 High Definition Audio Controller [GeForce 940MX] Digital Stereo (HDMI)"
jul 09 22:34:09 ThinkStation kmix[1096]: adding "alsa_output.pci-0000_03_00.1.hdmi-stereo" "GM107 High Definition Audio Controller [GeForce 940MX] Digital Stereo (HDMI)"
jul 09 22:34:09 ThinkStation kmix[1096]: mixer "PulseAudio::Capture_Devices:1" "Capture Devices"
jul 09 22:34:09 ThinkStation kmix[1096]: PulseAudio adding 0 devices
jul 09 22:34:09 ThinkStation kmix[1096]: mixer "PulseAudio::Playback_Streams:1" "Playback Streams"
jul 09 22:34:09 ThinkStation kmix[1096]: PulseAudio adding 4 devices
jul 09 22:34:09 ThinkStation kmix[1096]: mixer "PulseAudio::Capture_Streams:1" "Capture Streams"
jul 09 22:34:09 ThinkStation kmix[1096]: PulseAudio adding 0 devices
jul 09 22:34:09 ThinkStation kmix[1096]: org.kde.kmix: No such icon "audio-card-pci"
jul 09 22:34:09 ThinkStation kmix[1096]: org.kde.kmix: No such icon "audio-card-pci"
jul 09 22:34:09 ThinkStation kmix[1096]: org.kde.kmix: No such icon "audio-card-pci"
jul 09 22:34:09 ThinkStation plasmashell[895]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b.0.analog-stereo.monitor"
jul 09 22:34:27 ThinkStation kscreenlocker_greet[5428]: QRhiGles2: Context is lost.
jul 09 22:34:27 ThinkStation kscreenlocker_greet[5428]: Graphics device lost, cleaning up scenegraph and releasing RHI
jul 09 22:34:40 ThinkStation google-chrome-stable[1407]: [0709/223440.658226:ERROR:file_io_posix.cc(153)] open /home/emil/.config/google-chrome/Crash Reports/pending/18669a85-237b-4537-aff9-540aec06f235.lock: File exist>
jul 09 22:34:49 ThinkStation kscreenlocker_greet[5428]: QRhiGles2: Context is lost.
jul 09 22:34:49 ThinkStation kscreenlocker_greet[5428]: Failed to create RHI (backend 2)
jul 09 22:35:01 ThinkStation kscreenlocker_greet[5428]: QRhiGles2: Context is lost.
jul 09 22:35:01 ThinkStation kscreenlocker_greet[5428]: Graphics device lost, cleaning up scenegraph and releasing RHI
jul 09 22:35:01 ThinkStation kscreenlocker_greet[5428]: QRhiGles2: Context is lost.
jul 09 22:35:01 ThinkStation kscreenlocker_greet[5428]: Failed to create RHI (backend 2)

I can add that this has always been somewhat sketchy. Earlier the lock screen has just frozen some times, or the screen has been just black. But that might only have occurred at maybe 1 of 50 startups.

But since last update (running Arch linux) this behavior is consistent.

I guess its a bug somewhere, but would like to have some more input before submitting.

2 Likes
2

Im getting a very similar behaviour. I posted bug #489846 in the KDE bugzilla

For me, waiting about 20 seconds or so makes it show up. Does not happen under Wayland, only X11.

1 Like
3

haha, what a coincidence! I actually switched to Wayland a few days ago, and there kscreenlocker is working for me as well.

However, now the screen is artifacting after resume instead:
See my thread “screen-is-artifacting-after-resume-on-wayland/18896” (can’t post links)

But your bug report looks very similar to my issue. My lockscreen was actually behaving like yours earlier (1 year +), but now the password dialog does not show up at all (except after switching to a VC).

4

Sounds similar to 483163 – On X11 with compositing turned on, blank screen on lock screen when using Breeze Plasma style
Can you try to set your plasma style (not global theme) to either breeze dark or breeze light (not follows color scheme) and see if it works?

5

I can try that soon. For what it’s worth though I don’t think it will make a difference because I don’t have composting turned on in X11.

6

I’m having the same issue with X11 sessions. I’m already using the breeze dark plasma style.

7

Same issue here under X11, and I’ using Breeze Dark.

8

I am actually already on Breeze Dark, too.
I tried the workaround of switching TTYs. I can get into a TTY but then switching back actually freezes it at the TTY screen until it responds and loads the lock screen again (but when it does, it’s responsive). So it looks like, while it was freezing the lock screen before, its now freezing it at the TTY because switching back to the graphical TTY freezes the display again.

I’m using Nvidia proprietary drivers 555.58.

9

Hello there,

Same thing here. Happens every time that screen goes to sleep and wakes. I think that’s something related with the latest nvidia driver update but I’m not sure.

The weird things that I see is:

Jul 24 14:28:29 muspelheim kwin_x11[26721]: QRhiGles2: Context is lost.
Jul 24 14:28:29 muspelheim kwin_x11[26721]: QRhiGles2: Context is lost.
Jul 24 14:28:29 muspelheim firefox[5262]: [GFX1-]: Detect DeviceReset DeviceResetReason::NVIDIA_VIDEO DeviceResetDetectPlace::WR_POST_UPDATE in Parent process
Jul 24 14:28:29 muspelheim firefox[5262]: [GFX1-]: Failed to make render context current during destroying.
Jul 24 14:28:30 muspelheim kscreenlocker_greet[41501]: QRhiGles2: Context is lost.
Jul 24 14:28:30 muspelheim kscreenlocker_greet[41501]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jul 24 14:28:30 muspelheim kscreenlocker_greet[41501]: QRhiGles2: Context is lost.
Jul 24 14:28:30 muspelheim kscreenlocker_greet[41501]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jul 24 14:28:30 muspelheim plasmashell[4528]: QRhiGles2: Context is lost.
Jul 24 14:28:30 muspelheim plasmashell[4528]: Graphics device lost, cleaning up scenegraph and releasing RHI

Edit: ArchLinux/KDE6 latest kernel (6.10.0)

10

The same thing. I start to type password, the screen turns on but time is stalled, after about 20 secs everything goes well.

OS: Arch Linux x86_64
Kernel: Linux 6.10.1-arch1-1
DE: KDE Plasma 6.1.3
WM: KWin (X11)
GPU: NVIDIA GeForce GTX 980 [Discrete] (proprietary driver installed)

Jul 27 10:36:53 archlinux kwin_x11[1850]: kwin_core: XCB error: 3 (BadWindow), sequence: 14868, resource id: 60817431, major code: 129 (SHAPE), minor code: 6 (Input)
Jul 27 10:36:53 archlinux kwin_x11[1850]: kwin_core: XCB error: 152 (BadDamage), sequence: 14867, resource id: 21201404, major code: 143 (DAMAGE), minor code: 2 (Destroy)
Jul 27 10:36:53 archlinux kernel: Code: 61 38 00 0f 1f 40 00 f3 0f 1e fa 55 48 89 e5 41 54 53 48 83 ec 30 4c 8b 67 08 64 48 8b 1c 25 28 00 00 00 48 89 5d e8 48 89 fb <49> 8b bc 24 80 00 00 00 48 85 ff 74 5f 48 8b 07 ff 50 58 84 c0 74
Jul 27 10:36:53 archlinux kernel: QSGRenderThread[32104]: segfault at 80 ip 00007f5bc98ada63 sp 00007f5b92bff9f0 error 4 in libQt6Gui.so.6.7.2[4ada63,7f5bc94d9000+618000] likely on CPU 3 (core 3, socket 0)
Jul 27 10:36:53 archlinux kscreenlocker_greet[32073]: Failed to create RHI (backend 2)
Jul 27 10:36:53 archlinux kscreenlocker_greet[32073]: QRhiGles2: Context is lost.
Jul 27 10:36:53 archlinux kscreenlocker_greet[32073]: Graphics device lost, cleaning up scenegraph and releasing RHI
Jul 27 10:36:53 archlinux kscreenlocker_greet[32073]: QRhiGles2: Context is lost.
11

I’m also experiencing the same issue, I think the following bug that was reported matched up kde bug 490649 so far I’ve also tried swapping themes around, even lockscreen themes and no improvements in behavior. Also running X11 and latest Nvidia Drivers.

12

Same problem. Running x86_64 Arch with latest Nvidia drivers.

13

Yep, still experiencing this issue. It really needs to be resolved, at the very least it would be nice to get some acknowledgement from a developer that it’s actually a problem.

14

Just to make sure discussion here is connected to the right bug - I think this is the pertinent report? 483094 – On X11 with AMD or NVIDIA GPU, after monitor wake-up, unlocking the screen is delayed by 30-60 seconds

I wanted to at least post that link here as I hadn’t seen it come up yet directly - and if that does reflect what folks in this topic are experiencing, then that would be a good place to add any additional diagnostic info that might help.

1 Like
15

That’s the exact bug I’m experiencing here John, thanks for the feedback.

I might see if I can add to the list of reports.