GNOME Bugzilla – Bug 483524
crash in Sound Juicer CD Extractor: Trying to extract a CD. ...
Last modified: 2007-10-05 10:34:21 UTC
Version: 2.20.0 What were you doing when the application crashed? Trying to extract a CD. Got a box telling me it couldn't open the CD for reading and then instantly crashed afterwards. Sounds like something isn't getting cleaned up in this situation. Distribution: Gentoo Base System release baselayout-2.0.0_rc4-r1 Gnome Release: 2.20.0 2007-09-18 (Gentoo) BugBuddy Version: 2.20.0 System: Linux 2.6.22-gentoo-r8 #1 SMP Fri Sep 28 16:37:33 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Echo Memory status: size: 355381248 vsize: 355381248 resident: 25014272 share: 15196160 rss: 25014272 rss_rlim: 18446744073709551615 CPU usage: start_time: 1191539396 rtime: 63211 utime: 53335 stime: 9876 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/sound-juicer' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47398889806832 (LWP 4433)] 0x00002b1be0f7aadf in __libc_waitpid (pid=4489, stat_loc=0x7fffc9d84a20, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 167831
Thread 1 (Thread 47398889806832 (LWP 4433))
----------- .xsession-errors --------------------- Transport error: Device busy System error: Device or resource busy scsi_read error: sector=110613 length=13 retry=0 Sense key: 2 ASC: 4 ASCQ: 8 Transport error: Device busy System error: Device or resource busy scsi_read error: sector=112713 length=13 retry=0 Sense key: 2 ASC: 4 ASCQ: 8 Transport error: Device busy System error: Device or resource busy scsi_read error: sector=122424 length=13 retry=0 Sense key: 2 ASC: 4 ASCQ: 8 Transport error: Device busy System error: Device or resource busy 41 ../sysdeps/unix/sysv/linux/waitpid.c: No such file or directory. --------------------------------------------------
God damn it, a report of this on 2.20. I was hoping it was fixed. *** This bug has been marked as a duplicate of 403870 ***