GNOME Bugzilla – Bug 463403
crash in Multimedia Systems Selector: trying to get sound to w...
Last modified: 2007-09-09 09:28:56 UTC
Version: 2.18.0 What were you doing when the application crashed? trying to get sound to work Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 34263040 vsize: 34263040 resident: 15253504 share: 11534336 rss: 15253504 rss_rlim: 4294967295 CPU usage: start_time: 1186227543 rtime: 126 utime: 116 stime: 10 cutime:3 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 -1226000720 (LWP 19807)] (no debugging symbols found) 0xb73d4ae1 in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 152762
Thread 1 (Thread -1226000720 (LWP 19807))
----------- .xsession-errors (32015092 sec old) --------------------- the application. The application 'smart-notifier' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. Window manager warning: Lost connection to the display ':0.0'; most likely the X server was shut down or you killed/destroyed the window manager. (gnome-panel:7083): Gnome-CRITICAL **: gnome_program_get_app_version: assertion `program != NULL' failed The application 'gnome-cups-icon' lost its connection to the display :0.0; most likely the X server was shut down or you killed/destroyed the application. The application 'gnome_segv2' lost its connection to the display localhost:0.0; most likely the X server was shut down or you killed/destroyed the application. --------------------------------------------------
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 ***