Bug 872668

Summary:	Lock screen stops responding
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Olaf Hering <ohering>
Component:	GNOME	Assignee:	E-mail List <gnome-bugs>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	badshah400, dimstar, mcatanzaro, ohering, roger.luedecke
Version:	13.2 Milestone 0
Target Milestone:	---
Hardware:	x86-64
OS:	Linux
Whiteboard:
Found By:	Outsourced Testing	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	bug872668.tar.xz journalctl-b.txt My hardware profile

Description Olaf Hering 2014-04-09 06:34:51 UTC

This is with current factory, but I'm 100% sure this already happend several times "last year".

If the screensaver is active, and the mouse is moved the gnome screensaver thing requires to either "move the thing up" (to simulate a touchpad), or its required to press space for example.
While requirering this action, some up-arrows are displayed.

Sometimes the whole thing is stuck, does not react to mouse or keyboard. Right now its 08:30, but the time shown is still 08:20. I'm sure it did not take me 10 minutes to recognize the bug and starting to report it here. Perhaps the bug is not triggered by moving the mouse/pressing space. 

I dont have a testcase.

/home/olaf/.xsession-errors, /var/log/Xorg.0.log and ps faux will be attached.

Comment 1 Olaf Hering 2014-04-09 06:39:22 UTC

Created attachment 585597 [details]
bug872668.tar.xz

Some logs.

Alt+F1 to switch to console, then Alt+Right several times to get back to vt7 just gives a black screen with mouse. Still no reaction.

Could be that X11 is stuck? No idea where to look. Will leave it running until noon in case someone has a quick idea.

Comment 2 Olaf Hering 2014-04-09 06:43:06 UTC

Created attachment 585598 [details]
journalctl-b.txt

Hah, /var/log/messages is dead since months. nice trick, lack of upstream testing...

Comment 3 Atri Bhattacharya 2014-04-09 06:46:29 UTC

I see this while testing GNOME 3.12 on openSUSE 13.1 as well. Guess this is a
general GNOME 3.12 issue. I am trying to see if there is a definite something
that triggers the freeze, but no candy so far.

Olaf, I see the issue occur when there are notifications shown on the
gnome-shell locked screen "curtain". Did you have notifications on the locked
screen when this happened as well?

Comment 4 Olaf Hering 2014-04-09 06:53:25 UTC

I think its the Audiocd thing from bug#872575, which may be still active. Cant tell for sure, but most likely its still present as I did not "accept the notification".

Comment 5 Dominique Leuenberger 2014-10-04 16:13:19 UTC

Olaf,

Do you actually still see that one? I know a long time passed, and due to the (surprisingly, for this kind of bug) low reports of similar bugs (actually, I'm not aware of any dup), this went a bit unnoticed.

As we now have GNOME 3.14 in Factory, there was certainly a lot of change since you reported this and your feedback is most welcome.

Comment 6 Roger Luedecke 2014-10-14 07:48:26 UTC

I have this very same problem. I had thought it was resolved in update to RC1, but after reinstalling RC2 it has returned.

Comment 7 Roger Luedecke 2014-10-14 07:50:27 UTC

Created attachment 609941 [details]
My hardware profile

This is my hardware information since this bug affects me too.

Comment 8 Atri Bhattacharya 2014-10-14 08:04:38 UTC

Please do not adjust the Priority of the bug if you are not the developer working on it. The Priority field is "...set by a member of a development team. Priority may suggest the order the developer will work on bugs." [see https://bugzilla.opensuse.org/page.cgi?id=importance_matrix.html ].

Comment 9 Roger Luedecke 2014-10-14 17:51:01 UTC

Apologies. I've not participated in testing in some time and have forgotten things.

The lockscreen issue seems to have resolved itself again. However, since the behavior is mysterious it could still pop up again.

What is the NEEDINFO? Perhaps I can supply.

Comment 10 Olaf Hering 2014-10-29 16:26:37 UTC

Lets assume its fixed in 13.2

Comment 11 Roger Luedecke 2014-10-29 17:49:13 UTC

(In reply to Olaf Hering from comment #10)
> Lets assume its fixed in 13.2

If we're shipping with 3.14, then yes it'd be fixed.