kde-guidance-powermanager: python2.5 crashed with AttributeError in checkBatteryCritical()

Playing around with it, I notice it starts fine on battery.

Also, this notebook has a mobile celeron yet Power Manager doesn't show the current CPU speed.

Thank you for your bug report. Please try to start the power manager from command-line. This should give you a python backtrace when it crashes; please attach this as a file to this bug report. You can start the power manager with the command "guidance-power-manager".

  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 1125, in <module>
    mainWindow = PowermanagerApp(None, "main window")
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 1069, 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 928, in powerHasBeenUnplugged
    self.checkBatteryCritical()
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 954, in checkBatteryCritical
    if self.batt_state == "discharging":
AttributeError: batt_state

I have the same problem than PraysToPan and the same output for guidance-power-manager

This bug was fixed in the package kde-guidance - 0.8.0svn20080103-0ubuntu18

---------------
kde-guidance (0.8.0svn20080103-0ubuntu18) intrepid; urgency=low

  [ Anthony Fok ]
  * kubuntu_32_displayconfig_update_refresh_rate.patch:
    - The refresh rate was not updated for the selected resolution, so
      resolution change could fail. (LP: #82279)
  * kubuntu_33_displayconfig_add_new_video_cards.patch:
    - Added 8086:29b2 for "Intel Q35";
  * debian/copyright: s/FDL/GFDL/;

  [ Andreas Wenning ]
  * kubuntu_34_kde-powermanager_no_lid_special_behaviour_disable.patch:
    - No need to call power plugged/unplugged in init if no lid is
      found; this just make us crash. (LP: #231163)

 -- Andreas Wenning <email address hidden> Mon, 02 Jun 2008 22:20:45 +0200

Great work! Any chance of updating Hardy as well?

Thanks,
Jon

Hi Jon

I'm working on getting it into hardy; see the SRU request at the bottom of bug 82279 . It will at first get into hardy-proposed before going into hardy-updates; so it would be very nice if one that is affected has hardy-proposed enabled to give feedback when it get into hardy-proposed.

We need to have someone affected by this bug install from hardy-proposed and tell us if that package fixes the problem.

The update is ready for Hardy; I have upgrade it and works fine. Thank you very much!