Bug 413387 - Unable to unlock after wake up
Summary: Unable to unlock after wake up
Status: RESOLVED DUPLICATE of bug 370676
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: greeter (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-24 11:32 UTC by Arnaud Frézet
Modified: 2021-06-21 22:56 UTC (History)
6 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 Arnaud Frézet 2019-10-24 11:32:10 UTC
SUMMARY

Hi everyone,

I have a strange behavior when my laptop wake up from sleep mode. Like this bug https://bugs.kde.org/show_bug.cgi?id=329076, the widget to enter the password and then unlock the screen is missing, so I am unable to unlock. The clock is visible (but not updated, the time is at when I put the laptop to sleep), the login background too.

The mouse is moving, and the computer does not seem freezed, I can switch between tty, but the widget ket missing. This a quite strange as the bug does not occurs every time. Just a few once...

My laptop is a Dell E7470 with latest KDE Neon (KDE 5.17 et Ubuntu 18.04, built-in Intel HD graphics), with an extra screen (which I think that might cause the issue). Note that the bug does happens in my desktop computer (with nVidia graphics card) or my second laptop (Lenovo with graphics card too).


STEPS TO REPRODUCE
1. Close the laptop to go in sleep mode
2. Open the laptop to wake up
3. The login widget is missing (sometimes)


OBSERVED RESULT
The widget to enter the password in order to unlock the computer desktop is missing.


EXPECTED RESULT
I must be able to see the password widget every time. 


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE Neon 5.17, Ubuntu 18.04
(available in About System)
KDE Plasma Version: 5.17
KDE Frameworks Version: 5.63.0
Qt Version: 5.13.1



ADDITIONAL INFORMATION

I found some logs in KSystemLog which might be suspicious, before I was unable to unlock :

24/10/2019 13:10	pulseaudio	[pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
24/10/2019 13:10	pulseaudio	[pulseaudio] module-gconf.c: pa_module_load() failed
24/10/2019 13:10	pulseaudio	[pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
24/10/2019 13:10	spice-vdagent	Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
24/10/2019 13:10	kernel	uvcvideo 1-2:1.0: Entity type for entity Extension 4 was not initialized!
24/10/2019 13:10	kernel	uvcvideo 1-2:1.0: Entity type for entity Extension 7 was not initialized!
24/10/2019 13:10	kernel	uvcvideo 1-2:1.0: Entity type for entity Processing 2 was not initialized!
24/10/2019 13:10	kernel	uvcvideo 1-2:1.0: Entity type for entity Camera 1 was not initialized!
24/10/2019 13:10	kernel	thermal thermal_zone7: failed to read out thermal zone (-61)
24/10/2019 13:10	udisks2.service	failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
24/10/2019 13:10	udisks2.service	Failed to load the 'mdraid' libblockdev plugin
24/10/2019 13:10	colord.service	failed to get session [pid 968]: Aucune donnée disponible
24/10/2019 13:10	colord.service	failed to get session [pid 968]: Aucune donnée disponible
24/10/2019 13:10	colord.service	failed to get session [pid 968]: Aucune donnée disponible
24/10/2019 13:10	NetworkManager	<warn>  [1571915416.4732] Error: failed to open /run/network/ifstate
24/10/2019 13:10	wpa_supplicant	dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
24/10/2019 13:10	wpa_supplicant	dbus: Failed to construct signal
24/10/2019 13:10	sddm-greeter	QObject: Cannot create children for a parent that is in a different thread.
(Parent is SDDM::GreeterApp(0x7ffccc97a0d0), parent's thread is QThread(0x55ceff014980), current thread is QThread(0x55ceff098de0)
24/10/2019 13:10	sddm-greeter	QObject: Cannot create children for a parent that is in a different thread.
(Parent is SDDM::GreeterApp(0x7ffccc97a0d0), parent's thread is QThread(0x55ceff014980), current thread is QThread(0x55ceff098de0)
24/10/2019 13:10	sddm-greeter	QObject: Cannot create children for a parent that is in a different thread.
(Parent is SDDM::GreeterApp(0x7ffccc97a0d0), parent's thread is QThread(0x55ceff014980), current thread is QThread(0x55ceff098de0)
24/10/2019 13:10	sddm-greeter	QObject::installEventFilter(): Cannot filter events for objects in a different thread.
24/10/2019 13:10	sddm-greeter	Cannot watch QRC-like path ":/icons/hicolor/index.theme"
24/10/2019 13:10	sddm-greeter	Hunspell dictionary is missing for "fr_FR" . Search paths ("/usr/share/qt5/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts")
24/10/2019 13:10	kernel	kauditd_printk_skb: 17 callbacks suppressed
24/10/2019 13:10	NetworkManager	<warn>  [1571915422.9354] device (wlp1s0): No agents were available for this request.





Thank you very much and keep up the good work !

Have a nice day,
Comment 1 Arnaud Frézet 2019-10-24 12:22:17 UTC
Note that the bug only seems to appears with an external monitor connected
Comment 2 Joe 2020-08-03 16:43:52 UTC
I got this issue a lot on my laptop with external monitor and running the Nvidia GPU. I also notice a very small/faint amount of graphical distortion around the frozen clock, which looked a lot like the distortion that was happening everywhere on resume with an nvidia card. I have since switched to enabling NVIDIA prime/optimus and using the intel card as the main driver, and have yet to have any issues.
Comment 3 mjkorhon 2020-11-03 07:06:03 UTC
I have the same bug. This is a desktop with nvidia graphics card. I don't have two monitors - can the greeter still be shown to a non existent monitor, as the card has 3 outputs: hdmi, dvi and display port?
Comment 4 mjkorhon 2020-11-03 07:15:43 UTC
(In reply to mjkorhon from comment #3)
> I have the same bug. This is a desktop with nvidia graphics card. I don't
> have two monitors - can the greeter still be shown to a non existent
> monitor, as the card has 3 outputs: hdmi, dvi and display port?

Note that this is after any unlock, not just awter wake up.
Comment 5 Nate Graham 2021-06-21 22:56:54 UTC

*** This bug has been marked as a duplicate of bug 370676 ***