[hardy] Latest HAL breaks guidance powermanager

Bug #204768 reported by Mikael Gerdin
42
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
Fix Released
Undecided
Unassigned
kde-guidance (Ubuntu)
Fix Released
Undecided
Scott Kitterman
network-manager (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: kde-guidance

kde-guidance-0.8.0svn20080103:

guidance-power-manager crashes at startup after HAL update 0.5.11~rc2-1ubuntu1
The latest HAL update has changed the keys for checking for suspend and hibernation support.
Old names: "power_management.can_suspend_to_ram" and "power_management.can_suspend_to_disk"
New names: "power_management.can_suspend" and "power_management.can_hibernate"

Revision history for this message
Mikael Gerdin (mgerdin) wrote :
Revision history for this message
Mikael Gerdin (mgerdin) wrote :

This fix makes g-p-m use the new HAL-keys.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Did we really upload something AFTER beta that changes function names without seeing what else it affects?

Changed in kde-guidance:
assignee: nobody → kitterman
status: New → In Progress
Revision history for this message
Baronek (baronek1) wrote :

I can confirm that bug.
Patch from Mikael Gerding solves issue for me.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package hal - 0.5.11~rc2-1ubuntu2

---------------
hal (0.5.11~rc2-1ubuntu2) hardy; urgency=low

  * debian/rules: build using --with-deprecated-keys, since we don't want to
    break packages that were assuming this worked right up through beta.
    LP: #204768.

 -- Steve Langasek <email address hidden> Fri, 21 Mar 2008 20:24:33 +0000

Changed in hal:
status: New → Fix Released
Revision history for this message
Scott Kitterman (kitterman) wrote :

Please try again after you get hal 0.5.11~rc2-1ubuntu2 in your updates. That should fix it.

Revision history for this message
Steve Langasek (vorlon) wrote :

network-manager was also affected by the deprecated interfaces going missing. Since hal is fixed this isn't urgent for hardy, but should be cleaned up for intrepid.

Changed in network-manager:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Olivier (olivier-lacroix) wrote :

It's better but still not it. That's what I get now :

Warning: in getBrightness(): org.freedesktop.Hal.Device.PermissionDeniedByPolicy: org.freedesktop.hal.power-management.lcd-panel no <-- (action, result)
Traceback (most recent call last):
  File "/usr/share/python-support/kde-guidance-powermanager/guidance-power-manager.py", line 876, in changePoweredBrightness
    self.powermanager.adjustBrightness(level)
  File "/usr/share/python-support/kde-guidance-powermanager/powermanage.py", line 303, in adjustBrightness
    if level == self.getBrightness():
  File "/usr/share/python-support/kde-guidance-powermanager/powermanage.py", line 291, in getBrightness
    if self.old_b:
AttributeError: PowerManage instance has no attribute 'old_b'
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/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 876, in changePoweredBrightness
    self.powermanager.adjustBrightness(level)
  File "/usr/share/python-support/kde-guidance-powermanager/powermanage.py", line 303, in adjustBrightness
    if level == self.getBrightness():
  File "/usr/share/python-support/kde-guidance-powermanager/powermanage.py", line 291, in getBrightness
    if self.old_b:
AttributeError: PowerManage instance has no attribute 'old_b'

Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 204768] Re: [hardy] Latest HAL breaks guidance powermanager

What version of power-manager do you have installed? I thought I fixed
that one.

Revision history for this message
Olivier (olivier-lacroix) wrote :

The latest available in hardy : 0.8.0svn20080103-0ubuntu7

Revision history for this message
Scott Kitterman (kitterman) wrote :

Looks like I missed a spot when fixing the Guidance part of Bug #183656. I'll take care of it.

Revision history for this message
Olivier (olivier-lacroix) wrote :

After a reboot the problem is gone. Thanks Scott

Revision history for this message
Stuart Read (sread) wrote :

Mikael Gerdin pointed me in the direction of this bug. I have not had any of the power management problems, but my network-manager crashes in a related manner (Bug #199066, Bug #145652). Relevant daemon.log is attached. Note that this problem remains with hal version 0.5.11~rc2-1ubuntu2.

Revision history for this message
Stuart Read (sread) wrote :

Network-manager debdiff in Bug #204868 fixes the problem. So this symptom is not a hal problem after all.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

---------------
kde-guidance (0.8.0svn20080103-0ubuntu8) hardy; urgency=low

  [ Andreas Wenning ]
  * Added kubuntu_18_kde-powermanager_unique-check.patch:
    - Fixed guidance-power-managers check for being a unique app.
  * Added kubuntu_19_kde-powermanager_gpmhelper.patch
    (LP: #151444, #111143, #128666):
    - Added gpmhelper.py to listen for HAL button-events and issue
      dcop calls to guidance-power-manager.
    - guidance-power-manager will now start gpmhelper.py.
    - Patched setup.py to build/install gpmhelper.py
  * Changed debian/rules and debian/kde-guidance-powermanager.install
    to install gpmhelper.py
  * Added depends for kde-guidance-powermanager to python-gobject as
    this is the only mainloop to work with DBusGMainLoop.

  [ Scott Kitterman ]
  * Update kubuntu_12_powermanager_survive_no_brightness.patch so it correctly
    catches the error (LP: #183656)
  * Add kubuntu_20_displayconfig_no_resolutions.patch so displayconfig doesn't
    crash if current display size or refresh rate can't be fetched and similar
    changes for displayconfig-restore(LP: #147721, #110853)
  * Add kubuntu_21_powermanager_new_names.patch to use new hal keys
    (LP: #204768)
    - Patch thanks to Mikael Gerdin

 -- Scott Kitterman <email address hidden> Tue, 25 Mar 2008 13:04:50 -0400

Changed in kde-guidance:
status: In Progress → Fix Released
Alexander Sack (asac)
Changed in network-manager:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.