Questions[xfce4-power-manager](ubuntu)

I have two batteries for my laptop of differing capacities. I took out the larger battery today and hot swapped it for the smaller battery as I had not used it in a while an I wanted to make sure it didn't discharge too far. (Note: Technically it is probably more accurate to call it a "warm" swap. I basically went to suspend, but mainly for convenience because I have to shut the lid to flip the unit over to swap batteries, and my system is set to suspend when the lid closes.)

But after swapping the battery, the Xfce Power Manager reports strange values. For instance, it said it would take about 60 hours to charge the battery. After a couple of hours it has charged up to 80% and is still saying close to 6 hours are left to charge. Under devices it says that fully charged the battery is 66.2Wh. But if I swap back to the larger battery the battery name (e.g. LG 45NXXXX) doesn't change, and the battery size doesn't change either. This is making me wonder if it thinks the smaller battery is still the larger battery and might try to overcharge it thinking it has the higher capacity.

Is this something I need to worry about? Is there some command I can run to "reset" things so it properly recognizes the new battery?

I'd like to be able to suspend-then-hibernate automatically with xfce4-power-manager, though I'm not sure if this is possible.

I believe this is a permission error with polkit1 because:

$ xfce4-power-manager --dump
---------------------------------------------------
       Xfce power manager version 1.6.1
With policykit support
With network manager support
---------------------------------------------------
Can suspend: True
Can hibernate: False
Authorized to suspend: True
Authorized to hibernate: False
Authorized to shutdown: True
Has battery: True
Has brightness panel: True
Has power button: True
Has hibernate button: True
Has sleep button: True
Has LID: True

My polkitsettings under/usr/share/polkit-1/actions/org.freedesktop.login1.policyare identical for suspend and hibernate, so it doesn't make much sense whenxfce-power-manager` can't access hibernate options.

According to How to go automatically from Suspend into Hibernate?: I've created /etc/systemd/sleep.conf and tested it. The following command does work (suspend and then hibernates according to sleep.conf):

sudo systemctl suspend-then-hibernate

But this does not work when I use xfce4-power-manager to do the suspension.

A post I found (How to go automatically from Suspend into Hibernate?) is similar, but is not exactly what I'm trying to do. I don't care about lid closed operation, I want everything time related.

With XUbuntu 18.10 (pretty fresh install) when locking the system the monitor is immediately suspended; pressing any key or mouse button doesn't wake it. Pressing CTRL + ALT + F7 finally wakes the monitor and the message below is presented:

This session is locked You'll be redirected to the unlock dialog automatically in a few seconds

then the lock screen appears and everything goes as expected.

Another solution is to type the password (while the monitor is still blank) then press ENTER which then wakes the monitor and also unlocks the session (if the password is correctly typed, of course).

I have these settings (Display Power Management on or off and/or Automatically lock the session activated or not make no difference):

The expected behavior with Display Power Management on and Automatically lock the session activated is:

1. when locking the system first the monitor should be still on
2. the lock window should be presented
3. after 10 min the monitor should go black
4. after 15 min the monitor should sleep
5. after 60 min the monitor should switch off
6. when pressing any key or mouse the monitor should switch on and the lock window be presented

What should I do in order to obtain the desired behavior? also I don't want to avoid the problem by using xscreensaver

UPDATE

The same behavior is no matter what I choose for Display Power Management and/or Automatically lock the session.

With Power Manager unchecked in Session and Startup (Screen Locker still checked) the behavior is the same. I guess it's a Screen Locker (light-locker) issue.

This is the /var/log/syslog created when locking:

Apr 12 20:24:26 adrhc systemd[1]: Started /run/user/111 mount wrapper.
Apr 12 20:24:26 adrhc systemd[1]: Created slice User Slice of UID 111.
Apr 12 20:24:26 adrhc systemd[1]: Starting User Manager for UID 111...
Apr 12 20:24:26 adrhc systemd[1]: Started Session c9 of user lightdm.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Paths.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG network certificate management daemon.
Apr 12 20:24:26 adrhc systemd[21272]: Starting D-Bus User Message Bus Socket.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 20:24:26 adrhc systemd[21272]: Listening on Sound System.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Timers.
Apr 12 20:24:26 adrhc systemd[21272]: Listening on D-Bus User Message Bus Socket.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Sockets.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Basic System.
Apr 12 20:24:26 adrhc systemd[21272]: Reached target Default.
Apr 12 20:24:26 adrhc systemd[21272]: Startup finished in 33ms.
Apr 12 20:24:26 adrhc systemd[1]: Started User Manager for UID 111.
Apr 12 20:24:26 adrhc systemd[21272]: Started D-Bus User Message Bus.
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] AppArmor D-Bus mediation is enabled
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.1' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc systemd[21272]: Starting Accessibility services bus...
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Successfully activated service 'org.a11y.Bus'
Apr 12 20:24:26 adrhc systemd[21272]: Started Accessibility services bus.
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: dbus-daemon[21348]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' requested by ':1.3' (uid=111 pid=21337 comm="/usr/sbin/lightdm-gtk-greeter " label="unconfined")
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: dbus-daemon[21348]: Successfully activated service 'org.a11y.atspi.Registry'
Apr 12 20:24:26 adrhc at-spi-bus-launcher[21343]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Apr 12 20:24:26 adrhc systemd[21272]: Starting Virtual filesystem service...
Apr 12 20:24:26 adrhc dbus-daemon[21342]: [session uid=111 pid=21342] Successfully activated service 'org.gtk.vfs.Daemon'
Apr 12 20:24:26 adrhc systemd[21272]: Started Virtual filesystem service.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21244 (lightdm) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21327 (gnome-keyring-d) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21336 (lightdm-greeter) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: session-c9.scope: Killing process 21337 (lightdm-gtk-gre) with signal SIGTERM.
Apr 12 20:24:57 adrhc systemd[1]: Stopping Session c9 of user lightdm.
Apr 12 20:24:57 adrhc systemd[1]: Stopped Session c9 of user lightdm.
Apr 12 20:24:57 adrhc systemd[1]: [email protected]: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopping User Manager for UID 111...
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Default.
Apr 12 20:24:57 adrhc gvfsd[21352]: A connection to the bus can't be made
Apr 12 20:24:57 adrhc systemd[21272]: Stopping Accessibility services bus...
Apr 12 20:24:57 adrhc systemd[21272]: Stopping D-Bus User Message Bus...
Apr 12 20:24:57 adrhc systemd[21272]: Stopping Virtual filesystem service...
Apr 12 20:24:57 adrhc systemd[21272]: Stopped D-Bus User Message Bus.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped Accessibility services bus.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped Virtual filesystem service.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Basic System.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Paths.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Timers.
Apr 12 20:24:57 adrhc systemd[21272]: Stopped target Sockets.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache.
Apr 12 20:24:57 adrhc systemd[21272]: Closed Sound System.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG network certificate management daemon.
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Apr 12 20:24:57 adrhc systemd[21272]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Apr 12 20:24:57 adrhc systemd[21272]: Closed D-Bus User Message Bus Socket.
Apr 12 20:24:57 adrhc systemd[21272]: Reached target Shutdown.
Apr 12 20:24:57 adrhc systemd[21272]: Starting Exit the Session...
Apr 12 20:24:57 adrhc systemd[1]: [email protected]: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopped User Manager for UID 111.
Apr 12 20:24:57 adrhc systemd[1]: [email protected]: Unit not needed anymore. Stopping.
Apr 12 20:24:57 adrhc systemd[1]: Stopping /run/user/111 mount wrapper...
Apr 12 20:24:57 adrhc systemd[1]: Removed slice User Slice of UID 111.
Apr 12 20:24:57 adrhc systemd[1]: Stopped /run/user/111 mount wrapper.

In Xfce power manager settings I have set 6 minutes timeout for turning display off (and never for sleep). However, display turns off sooner and xset q displays (among other things):

DPMS (Energy Star): Standby: 120 Suspend: 0 Off: 0 DPMS is Enabled

If I change the setting to say 7 minutes in Xfce power manager, the output is

DPMS (Energy Star): Standby: 0 Suspend: 0 Off: 420 DPMS is Enabled

But I want the Xfce setting to be effective from start. What sets the DPMS timeout value to different from Xfce setting? Xcreensaver is not installed.

OS: Ubuntu 14.04.5 LTS with Xfce desktop

Workaround:

Add the following command in Application Autostart tab of Session and Startup dialog:

/bin/sh -c 'sleep 5 && xset dpms 0 $((60*$(xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/dpms-on-ac-sleep))) $((60*$(xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/dpms-on-ac-off)))'

(This is for AC mode. You may have to adjust the argument for sleep larger.)

I have Xubuntu 15.04 installed and having some issues with Suspend. It Suspends fine when done from the command line or the shutdown menu or even by closing the lid. I have set the inactivity timer to 15 minutes using xfce power manager for suspend. However, it never suspends because of inactivity. When I log back in after the failure to suspend, I see this message on the top right: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Permission denied

I have tried some of the solutions online such as the ones here and here but it didn't make a difference.

Anyone has any ideas of things to try. Is there any logs that can tell me what could be wrong.