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. Many thanks. -- System Information: Debian Release: wheezy/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xmobar depends on: ii libc6 2.13-37 ii libffi5 3.0.10-3 ii libgmp10 2:5.0.5+dfsg-2 ii libiw30 30~pre9-8 ii libx11-6 2:1.5.0-1 ii libxext6 2:1.3.1-2 ii libxft2 2.3.1-1 ii libxinerama1 2:1.1.2-1 ii libxrandr2 2:1.3.2-2 Versions of packages xmobar recommends: ii curl 7.26.0-1 Versions of packages xmobar suggests: ii xmonad 0.10-4+b2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
