GNOME Bugzilla – Bug 488152
crash in Volume Control: Changing the volume
Last modified: 2007-10-19 11:07:46 UTC
Version: 2.18.0 What were you doing when the application crashed? Changing the volume 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 41250816 vsize: 41250816 resident: 12738560 share: 9617408 rss: 12738560 rss_rlim: 4294967295 CPU usage: start_time: 1192768247 rtime: 53 utime: 50 stime: 3 cutime:1 cstime: 0 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 -1208731408 (LWP 4899)] (no debugging symbols found) 0x00cc8402 in __kernel_vsyscall ()
+ Trace 171324
Thread 1 (Thread -1208731408 (LWP 4899))
----------- .xsession-errors (180 sec old) --------------------- 21:27:53 : Found 180 available packages 21:27:53 : Sorting packages 21:27:53 : Population view with packages 21:27:53 : Population Completed Unable to send message to yum-updatesd (process:4746): 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. sound-properties-Message: Error running pipeline 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink': Internal GStreamer error: state change failed. Please file a bug at Failed to set state on new child.] --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 471133 ***