Hi, On 23 December 2012 22:31, frozencemetery <rharw...@club.cc.cmu.edu> wrote:
> Package: xmobar > Version: 0.14-4 > Followup-For: Bug #693025 > > Hello, > > When using BatteryP, xmobar is unable to detect my battery, and reports 0 > for > left constantly. > > As the original responder for this bug report did, I upgraded the version > of > xmobar to version 0.15 from cabal, and the battery appears to be detected > with > no problems. > > In message 20, Apollon Oikonomopoulos <apoi...@gmail.com> wrote: > > Most likely you need to use the -c parameter for BatteryP to point it to > the > > correct file under /sys/class/power/<BAT>/, see the manpage for details > and > > give it a try if you can. 0.15 does some autodiscovery and doesn't need > the > > -c flag anymore. > > I'd very much like to do this. However, that directory does not exist on > my > system. The closest thing appears to be /sys/class/power_supply, where > within > the relevant battery subdirectory there are files energy_full, > energy_full_design, and energy_now, which I believe -c is searching for. > With > 0.15, however, I don't even need to pass this flag. > > Yes, it is under /sys/class/power_supply (the manpage is wrong). Battery detection has changed significantly in 0.15, so no manual tuning is needed anymore. Unfortunately 0.15 depends on libghc-x11-dev 1.6.0, which didn't make it to unstable in time for wheezy, so I can't do much (except upload a version in experimental perhaps). Regards, Apollon
