GNOME Bugzilla – Bug 357412
[libbacon] crash on startup
Last modified: 2011-11-11 10:03:55 UTC
Version: 2.16.0 What were you doing when the application crashed? Just launching. Distribution: Fedora Core release 5.92 (FC6 Test3) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 Memory status: size: 23154688 vsize: 0 resident: 23154688 share: 0 rss: 5259264 rss_rlim: 0 CPU usage: start_time: 1159076392 rtime: 0 utime: 4 stime: 0 cutime:3 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-monitor' (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 -1208890960 (LWP 7406)] 0xb7f49410 in __kernel_vsyscall ()
+ Trace 73107
Thread 1 (Thread -1208890960 (LWP 7406))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
(In reply to comment #1) > I installed debuginfo, but unfortunately since then I'm not able to reproduce this situation anymore. If it happens the callstack information will be attached.
Happened again: Distribution: Fedora Core release 5.92 (FC6 Test3) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 Memory status: size: 23171072 vsize: 0 resident: 23171072 share: 0 rss: 5259264 rss_rlim: 0 CPU usage: start_time: 1160920745 rtime: 0 utime: 3 stime: 0 cutime:2 cstime: 0 timeout: 1 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-monitor' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1209067088 (LWP 459)] 0xb7f1e410 in __kernel_vsyscall ()
+ Trace 76460
Thread 1 (Thread -1209067088 (LWP 459))
But it's probably still not fully useful because not all of debug info were found. Is there a possibility to configure the GNOME to producing core files instead of launching the bugbuddy technique, which seems to be rather the unusable method? Having a core file, I would be able to load it under the gdb at any time and install all necessary debug information later. Also the idea given in comment #1 is not very helpfull in all cases. In my case the problem happen very rarely and is not 100% reproducible. It happen only when the system is very loaded and I clicking a few times on System Monitor Icon. It will probably never happen when I simply run it under gdb/ddd.
something is wrong with libbacon 672 conn = bacon_message_connection_new ("gnome-system-monitor"); 673 if (!conn) g_error("Couldn't connect to gnome-system-monitor");
*** Bug 442003 has been marked as a duplicate of this bug. ***
*** Bug 462900 has been marked as a duplicate of this bug. ***
This bug was reported against a GNOME version that is now not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. The current stable GNOME is 2.32.1. Please check if the problem you reported here still occurs with a recent version of GNOME by reporting back which exact version you tested against Thank you for reporting this bug and we are sorry it could not be fixed for your version. Without feedback this report will be closed as INCOMPLETE in 6 weeks.