Reporting Bugs

First, please find the list of bugs so that you are sure the bug you are reporting isn't a duplicate bug that someone else has fixed.

If not present, then please create a new bug attaching all the information to this new bug.

Please do not email me bug reports, as the volume of email I get is already huge. Bugzilla lets me keep it all the information in one place, so I don't loose track!

General Bugs

When GNOME Power Manager doesn't work, there is lots that could be wrong. To help me diagnose the problem, please supply the following information:

• The version of GNOME Power Manager installed.
• The version of DBUS installed.
• The version of HAL installed.
• The kernel version installed.
• The raw ACPI data supplied by ACPI (if applicable).
• The installation method you used (i.e. FC4 RPM, tarball).
• Your distribution and version.
• The verbose trace from gnome-power-manager
• The verbose trace from hald
• Any other information that may be relevant.

Raw ACPI Information

Do this as the root user.

for i in /proc/acpi/battery/*/*; do echo $i; cat $i; done

GNOME Power Manager Verbose Trace

This will turn on verbose debugging for GNOME Power Manager.

killall gnome-power-manager
gnome-power-manager --no-daemon --verbose

GConf custom settings

This will display your user settings for GNOME Power Manager.

gconftool-2 -R /apps/gnome-power-manager

Reason (/var/log/messages) information

This will return the reason GNOME Power Manager did a specific action.

cat /var/log/message | grep gnome-power-manager

HAL Verbose Trace

/usr/sbin/hald --daemon=no --verbose=yes --retain-privileges

Segfaults or random crashes

I would really appreciate it if you could send me more information about the crash, specifically a backtrace with gdb.

You have to compile GNOME Power Manager from CVS to do this. Grab the latest from CVS, and open configure.in, and uncomment the line below "Debugging switches" Run ./autogen.sh --prefix=/tmp as normal in the source directory. Compile it with "make", and then use "make install". After that in the same directory where you typed "make" run:

gdb ./gnome-power-manager

The GNU debugger (gdb) will start and put you at a prompt:

(gdb) _

Then type the following and crash the program / let it crash on it's own.

(gdb) run --no-daemon --verbose

You will be back in the gdb shell. Then type bt at the prompt and send me all the output that follows. This will tell me exactly what the program was doing when it crashed.

This link will give you more information.

You can also try calling the HAL methods from the command line:

dbus-send --system --print-reply --dest=org.freedesktop.Hal \
/org/freedesktop/Hal/devices/acpi_lcd \
org.freedesktop.Hal.Device.LaptopPanel.SetBrightness \
int32:2
dbus-send --system --print-reply --dest=org.freedesktop.Hal \
/org/freedesktop/Hal/devices/computer \
org.freedesktop.Hal.Device.SystemPowerManagement.Suspend \
int32:0

Downloads

GNOME Power Manager should come bundled with most modern distributions.

The latest source releases can always be found at the GNOME ftp site.

Make sure to get latest release of HAL, the service that GNOME Power Manager depends on.

Feedback

Bugs should be reported to the GNOME Bug Tracking System.

Please read the FAQ and the bug reporting guidelines before creating a new bug.

You can get in touch with developers and other users by sending a mail to the Power Manager mailing list or search the [archives].

Copyright © 2005-2007, Richard Hughes.
Optimized for standards.