Bug 8197

Summary:	Unable to unlock with password after xscreensaver starts
Product:	Mageia	Reporter:	Drew Edwards <drew>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	mageia, philippel, rwobben
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Bug Depends on:	7687
Bug Blocks:

Description Drew Edwards 2012-11-25 05:07:17 CET

Description of problem:
Using xfce on up-to-date x86-64 cauldron installation (lenovo thinkpad x120e).  When xscreensaver kicks in (after closing and then opening the laptop) and locks the screen it will not accept the correct password to unlock.  Can only get back to usable desktop by hitting ctrl-alt-backspace and logging in again.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Comment 1 Drew Edwards 2012-12-18 06:48:53 CET

Still present.

Comment 2 Drew Edwards 2012-12-18 06:50:08 CET

still present.  Not limited to xfce, also observed in razorqt desktop when xscreensaver starts.

Comment 3 Manuel Hiebel 2012-12-25 14:38:25 CET

and what is you dm ? gdm ?
can be a dup of bug 7687 

(there is some 'workaround' you could try them if it works)

Keywords: (none) => NEEDINFO

Comment 4 roelof Wobben 2013-01-09 07:52:05 CET

@Drew : Can you give a respons to comment 3.

Roelof

CC: (none) => r.wobben

Comment 5 Drew Edwards 2013-01-12 17:58:01 CET

kdm (sorry for the delay)

I have not observed this in gnome.

Comment 6 Manuel Hiebel 2013-01-18 23:12:06 CET

colin, maybe you have some ideas ? (i remember we have also a bug for kde beside gnome)

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

Comment 7 Drew Edwards 2013-01-26 16:38:16 CET

Still present after fresh install of Beta 2.

Manuel Hiebel 2013-01-29 21:50:55 CET

Depends on: (none) => 7687

Comment 8 Philippe Leblanc 2013-02-28 16:18:45 CET

Still present in fully up to date cauldron as of today.

CC: (none) => philippe.l

Comment 9 Colin Guthrie 2013-06-13 23:18:01 CEST

Sorry I missed updates to this bug. Is this still happening with mga3? I know I fixed a few issues with various DEs relating to pam registrations but not sure if this would help in this case.

Comment 10 Drew Edwards 2014-01-17 02:27:34 CET

Closing as this was resolved some time ago.

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