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

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:

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.

1 Like