dbus does not report any PowerManagment messages

Bug #526641 reported by Henning Moll on 2010-02-23
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-power-manager

My laptop does not supend on critical low battery power. If i plug or unplug AC, then gpm is notified about this and it shows a notification message. if i unplug AC while running a gnome session the icon appears and the tooltip shows, that the battery is discharging. After a while of inactivity, the screen is not dimmed. The warnings about low or critical battery power are not shown. Finally, the laptop does not suspend but just runs out of power...

If i start the laptop while AC is not connected then the situation is different: The screen gets dimmed after a few seconds of inactivity. Notifications of low or critical battery power are shown. Unfortunately, the laptop does not suspend.

Manual supend works perfect.

Output of dbus-monitor --session "type='signal',interface='org.freedesktop.PowerManagement'":

signal sender=org.freedesktop.DBus -> dest=:1.101 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.101"
method call sender=:1.57 -> dest=:1.101 serial=490 path=/; interface=org.freedesktop.DBus.Introspectable; member=Introspect

but nothing more. (For example, i unplug/plug AC while the command was running, but no output).

Running Ubuntu Karmic 9.10
Kernel 2.6.31-19-generic
gpm 2.28.1

My Laptop is an Acer Extensa 5635Z

ProblemType: Bug
Architecture: amd64
CheckboxSubmission: 06f8f0bfd32794bbacd433bf1b762a08
CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e
Date: Tue Feb 23 20:31:22 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: gnome-power-manager 2.28.1-0ubuntu1.3
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: gnome-power-manager
Uname: Linux 2.6.31-19-generic x86_64

Henning Moll (drscott) wrote :
Anzenketh (anzenketh) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please run apport-collect -p gnome-power-manager 526641 ? You might also want to take a look at the debugging instructions located at https://wiki.ubuntu.com/DebuggingGNOMEPowerManager and submit any other logs related to your problem. Thanks in advance.

Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
Anzenketh (anzenketh) wrote :

I apologize that is not needed I had a slip of the mouse.

Anzenketh (anzenketh) on 2010-02-24
tags: added: likely-dup
Anzenketh (anzenketh) wrote :

According to DevkitPower.txt you do not have suspend on low battery turned on. Please check your power settings to make sure that is not the case and post back if that did not fix your issue.

Henning Moll (drscott) wrote :

On the 'On battery power' tab it says: "When battery power is critical low => Hibernate"

Chris Coulson (chrisccoulson) wrote :

Thank you for your bug report. Please run "killall gnome-power-manager && gnome-power-manager --verbose 2>&1 | tee ~/gpm.log", let your battery run low, and attach the resulting file here if the laptop does not perform the expected action when the battery gets critically low.

Changed in gnome-power-manager (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Medium
Henning Moll (drscott) wrote :

Ok, here are the results. I did two test runs:

1. I started your suggested command first and then disconnect AC. The only notifications are those of AC connect/disconnect. After charge state reached 0.0 i immediately reconnect AC. I didn't risk running out of power.

2. I disconnect AC before starting the laptop. After login i run your command. This time hibernation worked. But it works not everytime. In my opinion the distribution of the notifications over time is strange: Four notifications between 11.9 and 9.8 percent charge, then no notification down to 2.3 percent. At this point the first critical warning appeard (critical, only 5 minutes left). The last notification at 0.9 percent says "critical, system hibernates now". And it worked this time.

Henning Moll (drscott) wrote :

Test 2

Henning Moll (drscott) on 2010-03-01
Changed in gnome-power-manager (Ubuntu):
status: Incomplete → New
Anzenketh (anzenketh) wrote :

Could we get the following information added to the bug report just so we have it.
I know we already covered this.

gconftool-2 --recursive-list /apps/gnome-power-manager > gpm.gconf.values.txt

Anzenketh (anzenketh) wrote :

Please attach the file to your bug report.

Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
Chris Coulson (chrisccoulson) wrote :

The log from your first test case (disconnecting AC after powering up) shows that the critically low battery is ignored because the computer still thinks you're on AC.

Please provide the output of "upower --dump" with AC disconnected for both test cases above (1 - disconnecting AC after starting up, 2 - disconnecting AC before starting up)

Henning Moll (drscott) wrote :

How do i install upower on karmic?

Please find attached the requested information from gconftool-2

Chris Coulson (chrisccoulson) wrote :

Oh, sorry, I didn't realise you were on karmic. You can just replace "upower --dump" with "devkit-power --dump" instead then.

It would also be great if you could try it with the Lucid Alpha 3 live CD, to see if it is an issue there too

Henning Moll (drscott) wrote :

It seems to work with lucid a3.

_sRg_ (sor-sergey) wrote :

Confirm this bug in Ubuntu 10.04

ybaruss (yabruss) wrote :

Please, if you experienced this problem with 10.04Lucid can you provide:

* The output of "upower --dump" with AC disconnected/connected in both case: dis/connected before boot or dis/connection under session open ?

* Do command: gconftool-2 --recursive-list /apps/gnome-power-manager > gpm.gconf.values.txt
and attach file gpm.gconf.values.txt ?

Many thanks

Download full text (3.3 KiB)

Thank you for you help to resolve this trouble. I really appreciate it.

Outputs of "upower --dump" can be found in attachments.
   * Battery_mode_after_boot - laptop has been turned on with unplugged AC
power;
   * AC_mode_after_boot - few minutes after log in session I plugged AC
power. Nothing changed;
   * AC_mode_after_boot_changed - after about 5 minutes screen brightness
was increased and AC power mode was activated;
   * gpm.gconf.values.txt - gpm settings dump.

Why does it takes core so much time to switch between power modes in Ubuntu
10,04?
Please help me solve and correct this bug.

2010/10/2 ybaruss <email address hidden>

> Please, if you experienced this problem with 10.04Lucid can you provide:
>
> * The output of "upower --dump" with AC disconnected/connected in both
> case: dis/connected before boot or dis/connection under session open ?
>
> * Do command: gconftool-2 --recursive-list /apps/gnome-power-manager >
> gpm.gconf.values.txt
> and attach file gpm.gconf.values.txt ?
>
> Many thanks
>
> --
> dbus does not report any PowerManagment messages
> https://bugs.launchpad.net/bugs/526641
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “gnome-power-manager” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: gnome-power-manager
>
> My laptop does not supend on critical low battery power. If i plug or
> unplug AC, then gpm is notified about this and it shows a notification
> message. if i unplug AC while running a gnome session the icon appears and
> the tooltip shows, that the battery is discharging. After a while of
> inactivity, the screen is not dimmed. The warnings about low or critical
> battery power are not shown. Finally, the laptop does not suspend but just
> runs out of power...
>
> If i start the laptop while AC is not connected then the situation is
> different: The screen gets dimmed after a few seconds of inactivity.
> Notifications of low or critical battery power are shown. Unfortunately, the
> laptop does not suspend.
>
> Manual supend works perfect.
>
> Output of dbus-monitor --session
> "type='signal',interface='org.freedesktop.PowerManagement'":
>
> signal sender=org.freedesktop.DBus -> dest=:1.101 serial=2
> path=/org/freedesktop/DBus; interface=org.freedesktop.DBus;
> member=NameAcquired
> string ":1.101"
> method call sender=:1.57 -> dest=:1.101 serial=490 path=/;
> interface=org.freedesktop.DBus.Introspectable; member=Introspect
>
> but nothing more. (For example, i unplug/plug AC while the command was
> running, but no output).
>
> Running Ubuntu Karmic 9.10
> Kernel 2.6.31-19-generic
> gpm 2.28.1
>
> My Laptop is an Acer Extensa 5635Z
>
> ProblemType: Bug
> Architecture: amd64
> CheckboxSubmission: 06f8f0bfd32794bbacd433bf1b762a08
> CheckboxSystem: 2954e74ba17fb0e37fc942cd1d9fab4e
> Date: Tue Feb 23 20:31:22 2010
> DistroRelease: Ubuntu 9.10
> InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
> Package: gnome-power-manager 2.28.1-0ubuntu1.3
> ProcEnviron:
> LANG=de_DE.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
> SourcePackage: gnome-power-manager
> Uname: Linux 2....

Read more...

ybaruss (yabruss) on 2010-10-03
Changed in gnome-power-manager (Ubuntu):
status: Incomplete → Confirmed
To post a comment you must log in.