Package: upower
Version: 0.9.23-2+b1
Followup-For: Bug #728762
I have the exact same problem (XFCE/lightdm from sid), with the exact
same output from `xfce4-power-manager --dump` and when attempting to
suspend via dbus-send. It started occurring about two weeks ago.
Two more symptoms that I suspect are related:
- Automatic mounting of USB thumb drives, external HDDs, etc. no
longer works in XFCE.
- The XFCE panel session menu's suspend, hibernate, shutdown and
restart options are now greyed out and unavailable.
Also, I found a very similar-smelling bug report[1] from around August
this year to do with a lightdm bug that prevented it from creating
active consolekit sessions. The bug report, which was for lightdm
1.7.7, contained a patch that was applied upstream and was fixed in
1.7.16. I checked, and lightdm 1.8.5-1 -- which I currently have
installed -- includes the patch. So it sounds like a different issue.
However, the report mentions that the output of `ck-list-sessions`
should list at least one active session (i.e., with "active = TRUE").
On my system, it doesn't. Should it? (I'm not very familiar with
consolekit.)
[1] https://bugs.launchpad.net/lightdm/+bug/1211892
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.11-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages upower depends on:
ii dbus 1.6.18-1
ii libc6 2.17-95
ii libdbus-1-3 1.6.18-1
ii libdbus-glib-1-2 0.100.2-1
ii libglib2.0-0 2.36.4-1
ii libgudev-1.0-0 204-5
ii libimobiledevice4 1.1.5-2
ii libplist1 1.10-1
ii libpolkit-gobject-1-0 0.105-4
ii libupower-glib1 0.9.23-2+b1
ii libusb-1.0-0 2:1.0.17-1+b1
ii pm-utils 1.4.1-13
ii systemd 204-5
ii udev 204-5
Versions of packages upower recommends:
ii policykit-1 0.105-4
upower suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
