Hi,
On 23 December 2012 22:31, frozencemetery 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
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
On 18:43 Mon 12 Nov , Martin Kjær Jørgensen wrote:
> On Mon, Nov 12, 2012 at 06:32:04PM +0200, Apollon Oikonomopoulos wrote:
> > Hi,
> >
> > On 08:39 Mon 12 Nov , Martin Kjær Jørgensen wrote:
> > > Dear Maintainer,
> > > I'm using xmobar with XMonad. When using CoreTemp in .xmobarrc i get:
Hi,
On 08:39 Mon 12 Nov , Martin Kjær Jørgensen wrote:
> Dear Maintainer,
> I'm using xmobar with XMonad. When using CoreTemp in .xmobarrc i get:
> "Prelude.read: no parse" instead of the core temperature.
Can you please attach the output of `cat
/sys/bus/platform/devices/coretemp.0/temp1_l
Package: xmobar
Version: 0.14-3
Severity: important
Dear Maintainer,
I'm using xmobar with XMonad. When using CoreTemp in .xmobarrc i get:
"Prelude.read: no parse" instead of the core temperature.
When using BatteryP I get " 0%" instead of the actual value.
I've tried purge the xmobar package
5 matches
Mail list logo