Bug 469101 – crash in Sound Juicer CD Extractor: ripping 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 469101 - crash in Sound Juicer CD Extractor: ripping a cd


Summary:	crash in Sound Juicer CD Extractor: ripping a cd


Status:	RESOLVED DUPLICATE of bug 465971

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-08-22 04:02 UTC by Shyiskhar
Modified:	2007-08-22 13:39 UTC

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

Description Shyiskhar 2007-08-22 04:02:39 UTC

Version: 2.16.4

What were you doing when the application crashed?
ripping 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.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 110030848 vsize: 110030848 resident: 31535104 share: 22183936 rss: 31535104 rss_rlim: 4294967295
CPU usage: start_time: 1187754332 rtime: 59261 utime: 57513 stime: 1748 cutime:5 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 -1208435840 (LWP 2817)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 157034

Thread 1 (Thread -1208435840 (LWP 2817))

#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 (16 sec old) ---------------------
--- Hash table keys for warning below:
--> file:///home/kal
(nautilus:2725): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
(sound-juicer:2540): GLib-CRITICAL **: g_source_remove: assertion `tag > 0' failed
(synaptic:2798): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed
** (sound-juicer:2817): WARNING **: Could not lock drive: Extracting audio from CD
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2a0001f specified for 0x2a00431 (Choose a d).
gnome-mount 0.6
Ejected /dev/scd0
(sound-juicer:2817): GLib-CRITICAL **: g_source_remove: assertion `tag > 0' failed
--------------------------------------------------

Comment 1 palfrey 2007-08-22 13:39:37 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 465971 ***