Hi, I assume this is something I've done wrong, but am unable to find any documentation related to it. On two notebooks: Compaq nw8440 HP dv2 When I install gnome power manager 2.26.4, I do not have any suspend, sleep, or battery options within gnome power manager. However, if I downgrade to 2.24.3, I have those settings and they work correctly. Both laptops are running ~amd64. The HP dv2 is a fresh install as of two days ago. I'm at a loss as to why this is occurring, but I have followed the Gentoo Power Management guide, and verified all use flags, and searched the forums. I've also searched the gnome bugzilla database as well. This issue only occurs when using g-p-m 2.26.4, g-p-m on the same system shows all the correct tabs and configuration settings for these two notebooks. If you require any additional information, please let me know. Reproducible: Always Steps to Reproduce: 1. Set ~arch in make.conf 2. Perform fresh install with gnome 3. Start gnome as root or user 4. Open g-p-m Actual Results: The battery/sleep/suspend tabs/options are missing. Expected Results: Same behavior as 2.24.4, which is to support the power management of the notebook.
Created attachment 201394 [details] output of emerge --info For reference, output of emerge --info
could you attach the output of: $ gnome-power-bugreport.sh
Created attachment 201969 [details] output of gnome-power-bugreport.sh Attached gnome-power-bugreport.sh from the fresh install. I am unable to get the log from the old laptop, as it has been sent back for servicing. This laptop is an HP DV2. With gnome-power-manager 2.4.4, there are no issues with power control.
you shouldn't be having those devicekit warning messages I guess.
(In reply to comment #4) > you shouldn't be having those devicekit warning messages I guess. > Probably not, but since this is a fresh install, I'm unsure why they are occurring. Given that this also happened on an old installation, I'd like to determine the root cause.
Reopening bug too, as the requested information was provided
(devkit-power:16969): devkit-power-gobject-WARNING **: Couldn't enumerate devices: Failed to execute program /usr/libexec/dbus-daemon-launch-helper: Success Daemon: I had a similar problem, and I solved it by re-emerging DBus, then restart it... can you try it ?
(In reply to comment #7) > I had a similar problem, and I solved it by re-emerging DBus, then restart > it... can you try it ? > re-emerging dbus did resolve this for me, but I'm concerned about what the root cause was. Portage must have pulled in something after dbus was installed that caused this to fail. At the moment, g-p-m 2.26.4 is running without any problems, and I can now manually make the dbus call: dbus-send --print-reply \ --system \ --dest=org.freedesktop.DeviceKit.Power \ /org/freedesktop/DeviceKit/Power/devices/battery_BAT0 \ org.freedesktop.DBus.Properties.GetAll \ string:org.freedesktop.DeviceKit.Power.Device Which now correctly returns: <snip> method return sender=:1.12 -> dest=:1.34 reply_serial=2Properties.GetAll array [ dict entry( string "native-path" variant string "/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:1e/PNP0C0A:00/power_supply/BAT0" ) dict entry( string "vendor" variant string "Hewlett-Packard" ) dict entry( string "model" variant string "5100" ) dict entry( string "serial" variant string "Li4402A" ) dict entry( string "update-time" variant uint64 1251020562 ) dict entry( string "type" variant uint32 2 ) dict entry( string "power-supply" variant boolean true ) dict entry( string "has-history" variant boolean true ) dict entry( string "has-statistics" variant boolean true ) dict entry( string "online" variant boolean false ) dict entry( string "energy" variant double 53.752 ) dict entry( string "energy-empty" variant double 0 ) dict entry( string "energy-full" variant double 53.752 ) dict entry( string "energy-full-design" variant double 55.08 ) dict entry( string "energy-rate" variant double 0.001 ) dict entry( string "voltage" variant double 12.531 ) dict entry( string "time-to-empty" variant int64 0 ) dict entry( string "time-to-full" variant int64 0 ) dict entry( string "percentage" variant double 100 ) dict entry( string "is-present" variant boolean true ) dict entry( string "state" variant uint32 4 ) dict entry( string "is-rechargeable" variant boolean true ) dict entry( string "capacity" variant double 97.411 ) dict entry( string "technology" variant uint32 0 ) dict entry( string "recall-notice" variant boolean false ) dict entry( string "recall-vendor" variant string "" ) dict entry( string "recall-url" variant string "" ) ] </snip> Thanks, Anthony
Did you forget to do `/etc/init.d/dbus reload` by any chance? Also, dbus upgrades require a system restart to function reliably (according to upstream)
(In reply to comment #9) > Did you forget to do `/etc/init.d/dbus reload` by any chance? Also, dbus > upgrades require a system restart to function reliably (according to upstream) > No, I did not forget that. Several times, after rebooting, I continued to have the issue. As a result, I had to downgrade to 2.24.4 which at least allowed me to set battery preferences.
the best thing to do would be to reproduce this bug and try to see why /usr/libexec/dbus-daemon-launch-helper fails but I guess you didn't make a copy of your old dbus there is nothing more we can do that close this bug worksforme. Please do re-open this bug if you come across such problem again though.
Looks like this was due to incorrect owner/group for /usr/libexec/dbus-daemon-launch-helper, will follow up in bug #222551.
(In reply to comment #12) > Looks like this was due to incorrect owner/group for > /usr/libexec/dbus-daemon-launch-helper, will follow up in bug #222551. > This should be fixed now that bug 222551 is.
