Bug 473639 – crash in Sound Juicer CD Extractor: just extrac CD audio and...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 473639 - crash in Sound Juicer CD Extractor: just extrac CD audio and...


Summary:	crash in Sound Juicer CD Extractor: just extrac CD audio and...


Status:	RESOLVED DUPLICATE of bug 471853

Product:	sound-juicer
Classification:	Applications
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Sound Juicer Maintainers
QA Contact:	Sound Juicer Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-04 17:45 UTC by herle.cariou
Modified:	2007-09-05 15:41 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description herle.cariou 2007-09-04 17:45:05 UTC

Version: 2.16.4

What were you doing when the application crashed?
just extrac CD audio and  look  teh weeb for mozilla


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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 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: 89186304 vsize: 89186304 resident: 27971584 share: 20320256 rss: 27971584 rss_rlim: 4294967295
CPU usage: start_time: 1188926753 rtime: 24096 utime: 19082 stime: 5014 cutime:7 cstime: 1 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 -1208497280 (LWP 5281)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 160437

Thread 1 (Thread -1208497280 (LWP 5281))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 gtk_list_store_set_valist
from /usr/lib/libgtk-x11-2.0.so.0
#5 gtk_list_store_set
from /usr/lib/libgtk-x11-2.0.so.0
#6 ??
#7 ??
#8 ??
#9 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#10 g_closure_invoke
from /lib/libgobject-2.0.so.0
#11 ??
from /lib/libgobject-2.0.so.0
#12 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#13 g_signal_emit
from /lib/libgobject-2.0.so.0
#14 ??
#15 ??
from /usr/lib/libgstreamer-0.10.so.0
#16 g_closure_invoke
from /lib/libgobject-2.0.so.0
#17 ??
from /lib/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#19 g_signal_emit
from /lib/libgobject-2.0.so.0
#20 gst_bus_async_signal_func
from /usr/lib/libgstreamer-0.10.so.0
#21 ??
from /usr/lib/libgstreamer-0.10.so.0
#22 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#23 ??
from /lib/libglib-2.0.so.0
#24 g_main_loop_run
from /lib/libglib-2.0.so.0
#25 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#26 main
#0 __kernel_vsyscall



----------- .xsession-errors (1140 sec old) ---------------------
                 System error: Périphérique ou ressource occupé
scsi_read error: sector=146 length=1 retry=7
                 Sense key: 2 ASC: 3a ASCQ: 0
                 Transport error: Device busy
                 System error: Périphérique ou ressource occupé
scsi_read error: sector=146 length=1 retry=8
                 Sense key: 2 ASC: 3a ASCQ: 0
                 Transport error: Device busy
                 System error: Périphérique ou ressource occupé
scsi_read error: sector=2 length=24 retry=0
                 Sense key: 2 ASC: 3a ASCQ: 0
                 Transport error: Device busy
                 System error: Périphérique ou ressource occupé
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 palfrey 2007-09-05 15:41:14 UTC

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 471853 ***