Ubuntu
kde-guidance package

[feisty] guidance-power-manager crashes on launch

Bug #96411 reported by bhansley
6
Affects Status Importance Assigned to Milestone
kde-guidance (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: kde-guidance-powermanager

After feisty upgrade (don't know if it's related...) but kde guidance crashes at launch, resulting in

KCrash: Application 'guidance-power-manager.py' crashing...

(This doesn't seem like much help, but I can't find more crash/bug details to report.)

ProblemType: Bug
Architecture: i386
Date: Mon Mar 26 06:32:32 2007
DistroRelease: Ubuntu 7.04
Uname: Linux cheese 2.6.20-12-386 #2 Wed Mar 21 20:53:13 UTC 2007 i686 GNU/Linux

Revision history for this message
Steve.Lewis (day-lewis) wrote :
Download full text (3.5 KiB)

I am experiencing the same behavior as described above after my upgrade to Feisty. I run a Dell Latitude D600.

KDE: 3.5.6
Architecture: i686

Uname:Linux 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

From kcrash:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1210701616 (LWP 5345)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb64e5454 in ?? () from /usr/...

Read more...

Revision history for this message
Sergio Cambra (sergio-ensanjose) wrote :

I have the same problem:
$ guidance-power-manager
$ X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 147
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 169
  Major opcode: 147
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
Traceback (most recent call last):
  File "/usr/share/python-support/kde-guidance/guidance-power-manager.py", line 1070, in <module>
    mainWindow = PowermanagerApp(None, "main window")
  File "/usr/share/python-support/kde-guidance/guidance-power-manager.py", line 1014, in __init__
    self.pmwidget.prepare()
  File "/usr/share/python-support/kde-guidance/guidance-power-manager.py", line 116, in prepare
    self.poll(False)
  File "/usr/share/python-support/kde-guidance/guidance-power-manager.py", line 663, in poll
    self._updateCpuWidgets()
  File "/usr/share/python-support/kde-guidance/guidance-power-manager.py", line 826, in _updateCpuWidgets
    self.systray.actionCollection().action(policy).setChecked(True)
AttributeError: 'NoneType' object has no attribute 'setChecked'
Error in sys.excepthook:
Traceback (most recent call last):
  File "/var/lib/python-support/python2.5/apport/python_hook.py", line 44, 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/guidance-power-manager.py", line 1070, in <module>
    mainWindow = PowermanagerApp(None, "main window")
  File "/usr/share/python-support/kde-guidance/guidance-power-manager.py", line 1014, in __init__
    self.pmwidget.prepare()
  File "/usr/share/python-support/kde-guidance/guidance-power-manager.py", line 116, in prepare
    self.poll(False)
  File "/usr/share/python-support/kde-guidance/guidance-power-manager.py", line 663, in poll
    self._updateCpuWidgets()
  File "/usr/share/python-support/kde-guidance/guidance-power-manager.py", line 826, in _updateCpuWidgets
    self.systray.actionCollection().action(policy).setChecked(True)
AttributeError: 'NoneType' object has no attribute 'setChecked'

Revision history for this message
Sergio Cambra (sergio-ensanjose) wrote :

Latest package is working for me now.

Revision history for this message
Matthew Carpenter (matt-eisgr) wrote :

Latest package is *NOT* working for me.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1210255152 (LWP 8807)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0x45450454 in ?? () from /usr/lib/libXrandr.so.2
#7 0x000106b9 in ?? ()
#8 0x085e9948 in ?? ()
#9 0x00000048 in ?? ()
#10 0xb71d5b2c in ?? () from /usr/lib/libX11.so.6
#11 0x00000000 in ?? ()

Changed in kde-guidance:
status: Unconfirmed → Confirmed
Revision history for this message
Sebastian Kügler (sebasje) wrote :

The last stacktrace is pretty useless, and I suppose it's another bug you're hitting. Can you open another bugreport for that one and attach the command-line output when running powermanager to it?

Changed in kde-guidance:
status: Confirmed → Fix Released
Revision history for this message
Matthew Carpenter (matt-eisgr) wrote :

Finally, after a recent dist-upgrade guidance-power-manager started working (aside from the CPU speed indications)
As for command line, there is no feedback. The crash was always a "KDE app" crash.

Revision history for this message
sulla (wolfgang-sailer) wrote :
Download full text (5.4 KiB)

I am experiencing the same problem since my dist-upgrade to feisty yesterday:

System: PC with Asus A8V deluxe mainboard, AMD Athlon 3000+ Winchester, Nvidia 6600GT (bindary driver), dual DVI screens in Xinerama mode.

There seems to be no updated packages available, at least adept does not offer any. (as of 2007-04-22 16:51 GMT)

Every login KDE crashes guidance-power-manager. This is the log I get (I also get it when I run guidance-power-manager from a terminal (the command line feedback is ":KCrash: Application 'guidance-power-manager.py' crashing...", then a KDE Kcrash window pops up with the following backtrace):

=========================================
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47747381356272 (LWP 5628)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5 0x00002b6d126b4a45 in ?? () from /usr/lib/libXrandr.so.2
#6 0x00002b6d126b4...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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