Hi,

After following this: http://forums.gentoo.org/viewtopic-t-85 ... ight-.html , I unmerged hal.

Since then, battery is not detected by KDE even though all info about battery is present system wise:

Code: Select all

louloute ~ # ls /sys/class/power_supply/BAT0/
alarm        charge_full_design  current_now  device        model_name  present        status     technology  uevent              voltage_now
charge_full  charge_now          cycle_count  manufacturer  power       serial_number  subsystem  type        voltage_min_design


Also dbus and consolekit are started.

I saw other users having it working so there might be something to setup/re-install on both linux laptops where I have this issue.

Any idea what?

Thank you

Greetings !!

I have a real problem with the same description of the issue.
Hal and dbus are both related to this issue, but I can not find a way to solve it.
The only one workaround I have is to start in run level 3 and from there startx, the Battery Monitor will be lighted up !!

You can check in run level 3 if all is ok for your battery by using acpi -b or lshal | grep battery.

I stay around to find a way to fix it.

Thinking about this workaround (related to the run levels) I switched off the 'B' flag for hal and now I have no more strange behaviour, note that I disabled wicd also.

Someone said that hal is mandatory with KDE4.4, which is the version I use.

I guess I have to wait untill next version is released/stable for my ditro.

As stated, KDE depends on HAL with KDE 4.5 and earlier. UPower, UDisks and UDev won't be used for information in these releases.

If you wish to use a HAL-less system, then KDE 4.6 or later is required. If you use KDE 4.6 or later, you therefore must have UPower and UDisks installed, as well as UDev functioning fully.

If you wish to continue using HAL with KDE 4.6, you need to export a particular environment variable which will enable HAL support and disable UDev, etc support.

Great to know that, I'll stick to hal untill KDE4.6. Thank you!