GNOME Bugzilla – Bug 428113
crash in Sound: after installing sound d...
Last modified: 2007-04-10 17:59:00 UTC
Version: 2.18.0 What were you doing when the application crashed? after installing sound driver for AC'97 Distribution: Fedora release 6.92 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.3045.fc7 #1 SMP Wed Apr 4 19:20:07 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299903 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: OSX Memory status: size: 68435968 vsize: 68435968 resident: 15486976 share: 11169792 rss: 15486976 rss_rlim: 4294967295 CPU usage: start_time: 1176175306 rtime: 62 utime: 48 stime: 14 cutime:2 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-sound-properties' (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 -1208604960 (LWP 2615)] [New Thread -1219040368 (LWP 2617)] (no debugging symbols found) 0x00758402 in __kernel_vsyscall ()
+ Trace 126459
Thread 1 (Thread -1208604960 (LWP 2615))
----------- .xsession-errors (7 sec old) --------------------- GTK Panel of SCIM 1.4.5 Starting SCIM as daemon ... SCIM has been successfully launched. Smart Common Input Method 1.4.5 SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2252 (process:2615): GStreamer-WARNING **: The GStreamer function gst_init_get_option_group() was called, but the GLib threading system has not been initialised yet, something that must happen before any other GLib function is called. The application needs to be fixed so that it calls if (!g_thread_supported ()) g_thread_init(NULL); as very first thing in its main() function. Please file a bug against this application. --------------------------------------------------
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. Thanks in advance!
*** Bug 428246 has been marked as a duplicate of this bug. ***
Thanks for the bug report. 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 413801 ***