GNOME Bugzilla – Bug 479505
crash in Volume Control: setting up the sound car...
Last modified: 2007-10-03 09:57:21 UTC
Version: 2.18.0 What were you doing when the application crashed? setting up the sound card. This is the third time this has happened 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:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 279474176 vsize: 279474176 resident: 16748544 share: 11366400 rss: 16748544 rss_rlim: 18446744073709551615 CPU usage: start_time: 1190549741 rtime: 632 utime: 575 stime: 57 cutime:2 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912677490160 (LWP 3625)] (no debugging symbols found) 0x00002aaaafd0e865 in waitpid () from /lib64/libpthread.so.0
+ Trace 164830
Thread 1 (Thread 46912677490160 (LWP 3625))
----------- .xsession-errors --------------------- localuser:root being added to access control list SESSION_MANAGER=local/c-24-22-136-166.hsd1.wa.comcast.net:/tmp/.ICE-unix/3312 (process:3520): 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:3625): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed --------------------------------------------------
Could you please try to reproduce this after installing the debuginfo packages for the relevant libraries?
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 471133 ***