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 a
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.
--
[feisty] guidance-power-manager crashes on launch
https://bugs.launchpad.net/bugs/96411
You r
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 (Ubuntu)
Status: Confirmed => Fix Released
--
[feisty] guidance
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 sym
Latest package is working for me now.
--
[feisty] guidance-power-manager crashes on launch
https://launchpad.net/bugs/96411
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
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
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 libra
