(Karmic regression) Despite my wishes screen is locked on resume

Bug #454325 reported by Roger Binns
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: gnome-power-manager

On one of my machines I do *not* want to enter a password on resume (from disk or standby). In the attached files you can see I set the appropriate gconf settings and have happily been password prompt free since the days of Feisty. Sadly on upgrade to Karmic I am now repeatedly prompted for a password.

(I can go into the reason why I want it this was if anyone cares. Ultimately it is a usability issue. If there is a workaround to avoid the password prompt such as an empty or null password I'd be happy to take that approach.)

ProblemType: Bug
Architecture: amd64
Date: Sat Oct 17 17:46:38 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: gnome-power-manager 2.28.0-0ubuntu7
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: gnome-power-manager
Uname: Linux 2.6.31-14-generic x86_64

Revision history for this message
Roger Binns (ubuntu-rogerbinns) wrote :
Revision history for this message
Ryan Fugger (rfugger) wrote :

I can confirm this issue. I had intrepid configured to not lock on resume, but after upgrade to karmic, it locks, and nothing in power management preferences or gconf-editor seems to fix it. (Settings remain the same as before.)

Revision history for this message
LarryGrover (lgrover) wrote :

I've experienced this same bug on two systems, one upgraded from 9.04 to 9.10, the other a fresh install of 9.10. If I kill all gnome-screensaver processes before suspending, then the unwanted password request screen does not appear after resuming.

Revision history for this message
Ryan Fugger (rfugger) wrote :

I can confirm that killing gnome-screensaver is a workaround. Could this be related to bug 411350 (gnome-screensaver does not activate)? I have that issue as well.

https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/411350

Revision history for this message
Dave North (north) wrote :

I'm also having the same problem, but it's an intel system (so it's not an AMD thing). Using x4500 graphics subsystem. Also can confirm the problem goes away when the screensaver process is killed.

tags: added: regression-release
Revision history for this message
MoarningSun (slowinthedark) wrote :

please also have a look at bug 501252 and bug 255228

Revision history for this message
Ryan Fugger (rfugger) wrote :

This and bug 501252 should probably be marked as duplicates of bug 255228...?

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. A new version of GNOME Power Manager is available on Maverick and we are wondering if this bug is still an issue for you with that version? Could you please test and comment back? Thanks in advance.

Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Roger Binns (ubuntu-rogerbinns) wrote :

If all Ubuntu does with bugs is wait a year or more after they are confirmed by several people, say "does it still happen" then what exactly is the point of reporting bugs? You obviously aren't going to make any effort to fix or otherwise progress them and are just hoping the progression of time means Launchpad can automatically expire them.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-power-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-power-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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