GNOME Bugzilla – Bug 502065
crash in Volume Control:
Last modified: 2007-12-06 19:19:41 UTC
Version: 2.18.0 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 35954688 vsize: 35954688 resident: 12349440 share: 9207808 rss: 12349440 rss_rlim: 4294967295 CPU usage: start_time: 1196971652 rtime: 324 utime: 236 stime: 88 cutime:4 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-volume-control' (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 -1208354576 (LWP 19464)] (no debugging symbols found) 0x00f08402 in __kernel_vsyscall ()
+ Trace 180982
Thread 1 (Thread -1208354576 (LWP 19464))
----------- .xsession-errors (38 sec old) --------------------- 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. (process:19408): 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. (gnome-volume-control:19464): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed --------------------------------------------------
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 492166 ***