[SRU] xfce4-power-manager does not inhibit systemd from handling buttons and lid events

Status changed to 'Confirmed' because the bug affects multiple users.

This affects me too, on xubuntu. I think this is a duplicate though

This is the XFCE equivalent of bug 1180513 (GNOME).

Temporary workaround is to set:

HandleLidSwitch=ignore

in /etc/systemd/logind.conf

However I now disabled xfce4-power-manager and let logind do the sleep, because it seems to go into suspend much faster (< 1 sec) than with xfce4-power-manager (~4 secs) on my MacBook Air.

Linking the Debian bug. This points to some patches for this.

Confirming here on a fresh Xubuntu 13.10 AMD64 install.
Hardware is Asus n55sf laptop.

The event tested is: during active xfce session, press power button.
Expected: a popup asks what to do (suspend, logout, power off, etc.).
Observed: no question asked, immediate shutdown procedure.

12.10 had expected good behavior.
13.10 has observed bad behavior.

Since there is no /etc/systemd/logind.conf in lubuntu, is there an alternate workaround?
Thanks guys.

Adding the PPA at https://launchpad.net/~noskcaj/+archive/power-manager-systemd should fix this. It uses the patches from openSUSE. It's still a work in progress as the current patches break autoreconf

I have installed the patched version provided by your PPA. Xfce Power Manager now prevents systemd from shutting down immediately and lets me interact with the shutdown dialog after the power button has been pressed.

Installed from PPA.

Pressing power button still powers down the machine.

I also tested the PPA and can confirm that it
1) makes the lid-events behave as expected from powermanager-settings and
2) inhibits logind from taking over the power-button.

So all is configurable again via the powermanager, as it used to be.

It's working here too, like ochosi says.

Ubuntu Studio 13.10 on Toshiba Sattellite p850.

The workaround doesn't work for me. Even editing /etc/systemd/logind.conf to have

#HandlePowerKey=ignore
#HandleSuspendKey=ignore
#HandleHibernateKey=ignore
#HandleLidSwitch=ignore

has no effect. Hitting power buttons means immediate shutdown. By the way my machine haven't got suspend or hibernate buttons, it's only the power button.

Tried to compare with same file in my working Ubuntu Studio 12.10 on the same machine, but I can't find a logind.conf at the expected location.

Is it safe to rename this file (in 13.10) and try to run without it?

Of course I forgot I have to uncomment.

Changing #HandlePowerKey=poweroff to

    HandlePowerKey=ignore

works.

Sorry.

Well, the workaround in /etc/systemd/logind.conf did indeed prevent the system from going into hibernate when I close the lid. This is some improvement, but it still does not lock the screen. When I open the lid, the system is unlocked, although I said otherwise in Lubuntu's power management settings.

Torsten Bronger, xfce4-power-manager normally uses xflock4 to lock, but that is not available in Lubuntu, where there is lxlock, instead. If I remember right, the power manager also supports a running xscreensaver or gnome-screensaver, if xflock4 is not available. Can you test it and maybe report a separate bug report about this issue by "ubuntu-bug xfce4-power-manager"?

Thanks Jarno for your explanations, but I don't know how to tell the power management to call xscreensaver or gnome-screensaver. Besides, this is a regression. I used to work out-of-the-box up to Ubuntu 13.04.

Torsten, besides telling the power manager to "Lock screen when going for suspend/hibernate" in its settings, you have to install xscreensaver package, add "xscreensaver -nosplash" as an autostarted application in LXDE settings. (You can test, if autostart worked by running command "pidof xscreensaver" in terminal after logging in: it displays a number, if xscreensaver is running.)

If you additionally want lxlock to be able to use xscreensaver (and to fix Bug #1205384) , you could do this in terminal (as superuser):
sudo wget --output-document=/usr/local/bin/lxlock http://bug-attachment.xfce.org/attachment.cgi?id=5295 && sudo chmod a+x /usr/local/bin/lxlock
If you later want to revert back to official lxlock, just delete the downloaded file /usr/local/bin/lxlock

Torsten, you could also view the downloaded script to get idea of alternative lockers, if you don't want to use xscreensaver. I think xfce4-power-manger works with all those alternatives, if you trick it to find xflock4, which is counterpart of lxlock in Xfce:

sudo ln -s -T /usr/local/bin/lxlock /usr/local/bin/xflock4

(Maybe you don't need to do it, if you have xfce4-session installed; then the power manager uses /usr/bin/xflock4 that comes with the package.)

This bug was fixed in the package xfce4-power-manager - 1.2.0-3ubuntu2

---------------
xfce4-power-manager (1.2.0-3ubuntu2) trusty; urgency=medium

  * Add patches from debian svn branch to fix systemd. LP: #1222021
  * Force run of xdt-autogen to continue to allow ppc64el to build
 -- Jackson Doak <email address hidden> Mon, 20 Jan 2014 07:04:09 +1100

Will it be also backported to 13.10?

Yes. Probably this weekend i'll start on the SRU. I just want to be sure
it's fully stable first

On Tue, Jan 21, 2014 at 11:17 AM, Goren <email address hidden> wrote:

> Will it be also backported to 13.10?
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1222021
>
> Title:
> xfce4-power-manager does not inhibit systemd from handling buttons and
> lid events
>
> Status in Xfce4 Power Manager:
> Unknown
> Status in “xfce4-power-manager” package in Ubuntu:
> Fix Released
> Status in “xfce4-power-manager” source package in Saucy:
> Triaged
> Status in “xfce4-power-manager” source package in Trusty:
> Fix Released
> Status in “xfce4-power-manager” package in Debian:
> New
>
> Bug description:
> Laptop sleeps when lid is closed, regardless of Power Manager
> settings. This also occurs in the Live install where Sleep is not even
> an option for lid closure actions. Confirmed in Ubuntu Studio 13.10
> Beta 1 x64 and Xubuntu 13.10 Beta 1. Does not occur in Ubuntu Studio
> 13.04.
>
> WORKAROUND: This can be adjusted in /etc/systemd/logind.conf. Just set
> HandleLidSwitch and other the events you want handled by systemd to
> "ignore" - you have to delete # in the beginning of the respective
> lines -, save, close the file, and restart.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.10
> Package: xfce4-power-manager 1.2.0-2ubuntu1
> ProcVersionSignature: Ubuntu 3.11.0-2.1-lowlatency 3.11.0-rc5
> Uname: Linux 3.11.0-2-lowlatency x86_64
> ApportVersion: 2.12.1-0ubuntu3
> Architecture: amd64
> CasperVersion: 1.336
> Date: Sat Sep 7 04:34:32 2013
> LiveMediaBuild: Ubuntu-Studio 13.10 "Saucy Salamander" - Alpha amd64
> (20130902)
> MarkForUpload: True
> SourcePackage: xfce4-power-manager
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/xfce4-power-manager/+bug/1222021/+subscriptions
>

This is the debian dir diff from the branch that Jackson attached. Jackson gave me the DEP-3 headers for the 06_add-shutdown-reboot-functionality-for-systemd.patch after I asked for them. I'm going ahead and uploading since it builds fine.

Hello Jerre, or anyone else affected,

Accepted xfce4-power-manager into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/xfce4-power-manager/1.2.0-2ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

No more to do for ubuntu-sponsors here, unsubscribing.

I'm running 13.10 and familiar with the issue, though I've mostly ignored it. This package from proposed fixed it for me today. I've got suspend-on-close for battery power, lock-screen-on-close for AC. Nice work!

Oh, and these are the package versions I upgraded to & tested:

ii xfce4-power-manager 1.2.0-2ubuntu1.1 amd64 power manager for Xfce desktop
ii xfce4-power-manager-data 1.2.0-2ubuntu1.1 all power manager for Xfce desktop, arch-indep files

Thanks for testing Casey. This should get move to release fairly soon.

Installed xfce4-power-manager 1.2.0-2ubuntu1.1 and xfce4-power-manager 1.2.0-2ubuntu1.1 from saucy-proposed, on Xubuntu 13.10 32bit. Closing the lid now behaves correctly!

This bug was fixed in the package xfce4-power-manager - 1.2.0-2ubuntu1.1

---------------
xfce4-power-manager (1.2.0-2ubuntu1.1) saucy; urgency=medium

  * Add patches from debian svn branch to fix systemd. LP: #1222021
  * Run dh-autoreconf to continue to allow arm64 to build
 -- Jackson Doak <email address hidden> Wed, 22 Jan 2014 10:34:16 +1100

The verification of the Stable Release Update for xfce4-power-manager has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

After installing update xfce4-power-manager (1.2.0-2ubuntu1.1) my screen brightness control is broken. (Well, I installed several updates, but this one seems to be the most likely culprit to me). I'll try to downgrade the package again to verify my suspicion. Right now I'm running on battery, so I don't want to try it immediately.

If turns out to be a regression, do you prefer to handle it here in the same report or in a new one? (Yes, I am aware of apport-collect)

Hmm, downgraded xfce-power-manager to the previously installed version, didn't help. Same exercise for gnome-settings-manager (which updated at the same time), did not help. Well, because downgrading did not help, I upgraded both of them to the current version again. Result: everything works fine. No clue what was going on there.

Sorry about the noise.

I just upgraded to Xubuntu 14.04 from 13.10. This issue is still not fixed. My laptop goes into hibernation or sleep when I close the lid. In Power Manager the action for closing the lid is set to 'lock screen' both for battery and AC powering. I have restarted after changes and tried multiple times.

The workaround mentioned in the bug description still works fully.

Scaramanga: Did you file a new bug and tag it as a regression per comment 32? I am also seeing this behavior but didn't want to duplicate the report.

I did. https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545

I had the same issue:
 - close the lid of my ubuntu 14.04 laptop
 - laptop goes in suspend
 - wake up to a black screen (reboot or console and kill x to get desktop back)

 fiddled around with powertools and no luck.
 BUT:
 Light locker (screensaver) settings where also set to start a screen saver etc.
 ===Disabled light locker and now===
 Close lid->suspend->open lid->wakeup is working!

 So check if multiple screen savers/powertools are interfering...

I am running Xubuntu 14.04 and have this issue, though I'm more concerned with the fact that my computer goes to sleep after a period of inactivity despite having both A/C and battery set to "Never" in the Power Manager. The workaround I use is a script that I added to the Application Autostart list:

xset s off
xset dpms 0 0 0
xset -dpms s off

I realize there is a bit of redundancy in using those three commands but I have tried different combinations and found using all three to be the only successful method.

An interesting thing to note is that everytime I update Xubuntu base I have to remove the command from the Autostart list and then add it again (unchecking and then checking the box does not work for me).

Hope this helps,
Jeremy

I'm still seeing this bug on 14.10.

I'm trying the logind.conf workaround.

I have xfce4-power-manager 1.4.1-0ubuntu1.