No battery level indication
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-power-manager (Ubuntu) |
Incomplete
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: indicator-applet
I've upgraded my June 2009 Macbook Pro from Karmic to Lucid. The battery indicator applet had been working, but right now it isn't. I see the indicator applet, and I can open its About dialog and preferences, but I get no information about battery status. Instead it shows the power-plug-like image. There is no tooltip.
The problem may be related to some failed suspend attempts I made just now; the system was probably still trying to suspend as I unplugged the power.
---
Architecture: i386
CheckboxSubmission: 7131a2e6825aee6
CheckboxSystem: 7e42599bda39ea7
DevkitPower:
Error: command ['upower', '-d'] failed with exit code 1:
(upower:28421): libupower-
DistroRelease: Ubuntu 10.04
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
MachineType: Apple Inc. MacBookPro5,4
NonfreeKernelMo
Package: gnome-power-manager 2.30.0-0ubuntu1
PackageArchitec
ProcCmdLine: root=UUID=
ProcEnviron:
LC_TIME=
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
Tags: lucid
Uname: Linux 2.6.32-19-generic i686
UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev pulse pulse-access sambashare video
dmi.bios.date: 06/15/09
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP53.88Z.
dmi.board.
dmi.board.name: Mac-F22587A1
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro5,4
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAppleInc
dmi.product.name: MacBookPro5,4
dmi.product.
dmi.sys.vendor: Apple Inc.
affects: | indicator-applet (Ubuntu) → gnome-power-manager (Ubuntu) |
tags: | added: karmic2lucid |
There were also no warnings about low-battery conditions. As my battery ran out, the system unexpectedly tried to suspend (as evidenced by a dialog saying it failed to), and later went into sudden shutdown.
The shutdown also caused other problems: the real-time clock was reset to the distant past (sometime before 2001), the system failed to recover a usable clock setting once it was working again, the filesystem needed fsck, the fsck message on the boot screen was broken, and the fsck failed; I'll file separate bugs for those issues.