Bug 20679

Summary:	unlock screen frozen after password validation (killing ksmserver makes logging in possible again)
Product:	Mageia	Reporter:	Antonin Roussel <antonin.roussel>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	fri, marja11
Version:	6
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	libkscreen ??	CVE:
Status comment:
Attachments:	journal excerpt - bug seen around 16:47:46 journal excerpt - bug seen around 11:08 journal excerpt - bug seen at 06:57 3 gdb backtraces following ksmserver kwrapper5 plasmashell

Description Antonin Roussel 2017-04-15 18:45:43 CEST

Description of problem:
When I left my computer alone, it goes to black screen, waiting for me to come back and give my password. But sometimes after validating the password, I'm stuck on the screen with the password filled. The mouse is alive, nothing reacts but tty.
After login, I noticed that my firefox browser was not on the page I left it with. So, I think, the frozen screen allowed me to click in this application despite what I saw (My history timeline proves it).
I don't know how to dig further in this bug... which logs could help you ?


Version-Release number of selected component (if applicable):


How reproducible:
Sometimes (about 5 times since months)

Steps to Reproduce:
1. let your screen lock (for instance after 5min) and let it wait for a password from you to unlock (5s)
2. If you wait long enough, the screen may become dark
3. Once you want to use the computer again, a prompt ask you a password, you fill it, and validate.
4. nothing seems happening, like frozen on the prompt screen, password filled.
5. It's still possible to get on tty2, ended to kill kmserver or session to manage to login again.

Comment 1 Marja Van Waes 2017-04-16 11:47:09 CEST

kmserver?

I can't find that one. Should that maybe be ksmserver?

Which desktop environment do you use?

Keywords: (none) => NEEDINFO
CC: (none) => marja11

Comment 2 Antonin Roussel 2017-04-16 12:07:01 CEST

You are right, ksmserver, environment KDE/Plasma

EDIT How reproducible:
Sometimes (about 5 times since 1 month)

Comment 3 Marja Van Waes 2017-04-17 13:48:07 CEST

(In reply to Antonin Roussel from comment #2)
> You are right, ksmserver, environment KDE/Plasma
> 
> EDIT How reproducible:
> Sometimes (about 5 times since 1 month)


When it happens again, can you then please login in tty2, become root, and run

    journalctl -ab > journal.txt


Please attach journal.txt to this bug report.

Assignee: bugsquad => kde
Summary: unlock screen frozen after password validation => unlock screen frozen after password validation (killing ksmserver makes logging in possible again)

Comment 4 Antonin Roussel 2017-04-17 20:12:22 CEST

As I remind the bug was at 16:48 the 15th, my command was :
journalctl -a -S2017-04-15\ 16:00 -U2017-04-15\ 18:00 > journalctl_20170415T1600-1800.txt
please find the file attached

Comment 5 Antonin Roussel 2017-04-17 20:17:12 CEST

Created attachment 9213 [details]
journal excerpt - bug seen around 16:47:46

In my browser history, I have blind clicked links at 16:48

Comment 6 Marja Van Waes 2017-04-19 09:19:52 CEST

(In reply to Antonin Roussel from comment #5)
> Created attachment 9213 [details]
> journal excerpt - bug seen around 16:47:46

So where those lines are repeated over 30 times:

avril 15 16:47:46 myhome.here.fr kscreen_backend_launcher[7658]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
avril 15 16:47:46 myhome.here.fr kscreen_backend_launcher[7658]: kscreen.xcb.helper: 	Output:  66
avril 15 16:47:46 myhome.here.fr kscreen_backend_launcher[7658]: kscreen.xcb.helper: 	Property:  Backlight
avril 15 16:47:46 myhome.here.fr kscreen_backend_launcher[7658]: kscreen.xcb.helper: 	State (newValue, Deleted):  0

(Assigning this report to libkscreen, even if those lines might be a red herring)

> 
> In my browser history, I have blind clicked links at 16:48

Thanks for the feedback.

Keywords: NEEDINFO => (none)
Source RPM: (none) => libkscreen ??

Comment 7 Antonin Roussel 2017-04-27 11:38:35 CEST

Created attachment 9229 [details]
journal excerpt - bug seen around 11:08

The mageia cauldron was updated and rebooted around 10:00
The bug happened again at 11:08
I left the computer alone, and when I came back I could not login... Ctrl+Alt+Backspace to start a new session
journalctl -a -S2017-04-27\ 11:50 -U2017-04-27\ 11:09:40 > journalctl_20170427T115000-110940.txt

Comment 8 Antonin Roussel 2017-06-10 07:24:18 CEST

Created attachment 9398 [details]
journal excerpt - bug seen at 06:57

Very light journal excerpt, showing what can be seen when the login screen freezes. Since one day got stuck 3 times

Comment 9 Antonin Roussel 2017-09-13 15:34:57 CEST

Still happening, I now suspect it to be caused by :
- too many applications running along a greedy boinc-client, or 
- some GTK or Python interferences (opt firefox profil 1, opt firefox profil 2, jbrout (python))

If this can help catch this mysterious bug...

I'm not in cauldron anymore so switched Mageia version

Version: Cauldron => 6

Comment 10 Antonin Roussel 2018-01-05 19:23:53 CET

Created attachment 9880 [details]
3 gdb backtraces following ksmserver kwrapper5  plasmashell

Still happening. I've put some tty with gdb to try to see something interesting...

Attached file gives the end of 3 gdb backtraces. 

When the bug happened, nothing was visible. So I Ctrl+Alt+Backspace my frozen locked session. Then the first backtrace was more verbose (tty2). Every gdb has to be continued several times until errors flow stop (from 0 to 3-4 times)
Then Restarting a new session, gives sometimes a bit more errors, making gdb need to be continued on some tty.

Comment 11 Morgan Leijström 2019-12-31 15:22:17 CET

Mageia 6 is EOL.

Please reopen or open a new bug if you see this again.

Status: NEW => RESOLVED
CC: (none) => fri
Resolution: (none) => OLD