GNOME Bugzilla – Bug 449308
crash in Sound: Went into Sound Preferen...
Last modified: 2007-06-20 02:04:05 UTC
Version: 2.19.3 What were you doing when the application crashed? Went into Sound Preferences because I was getting this message very often: "Couldn't open audio Please check that: Your soundcard is configured properly. You have the correct output plugin selected. No other Program is blocking the soundcard". This usually hapens when I am playing mp3 in xmm and another program produce any sound, for example, incoming message in kopete. Distribution: Fedora release 7.89 (Rawhide) Gnome Release: 2.19.3 2007-06-04 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-2925.10.fc8xen #1 SMP Mon Jun 11 15:31:58 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: gnome Memory status: size: 47681536 vsize: 47681536 resident: 23031808 share: 19992576 rss: 23031808 rss_rlim: 4294967295 CPU usage: start_time: 1182294969 rtime: 32 utime: 28 stime: 4 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-sound-properties' (no debugging symbols found) Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209112864 (LWP 9151)] (no debugging symbols found) 0x0021d402 in __kernel_vsyscall ()
+ Trace 142288
Thread 1 (Thread -1209112864 (LWP 9151))
----------- .xsession-errors (9 sec old) --------------------- Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply! QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver QApplication::postEvent: Unexpected null receiver --------------------------------------------------
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 413801 ***