Bug 283825

Summary:	Session locked (requiring password) after resume
Product:	[Unmaintained] Active	Reporter:	Thomas Pfeiffer <thomas.pfeiffer>
Component:	General	Assignee:	active
Status:	RESOLVED FIXED
Severity:	major	CC:	javier
Priority:	HI
Version:	unspecified
Target Milestone:	unscheduled
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Thomas Pfeiffer 2011-10-11 21:16:34 UTC

Version:           unspecified (using Devel) 
OS:                Linux

I don't know if it's image-specific, but at least on the meego image when I resume from suspend, I get the standard unlock dialog (with the password) instead of the Active locker, thus being unable to unlock without a keyboard.
But even if I plug a keyboard in and type the password, for some reason I still cannot unlock and have to kill X to log in again.
Could it be because in the power settings, "lock screen on resume" is selected and this uses the wrong locking screen?

Reproducible: Always

Steps to Reproduce:
1. Suspend the device (no matter how you do it, happens in all cases)
2. Resume the device

Actual Results:  
You get the standard lock screen

Expected Results:  
You should get the Active lock effect

I've set this bug to "crash" because even though it's not an actual crash, it's similar in severity as it forces users to restart the system unless they have a keyboard at hand and know how to switch to vt-1 and kill Xorg.

Comment 1 Thomas Pfeiffer 2011-10-11 22:06:01 UTC

If the screen is locked after being idle, the currect lock screen is displayed. The wrong one only happens after resuming form suspend.

Comment 2 Thomas Pfeiffer 2011-10-12 08:15:09 UTC

> -----Original Message-----
> From: active-bounces@kde.org [mailto:active-bounces@kde.org] On Behalf
> Of Stefan Werden
> Sent: Wednesday, October 12, 2011 12:38 AM
> To: bug-control@bugs.kde.org; active@kde.org
> Subject: Re: [Bug 283825] Session locked (requiring password) after resume
> 
> Hi,
> 
> Just check the passwords at
> http://community.kde.org/Plasma/Active/ReleaseNotes/1.0#Known_Issues
> _.2F_Errata
> 
> For the meego image (user/passwd is:
> 
> root -> meego
> meego -> meego
> 
> The open-slx image has no password on the stick
> 
> root -> no password
> linux -> no passord
> 
> Just type in user name + enter
> 
> Hope this helps,
> 
> Stefan

Thanks for the info. I tried these already though - with no luck. When I switched to vt-1,
I could log in with meego / meego, but I could not unlock with it. Plus even if the
password did work, it would still keep users locked out without a physical keyboard present.

Comment 3 Javier Llorente 2011-10-20 07:39:43 UTC

Bug reproducible on 2011-10-18-00-53-meego-plasma-contour-in-progress-USB-live.iso + updates from yesterday (19th). As Thomas says, you can't unlock the screen even using a physical keyboard; it doesn't accept the default password.

Comment 4 Javier Llorente 2011-11-09 15:08:08 UTC

I can't reproduce this bug on my Wetab since some time. Nevertheless, Fania confirms it as well as Martin Brook (vgrade) on the Advent Vega.

Comment 5 Javier Llorente 2011-12-02 11:20:32 UTC

I haven't been able to reproduce this bug since some time. Hence, closing this bug...