GNOME Bugzilla – Bug 478607
crash in Sound Juicer CD Extractor: With copying a CD to Mus...
Last modified: 2007-09-30 15:23:05 UTC
Version: 2.16.4 What were you doing when the application crashed? With copying a CD to Music folder, I have used Telnet to connect my college. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 103714816 vsize: 103714816 resident: 29814784 share: 20004864 rss: 29814784 rss_rlim: 4294967295 CPU usage: start_time: 1190294307 rtime: 158421 utime: 138797 stime: 19624 cutime:10 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/sound-juicer' (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 -1209078912 (LWP 7369)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 164139
Thread 1 (Thread -1209078912 (LWP 7369))
----------- .xsession-errors (23 sec old) --------------------- 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 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 --------------------------------------------------
*** This bug has been marked as a duplicate of 403870 ***