Ubuntu
xscreensaver package

Closing laptop lid locks even with "lock: False"

Bug #1067140 reported by Alistair Cunningham
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xscreensaver (Ubuntu)
New
Undecided
Unassigned

Bug Description

If I close the lid of my laptop, then open it again, I find it asking for a password even though "lock: False" is set in ~/.xscreensaver (attached). The password window says "XScreenSaver 5.15".

$ lsb_release -rd
Description: Ubuntu 12.10
Release: 12.10

$ apt-cache policy xscreensaver
xscreensaver:
  Installed: 5.15-2ubuntu1
  Candidate: 5.15-2ubuntu1
  Version table:
 *** 5.15-2ubuntu1 0
        500 http://archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages
        100 /var/lib/dpkg/status

I appreciate that this bug might not actually be in xscreensaver. Perhaps something like ACPI is telling it to lock. If so, please re-assign this bug report to the correct package.

Revision history for this message
Alistair Cunningham (acunningham) wrote :
Revision history for this message
Mamoru TASAKA (mtasaka) wrote :

If you can still reproduce this bug, would you try lauching xscreensaver with

$ xscreensaver -verbose -log output_log_name

and attach the contents of output_log_name ?

Revision history for this message
Alistair Cunningham (acunningham) wrote :

Certainly; please see attached. What I did was:

1. Ran "killall xscreensaver" to kill the running xscreensaver.
2. Ran "xscreensaver -verbose -log output_log_name". The splash screen came up.
3. Waited a few seconds.
4. Closed the laptop lid.
5. Waited a few seconds.
6. Opened the lid. The password entry box was displayed.
7. Entered my password. I was logged back in.
8. Waited a few seconds.
9. Hit ctrl-c on xscreensaver.

Revision history for this message
Alistair Cunningham (acunningham) wrote :

I guess this is the key line in the log file:

xscreensaver: 21:17:14: LOCK ClientMessage received; activating and locking.

Presumably something, such as ACPI, is asking xscreensaver to lock rather than activate?

Revision history for this message
Mamoru TASAKA (mtasaka) wrote :

> I guess this is the key line in the log file:
> xscreensaver: 21:17:14: LOCK ClientMessage received; activating and locking.

> Presumably something, such as ACPI, is asking xscreensaver to lock rather than activate?

Probably, from looking at the log.

Revision history for this message
Alistair Cunningham (acunningham) wrote :

Commenting out "LOCK_SCREEN=true" in /etc/default/acpi-support seems to fix this.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

I thought Ubuntu had got rid of acpi-support. Is this an upgraded installation?

Revision history for this message
Alistair Cunningham (acunningham) wrote :

Yes it is. Perhaps I should uninstall this package?

Revision history for this message
Tormod Volden (tormodvolden) wrote :

Yes, try that. Unless something else holds it back (package dependencies), you should be fine without. I don't have acpi-support on my 12.04 Lubuntu.

Revision history for this message
Alistair Cunningham (acunningham) wrote :

Thanks, it's gone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.