I also have the same issue with Gutsy. To get it to work, I quit the applet then restart hal, 'sudo /etc/init.d/hal restart', then I need run 'guidance-power-manager'.
Then I can see the battery (actually see two, but the second one is bogus and I am not worried about that).
I was wondering if hal is starting too soon in the boot up sequence? WHy would it not fuction from boot up.
After boot up the command, ' hal-find-by-capability --capability "battery"' showed nothing, but it shows this after I restart hal and gmp.
I know I could write a script to restart hal and then gpm after boot up, but I am worried that there may be other issues affected by this than I am aware of.
such as overheating or not charing the battery correctly. I doubt it, but I just don't know.
BTW I am running Kubuntu 7.10 Gutsy on a Dell Latitude D800, Pent-M 600-2000 Mhz, with 1 Gb of ram. A great laptop for Linux IMHO.
I also have the same issue with Gutsy. To get it to work, I quit the applet then restart hal, 'sudo /etc/init.d/hal restart', then I need run 'guidance- power-manager' .
Then I can see the battery (actually see two, but the second one is bogus and I am not worried about that).
I was wondering if hal is starting too soon in the boot up sequence? WHy would it not fuction from boot up.
After boot up the command, ' hal-find- by-capability --capability "battery"' showed nothing, but it shows this after I restart hal and gmp.
/org/freedeskto p/Hal/devices/ acpi_BAT0 p/Hal/devices/ acpi_BAT1
/org/freedeskto
I know I could write a script to restart hal and then gpm after boot up, but I am worried that there may be other issues affected by this than I am aware of.
such as overheating or not charing the battery correctly. I doubt it, but I just don't know.
BTW I am running Kubuntu 7.10 Gutsy on a Dell Latitude D800, Pent-M 600-2000 Mhz, with 1 Gb of ram. A great laptop for Linux IMHO.
Thanks for any help..