Bug 10966

Summary:	Gnome 3: Unable to get out of lock screen unless switching user
Product:	Mageia	Reporter:	Nicolas Martin <dev>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
See Also:	https://bugzilla.gnome.org/show_bug.cgi?id=690928
Whiteboard:	4alpha1
Source RPM:		CVE:
Status comment:

Description Nicolas Martin 2013-08-09 21:05:42 CEST

Description of problem:
After locking the screen, the wallpaper is displayed with the current date.
I have to swipe up the wallpaper to get the login window (normal behavior).
Sometimes, the wallpaper will immediately fall back down, preventing me from typing my credentials.
When I manage to get the login window, I type the credentials and see a spinning wheel that does spin forever without resulting in a successful login.

To log me back in, I have to select "Switch user" and type my password.


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


How reproducible:
Systematic

Steps to Reproduce:
1. Start a gnome 3 session
2. Use the top right corner shutdown icon and select the lockpad icon (screen lock)
3. Profit :(


Reproducible: 

Steps to Reproduce:

Comment 1 Nicolas Martin 2013-08-09 21:12:12 CEST

More weird behavior:
I lock the screen and then use the switching user workaround.
Then I lock the screen again.
All I get is a grey screen with only the top right icon displayed (sound, battery etc...).

I can't get out unless by a reboot or switching to a VT

Comment 2 Manuel Hiebel 2013-08-09 22:20:23 CEST

yep tmb just added it to the errata for coming alpha1

seems a consolekit issue

Whiteboard: (none) => 4alpha1

Manuel Hiebel 2013-08-09 22:22:09 CEST

See Also: (none) => https://bugzilla.gnome.org/show_bug.cgi?id=690928

Comment 3 Nicolas Martin 2013-08-09 23:18:47 CEST

Ok thanks for the swift clarification.

Comment 4 Nicolas Martin 2013-08-10 16:59:56 CEST

Looks like a duplicate of 10970

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

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE