[Bug 220324] [NEW] Guidance-power-manager stopped working after upgrade to Gutsy

[RickKnight]

Public bug reported:

Guidance-power-manager worked well under Dapper and Feisty on this
notebook PC. After upgrade from Feisty to Gutsy, the power
manager/battery monitor icon is not available. When I manually start
guidance-power-manager I get several error messages

Output of $ guidance-power-manager

guidance-power-manager &
[2] 9208
[1]   Done                    guidance-power-manager
rick at rick-laptop:~$ No battery found.
No AC adapter found - assume that we are on batteries.
Warning: While setting SystemPowerManagement to  True :  org.freedesktop.Hal.Device.SystemPowerManagement.NotSupported: No powersave method found
No AC adapter found - assume that we are on batteries.
No AC adapter found - assume that we are on batteries.
Traceback (most recent call last):
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 1120, in <module>
    mainWindow = PowermanagerApp(None, "main window")
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 1064, in __init__
    self.pmwidget.prepare()
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 101, in prepare
    self._initLid()
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 140, in _initLid
    self.powerHasBeenUnplugged()
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 927, in powerHasBeenUnplugged
    msg = self.checkCpuFreq()
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 902, in checkCpuFreq
    if not policy in self.cb_freq:
AttributeError: cb_freq
Error in sys.excepthook:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/apport_python_hook.py", line 42, in apport_excepthook
    binary = os.path.realpath(os.path.join(os.getcwdu(), sys.argv[0]))
IndexError: list index out of range

Original exception was:
Traceback (most recent call last):
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 1120, in <module>
    mainWindow = PowermanagerApp(None, "main window")
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 1064, in __init__
    self.pmwidget.prepare()
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 101, in prepare
    self._initLid()
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 140, in _initLid
    self.powerHasBeenUnplugged()
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 927, in powerHasBeenUnplugged
    msg = self.checkCpuFreq()
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 902, in checkCpuFreq
    if not policy in self.cb_freq:
AttributeError: cb_freq
                                           
Output of $ dmesg attached

Thanks,
Rick Knight

** Affects: kde-guidance (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Guidance-power-manager stopped working after upgrade to Gutsy 
https://bugs.launchpad.net/bugs/220324
You received this bug notification because you are a member of Kubuntu
Team, which is subscribed to kde-guidance in ubuntu.