After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 486327 - crash in Power Manager: This is some kind of rac...
crash in Power Manager: This is some kind of rac...
Status: RESOLVED DUPLICATE of bug 484516
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-manager
2.17.x
Other All
: High critical
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-10-13 14:34 UTC by Malcolm Caldwell
Modified: 2007-10-31 09:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Malcolm Caldwell 2007-10-13 14:34:05 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 ()

Thread 1 (Thread -1208297712 (LWP 4101))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 g_cclosure_marshal_VOID__BOOLEAN
  • #10 g_cclosure_marshal_VOID
    from /lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #12 ??
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #15 g_cclosure_marshal_VOID__BOOLEAN
  • #16 g_cclosure_marshal_VOID
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #18 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #22 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #23 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #24 ??
    from /usr/lib/libdbus-glib-1.so.2
  • #25 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #26 ??
    from /lib/libglib-2.0.so.0
  • #27 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #28 g_cclosure_marshal_VOID__BOOLEAN
  • #29 __libc_start_main
    from /lib/libc.so.6
  • #30 g_cclosure_marshal_VOID__BOOLEAN
  • #0 __kernel_vsyscall




----------- .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
--------------------------------------------------
Comment 1 palfrey 2007-10-29 14:29:07 UTC
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!
Comment 2 Malcolm Caldwell 2007-10-31 01:48:54 UTC
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 ()

Thread 1 (Thread -1208579488 (LWP 3503))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 369
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 677
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 google_breakpad::ExceptionHandler::HandleException
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 <signal handler called>
  • #9 phone_device_removed_cb
    at gpm-cell-array.c line 1198
  • #10 IA__g_cclosure_marshal_VOID__UINT
    at gmarshal.c line 251
  • #11 IA__g_closure_invoke
    at gclosure.c line 490
  • #12 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #13 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #14 IA__g_signal_emit
    at gsignal.c line 2243
  • #15 gpm_phone_num_batteries_changed
    at gpm-phone.c line 186
  • #16 IA__g_cclosure_marshal_VOID__UINT
    at gmarshal.c line 251
  • #17 marshal_dbus_message_to_g_marshaller
    at dbus-gproxy.c line 1635
  • #18 IA__g_closure_invoke
    at gclosure.c line 490
  • #19 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #20 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #21 IA__g_signal_emit
    at gsignal.c line 2243
  • #22 dbus_g_proxy_manager_filter
    at dbus-gproxy.c line 1688
  • #23 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #24 message_queue_dispatch
    at dbus-gmain.c line 101
  • #25 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #26 g_main_context_iterate
    at gmain.c line 2694
  • #27 IA__g_main_loop_run
    at gmain.c line 2898
  • #28 main
    at gpm-main.c line 267
  • #29 __libc_start_main
    from /lib/libc.so.6
  • #30 _start
  • #0 __kernel_vsyscall




----------- .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
--------------------------------------------------
Comment 3 palfrey 2007-10-31 09:48:29 UTC
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 ***