GNOME Bugzilla – Bug 484516
crash in Power Manager: I was logging in to my s...
Last modified: 2009-06-26 16:29:11 UTC
What were you doing when the application crashed? I was logging in to my system, then gnome-power-manager decided to crash. Oh the joy. Distribution: Gentoo Base System release 1.12.10 Gnome Release: 2.20.0 2007-09-19 (Gentoo) BugBuddy Version: 2.20.0 System: Linux 2.6.22.5 #4 PREEMPT Wed Oct 3 20:26:53 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 38596608 vsize: 38596608 resident: 10129408 share: 7168000 rss: 10129408 rss_rlim: 4294967295 CPU usage: start_time: 1191791865 rtime: 16 utime: 15 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-power-manager' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1227687712 (LWP 6200)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 168617
Thread 1 (Thread -1227687712 (LWP 6200))
----------- .xsession-errors --------------------- reply: 0x01 / 0x000a 01 79 00 f0 01 20 00 00 00 00 | y Please read Docs/Bugs and send a bug report! UNHANDLED FRAME RECEIVED request: 0x01 / 0x0004 00 01 00 20 | reply: 0x01 / 0x000a 01 79 00 f0 01 20 00 00 00 00 | y Please read Docs/Bugs and send a bug report! UNHANDLED FRAME RECEIVED request: 0x01 / 0x0004 00 01 00 20 | reply: 0x01 / 0x000a 01 79 00 f0 01 20 00 00 00 00 | y Please read Docs/Bugs and send a bug report! --------------------------------------------------
*** Bug 486327 has been marked as a duplicate of this bug. ***
Oh, this is an easy fix. Just stop gnome-phone-manager, as the version I was using was kind of broken. But it still should not crash gnome-power-manager.
Can you try trunk for me please? I've just committed this: 2007-11-02 Richard Hughes <richard@hughsie.com> * src/gpm-cell-array.c: (phone_device_removed_cb): Check to see if we have a gnome-phone-manager device before we unref it - I've a sneaking suspicion gnome-phone-manager is telling us Remove before Added at session start, although we certainly shouldn't crash out in this case. Hopefully fixes #484516
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
*** Bug 586943 has been marked as a duplicate of this bug. ***
Bug 586943 was reported using GPM 2.24, which included Revision #2551. http://svn.gnome.org/viewvc/gnome-power-manager/branches/gnome-2-24/src /gpm-cell-array.c?view=log Therefore, GPM 2.24 should have had the fix included. It looks like the fix Richard Hughes commited on 2007-11-02 (revision 2551) did not solve the bug. Additionally, the reporter also performed the following tests: In GPM 2.27.1: The battery level for the phone, as reported by gnome-power-manager, is 0, which might mean that it doesn't comunicate too well with gnome- phone-manager. If it did, it might crash, or not... Next I compiled gnome-phone-manager trunk, and it still doesn't work; and both power-manager and phone-manager from trunk, and it doesn't work. original report: https://bugs.launchpad.net/bugs/333910 original bug (marked as duplicate) and stack trace at Bug 586943