GNOME Bugzilla – Bug 506602
crash in Multimedia Systems Selector:
Last modified: 2008-01-19 16:39:54 UTC
Version: 2.18.0 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 38674432 vsize: 38674432 resident: 21594112 share: 17547264 rss: 21594112 rss_rlim: 4294967295 CPU usage: start_time: 1199122810 rtime: 31 utime: 28 stime: 3 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gstreamer-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 -1208453408 (LWP 3162)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 183653
Thread 1 (Thread -1208453408 (LWP 3162))
----------- .xsession-errors (32 sec old) --------------------- localuser:fil being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2891 ** (gnome-session:2891): WARNING **: Esound failed to start. gstreamer-properties-Message: Skipping unavailable plugin 'artsdsink' gstreamer-properties-Message: Skipping unavailable plugin 'pulsesink' gstreamer-properties-Message: Skipping unavailable plugin 'sdlvideosink' gstreamer-properties-Message: Skipping unavailable plugin 'v4lmjpegsrc' gstreamer-properties-Message: Skipping unavailable plugin 'qcamsrc' gstreamer-properties-Message: Skipping unavailable plugin 'esdmon' gstreamer-properties-Message: Skipping unavailable plugin 'pulsesrc' --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 413801 ***