Ubuntu
gnome-power-manager package

resuming from S3 wrongly prompts for password

Bug #578542 reported by marcw on 2010-05-10

This bug affects 4 people

	Status	Importance	Assigned to
Session Menu	Incomplete	Medium	Unassigned
Upower	Won't Fix	Medium	freedesktop-bugs #35797
gnome-power	New	Medium	gnome-bugs #646238
gnome-power-manager (Ubuntu)	New	Low	Phillip Susi
indicator-session (Ubuntu)	Incomplete	Undecided	Phillip Susi
upower (Ubuntu)	New	Undecided	Phillip Susi

Bug Description

Binary package hint: gnome-power-manager

Despite the gconf items
/apps/gnome-power-manager/lock/use_screensaver_settings and
/apps/gnome-power-manager/lock/suspend
both being set to false, I am still prompted for a password when resuming my workstation from S3. I do not want to be prompted. Other than this, my suspend & resume work fine.

Description: Ubuntu 10.04 LTS
Release: 10.04
32 bit
---
Architecture: i386
DistroRelease: Ubuntu 10.04
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Lsusb:
Bus 002 Device 002: ID 0458:0024 KYE Systems Corp. (Mouse Systems)
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 046d:0990 Logitech, Inc. QuickCam Pro 9000
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
NonfreeKernelModules: nvidia
Package: gnome-power-manager 2.30.0-0ubuntu1
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic-pae root=UUID=90fb6769-d9c5-44a0-9aa9-253a95e9bf49 ro quiet splash
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic-pae 2.6.32.15+drm33.5
Tags: lucid
Uname: Linux 2.6.32-24-generic-pae i686
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare vboxusers
dmi.bios.date: 02/26/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FHe
dmi.board.name: M57SLI-S4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFHe:bd02/26/2009:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM57SLI-S4:rvrx.x:cvn:ct3:cvr:

See original description

Tags:

Related branches

lp://staging/~psusi/ubuntu/natty/indicator-session/sleep

Rejected for merging into lp://staging/ubuntu/natty/indicator-session

Chris Halse Rogers: Approve on 2011-03-29

Ubuntu branches: Pending requested 2011-03-19

lp://staging/~psusi/ubuntu/natty/gnome-power-manager/sleep

Rejected for merging into lp://staging/ubuntu/natty/gnome-power-manager

Chris Coulson (community): Disapprove on 2011-04-04

Phillip Susi (community): Needs Resubmitting on 2011-03-29

Chris Halse Rogers: Needs Fixing on 2011-03-29

Ubuntu branches: Pending requested 2011-03-19

lp://staging/~psusi/ubuntu/natty/upower/sleep

Rejected for merging into lp://staging/ubuntu/natty/upower

Chris Coulson (community): Disapprove on 2011-04-04

Evan Broder (community): Disapprove on 2011-03-30

Phillip Susi (community): Needs Resubmitting on 2011-03-29

Chris Halse Rogers: Needs Fixing on 2011-03-29

Ubuntu branches: Pending requested 2011-03-19

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2010-08-18:

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please open a terminal and execute: apport-collect 578542 ? It will attach the necessary information to this report. Thanks in advance.

Changed in gnome-power-manager (Ubuntu):
importance:	Undecided → Low
status:	New → Incomplete

Revision history for this message

marcw (marcw) wrote on 2010-08-18: BootDmesg.txt

BootDmesg.txt Edit (42.2 KiB, text/plain)

apport information

tags:	added: apport-collected
description:	updated

Revision history for this message

marcw (marcw) wrote on 2010-08-18: CurrentDmesg.txt

CurrentDmesg.txt Edit (61.5 KiB, text/plain)

apport information

Revision history for this message

marcw (marcw) wrote on 2010-08-18: Dependencies.txt

Dependencies.txt Edit (5.8 KiB, text/plain)

apport information

Revision history for this message

marcw (marcw) wrote on 2010-08-18: DevkitPower.txt

DevkitPower.txt Edit (167 bytes, text/plain)

apport information

Revision history for this message

marcw (marcw) wrote on 2010-08-18: GConfNonDefault.txt

GConfNonDefault.txt Edit (588 bytes, text/plain)

apport information

Revision history for this message

marcw (marcw) wrote on 2010-08-18: Lspci.txt

Lspci.txt Edit (11.2 KiB, text/plain)

apport information

Revision history for this message

marcw (marcw) wrote on 2010-08-18: ProcCpuinfo.txt

ProcCpuinfo.txt Edit (1.5 KiB, text/plain)

apport information

Revision history for this message

marcw (marcw) wrote on 2010-08-18: ProcInterrupts.txt

ProcInterrupts.txt Edit (1.5 KiB, text/plain)

apport information

Revision history for this message

marcw (marcw) wrote on 2010-08-18: ProcModules.txt

#10

ProcModules.txt Edit (2.4 KiB, text/plain)

apport information

Revision history for this message

marcw (marcw) wrote on 2010-08-18: UdevDb.txt

#11

UdevDb.txt Edit (95.3 KiB, text/plain)

apport information

Revision history for this message

marcw (marcw) wrote on 2010-08-18: UdevLog.txt

#12

UdevLog.txt Edit (207.4 KiB, text/plain)

apport information

Revision history for this message

marcw (marcw) wrote on 2010-08-18: gnome-power-bugreport.txt

#13

gnome-power-bugreport.txt Edit (1.6 KiB, text/plain)

apport information

Revision history for this message

Phillip Susi (psusi) wrote on 2010-09-18:

#14

I have observed the same thing on my laptop.

Changed in gnome-power-manager (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

marcw (marcw) wrote on 2010-09-18:

#15

In the past couple days I've figured out a work around for this issue: I uninstalled gnome-screensaver and installed xscreensaver instead. This seems to have solved the issue. And I get better screens to boot!

Revision history for this message

Phillip Susi (psusi) wrote on 2011-03-07:

#16

It looks like gnome-power-manager is not used to handle suspend any more. Indicator-session appears to directly lock the screen, kick off the screen saver, and ask UPower to transition the system to sleep mode. I can not see any dbus interface being exported by g-p-m to even ask it to suspend, so I guess that interface must have been removed. It does appear to still suspend when it decides the system has been idle long enough to auto suspend.

I think that the gpm interface needs put back and indicator-session needs fixed to call on it instead of handling the locking/screen saver and UPower calls itself. Either that or it needs to only call UPower, and if g-p-m wants to lock the screen then it should monitor for the Suspending signal UPower emits.

Phillip Susi (psusi) on 2011-03-19

Changed in upower (Ubuntu):
assignee:	nobody → Phillip Susi (psusi)
status:	New → In Progress
Changed in indicator-session (Ubuntu):
assignee:	nobody → Phillip Susi (psusi)
status:	New → In Progress
Changed in gnome-power-manager (Ubuntu):
assignee:	nobody → Phillip Susi (psusi)
status:	Confirmed → In Progress

Revision history for this message

Ted Gould (ted) wrote on 2011-03-21:

#17

Adding an indicator-session task with it marked as "incomplete" to see if the other patches get merged as it effects how this should be accepted. I think this is the right approach, but there are a couple of dependencies here.

Changed in indicator-session:
assignee:	nobody → Ted Gould (ted)
importance:	Undecided → Medium
status:	New → Incomplete

Revision history for this message

In freedesktop.org Bugzilla #35797, Michael Terry (mterry) wrote on 2011-03-30:

#19

Created attachment 45048
Adds signal arg

In Ubuntu, we got a bug filed about how suspends initiated outside of gnome-power-manager were not locking the screen correctly.

This is because it handled locking as a result of internal methods, not as a response to the Sleeping signal from upower. Ideally it would do that instead, but first, that signal needs to have enough information for a policy agent like gnome-power-manager to determine policy.

Which means it needs to tell listeners whether the sleep is a suspend or hibernate.

We received a patch for this by Phillip Susi (attached). It simply adds an int argument to the signal. Will existing dbus listeners be confused by the addition of a new argument?

Revision history for this message

In freedesktop.org Bugzilla #35797, Richard Hughes (richard-hughes) wrote on 2011-03-30:

#20

Yup, see http://lists.freedesktop.org/archives/devkit-devel/2011-March/001054.html

And yes, adding an argument will upset people.

Revision history for this message

In freedesktop.org Bugzilla #35797, Michael Terry (mterry) wrote on 2011-03-30:

#21

Ah, sorry, searched bugs, but didn't think about the mailing list.

What about a second signal, named "SleepingFull" or something?

Revision history for this message

In freedesktop.org Bugzilla #35797, Richard Hughes (richard-hughes) wrote on 2011-03-30:

#22

SleepingFull might be best, I though perhaps Sleeping2, but both seem non-ideal. Got any better ideas?

Richard.

Revision history for this message

In freedesktop.org Bugzilla #35797, Michael Terry (mterry) wrote on 2011-03-30:

#23

The only alternative to a second signal I can think of is a query method like GetCurrentSleepType(), but that's a whole 'nother round trip eating into the precious second before suspend (I don't know how much of a concern that is).

Revision history for this message

In freedesktop.org Bugzilla #35797, Michael Terry (mterry) wrote on 2011-03-30:

#24

Oh, I think you meant naming ideas? SleepingWithType?

Revision history for this message

In freedesktop.org Bugzilla #35797, Richard Hughes (richard-hughes) wrote on 2011-03-30:

#25

(In reply to comment #4)
> The only alternative to a second signal I can think of is a query method like
> GetCurrentSleepType(), but that's a whole 'nother round trip eating into the
> precious second before suspend (I don't know how much of a concern that is).

Eek. RTT is probably too high for that. Even setting a property might be racy, I'm not sure. A PropertyChanged signal in GDBus is run in a new thread, and I'm not sure how it works when we're using the clunky dbus-glib.

At the moment I'm erring for ::SleepingKind and ::ResumingKind as we call things kinds internally (rather than type, which upsets glib sometimes).

Revision history for this message

Michael Terry (mterry) wrote on 2011-03-30:

#18

I filed upstream bugs with your patches, Phillip. I think upstream should probably greenlight such patches, as the new dbus signal argument will likely impact all listeners to that signal.

Bug Watch Updater (bug-watch-updater) on 2011-03-30

Changed in upower:
importance:	Unknown → Medium
status:	Unknown → Confirmed
Changed in gnome-power:
importance:	Unknown → Medium
status:	Unknown → New

Conor Curran (cjcurran) on 2011-09-01

Changed in indicator-session (Ubuntu):
status:	In Progress → Incomplete

Ted Gould (ted) on 2012-09-28

Changed in indicator-session:
assignee:	Ted Gould (ted) → nobody

Revision history for this message

In freedesktop.org Bugzilla #35797, Bugzilla-x (bugzilla-x) wrote on 2013-10-12:

#26

The Sleeping signal is deprecated, and removed in my branch. We won't get a new signal.

Bug Watch Updater (bug-watch-updater) on 2013-10-13

Changed in upower:
status:	Confirmed → Won't Fix

Charles Kerr (charlesk) on 2014-03-14

Changed in gnome-power-manager (Ubuntu):
status:	In Progress → New
Changed in upower (Ubuntu):
status:	In Progress → New

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

gnome-bugs #646238
[UNCONFIRMED] Edit
freedesktop-bugs #35797
[RESOLVED WONTFIX] Edit

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

Ubuntugnome-power-manager package

resuming from S3 wrongly prompts for password

Bug Description

Related branches

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
gnome-power-manager package