Bug 457340 – crash in Sound Juicer CD Extractor: trying to rip a cd

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 457340 - crash in Sound Juicer CD Extractor: trying to rip a cd


Summary:	crash in Sound Juicer CD Extractor: trying to rip a cd


Status:	RESOLVED DUPLICATE of bug 454140

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-07-16 12:41 UTC by keeker1
Modified:	2007-07-17 13:03 UTC

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

Description keeker1 2007-07-16 12:41:21 UTC

Version: 2.16.4

What were you doing when the application crashed?
trying to rip a cd


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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 105340928 vsize: 105340928 resident: 27721728 share: 21159936 rss: 27721728 rss_rlim: 4294967295
CPU usage: start_time: 1184589219 rtime: 625 utime: 468 stime: 157 cutime:1 cstime: 0 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 -1208816768 (LWP 13467)]
(no debugging symbols found)
0x00bd7402 in __kernel_vsyscall ()

+ Trace 148340

Thread 1 (Thread -1208816768 (LWP 13467))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_cclosure_marshal_VOID__VOID
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 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /lib/libgobject-2.0.so.0
#10 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#12 g_signal_emit
from /lib/libgobject-2.0.so.0
#13 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#16 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /lib/libgobject-2.0.so.0
#18 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#20 g_signal_emit
from /lib/libgobject-2.0.so.0
#21 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#22 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#23 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#24 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#25 g_closure_invoke
from /lib/libgobject-2.0.so.0
#26 g_cclosure_marshal_VOID__VOID
from /lib/libgobject-2.0.so.0
#27 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#28 g_signal_emit
from /lib/libgobject-2.0.so.0
#29 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#31 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#32 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgdk-x11-2.0.so.0
#33 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#34 g_cclosure_marshal_VOID__VOID
from /lib/libglib-2.0.so.0
#35 g_main_loop_run
from /lib/libglib-2.0.so.0
#36 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#37 main
#0 __kernel_vsyscall



----------- .xsession-errors (60999 sec old) ---------------------
Error trying to open /dev/sgx exclusively (No such file or directory). retrying in 1 second.
Error trying to open /dev/sg24 exclusively (No such file or directory). retrying in 1 second.
Error trying to open /dev/sg24 exclusively (No such file or directory). retrying in 1 second.
Error trying to open /dev/sg24 exclusively (No such file or directory). retrying in 1 second.
Error trying to open /dev/sg24 exclusively (No such file or directory). retrying in 1 second.
Error trying to open /dev/sg24 exclusively (No such file or directory). retrying in 1 second.
Error trying to open /dev/sg24 exclusively (No such file or directory). retrying in 1 second.
Error trying to open /dev/sg24 exclusively (No such file or directory). retrying in 1 second.
Error trying to open /dev/sg24 exclusively (No such file or directory). retrying in 1 second.
Error trying to open /dev/sg24 exclusively (No such file or directory). retrying in 1 second.
Error trying to open /dev/sg24 exclusively (No such file or directory). retrying in 1 second.
Error trying to open /dev/sgy exclusively (No such file or directory). retrying in 1 second.
Error trying to open /dev/sgy exclusively (No such file or directory). retrying in 1 second.
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Pedro Villavicencio 2007-07-17 13:03:17 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 454140 ***