Launchpad has imported 8 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=35797.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2011-03-30T07:34:48+00:00 Michael Terry wrote: 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? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/578542/comments/18 ------------------------------------------------------------------------ On 2011-03-30T08:05:44+00:00 Richard Hughes wrote: Yup, see http://lists.freedesktop.org/archives/devkit- devel/2011-March/001054.html And yes, adding an argument will upset people. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/578542/comments/19 ------------------------------------------------------------------------ On 2011-03-30T08:12:38+00:00 Michael Terry wrote: Ah, sorry, searched bugs, but didn't think about the mailing list. What about a second signal, named "SleepingFull" or something? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/578542/comments/20 ------------------------------------------------------------------------ On 2011-03-30T10:14:13+00:00 Richard Hughes wrote: SleepingFull might be best, I though perhaps Sleeping2, but both seem non-ideal. Got any better ideas? Richard. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/578542/comments/21 ------------------------------------------------------------------------ On 2011-03-30T10:17:54+00:00 Michael Terry wrote: 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). Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/578542/comments/22 ------------------------------------------------------------------------ On 2011-03-30T10:18:59+00:00 Michael Terry wrote: Oh, I think you meant naming ideas? SleepingWithType? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/578542/comments/23 ------------------------------------------------------------------------ On 2011-03-30T10:24:53+00:00 Richard Hughes wrote: (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). Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/578542/comments/24 ------------------------------------------------------------------------ On 2013-10-12T22:52:43+00:00 Bugzilla-x wrote: The Sleeping signal is deprecated, and removed in my branch. We won't get a new signal. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/578542/comments/26 ** Changed in: upower Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/578542 Title: resuming from S3 wrongly prompts for password Status in Gnome Powermanager: New Status in The Session Menu: Incomplete Status in Upower: Won't Fix Status in “gnome-power-manager” package in Ubuntu: In Progress Status in “indicator-session” package in Ubuntu: Incomplete Status in “upower” package in Ubuntu: In Progress 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: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/578542/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
