(In reply to ian from comment #2)
> The settings *are* different: lock screen when the lid is closed on AC, and
> suspend when the lid is closed on battery.  But keeping the laptop awake
> just because the cord was still plugged in at the instant that the lid was
> closed seems like a very stupid thing for the power manager to do.  Is there
> a good reason for this behavior?  And does it offset the silliness of having
> to open and close the lid (after unplugging) to get the laptop to go to
> sleep?

First of all, keep the tone friendly. We took over the power manager
after it was unmaintained for 2 years. A lot of the infrastructure
around it has changed and we're trying to keep/make it working.

In one of the last few releases, Ubuntu introduced logind to handle these sort 
of things and xfpm carries patches for that.
Anyway, it's very odd that the behavior seems mixed up. You could check the 
xfconf variables for the settings, if you've upgraded from previous versions 
you could also try to reset the channel via xfce4-settings-editor and then 
configure xfpm anew and see whether that fixes the issue.
It might also help if you attach the settings xml file of xfce4-power-manager 
(from ~/.config/xfce4/xfconf/..)

> Is there some other way that any sequence of events resulting in a
> simultaneous-closed-lid-and-unplugged-power-supply state will suspend the
> laptop?  That was the case under Ubuntu 10.10, IIRC.

Ubuntu 10.10 was released about 4 years ago, the architecture around
suspend has changed a lot since then (e.g. UPower doesn't support it
anymore).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1014891

Title:
  Laptop doesn't suspend when power is unplugged while lid is closed

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-power-manager/+bug/1014891/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to