GNOME Bugzilla – Bug 486327
crash in Power Manager: This is some kind of rac...
Last modified: 2007-10-31 09:48:29 UTC
What were you doing when the application crashed? This is some kind of race condition. When I first login power manager crashes, however if I start it later by hand it works fine. Distribution: Fedora release 7.92 (Rawhide) Gnome Release: 2.20.0 2007-09-27 (Red Hat, Inc) BugBuddy Version: 2.20.0 System: Linux 2.6.23-5.fc8 #1 SMP Wed Oct 10 20:23:30 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000001 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 31129600 vsize: 31129600 resident: 9736192 share: 6823936 rss: 9736192 rss_rlim: 4294967295 CPU usage: start_time: 1192285916 rtime: 24 utime: 18 stime: 6 cutime:8 cstime: 14 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-power-manager' (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 -1208297712 (LWP 4101)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 169968
Thread 1 (Thread -1208297712 (LWP 4101))
----------- .xsession-errors (17 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Hope this helps. Distribution: Fedora release 8 (Werewolf) Gnome Release: 2.20.1 2007-10-15 (Red Hat, Inc) BugBuddy Version: 2.20.1 System: Linux 2.6.23.1-37.fc8 #1 SMP Fri Oct 26 12:36:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 42819584 vsize: 42819584 resident: 9695232 share: 6770688 rss: 9695232 rss_rlim: 4294967295 CPU usage: start_time: 1193787420 rtime: 16 utime: 14 stime: 2 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 -1208579488 (LWP 3503)] 0x00110402 in __kernel_vsyscall ()
+ Trace 174057
Thread 1 (Thread -1208579488 (LWP 3503))
----------- .xsession-errors (21 sec old) --------------------- ** Message: Connecting... ** Message: Status 1 ** Message: Making serial port connection ** (gnome-phone-manager:3416): WARNING **: Unknown status 19 conn_complete: status 0x00 ** (gnome-phone-manager:3416): WARNING **: Model SGH-A701 not supported natively ** Message: Using driver 'AT' ** Message: Status 2 ** Message: Serial port connected ** Message: Connected to device on 00:18:AF:33:EE:D9 ** Message: Exiting connect thread ** Message: driver supports sms notifications error getting update info: Cannot retrieve repository metadata (repomd.xml) for repository: google. Please verify its path and try again --------------------------------------------------
Thanks for the extra information. With it, we were able to determine that this particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 484516 ***