Bug 473905 – crash in Sound Juicer CD Extractor: Taking a (legit) copy of...

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 473905 - crash in Sound Juicer CD Extractor: Taking a (legit) copy of...


Summary:	crash in Sound Juicer CD Extractor: Taking a (legit) copy of...


Status:	RESOLVED DUPLICATE of bug 468977

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-05 13:36 UTC by fedora.bugs
Modified:	2007-09-05 15:41 UTC

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

Description fedora.bugs 2007-09-05 13:36:45 UTC

Version: 2.16.4

What were you doing when the application crashed?
Taking a (legit) copy of FleetwoodMac Tusk (disc 1).
Half way through SoundJuicer reported an error (unable to open disk), then crashed when I clicked 'Ok'.
CD was in standard CD reader, and target directory is on a software RAID partition.
Will try again with the same disk.


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 21:50:50 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: DarkGilouche
Icon Theme: Clearlooks

Memory status: size: 487481344 vsize: 487481344 resident: 36634624 share: 26370048 rss: 36634624 rss_rlim: 18446744073709551615
CPU usage: start_time: 1188997272 rtime: 113879 utime: 76061 stime: 37818 cutime:2 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496328480 (LWP 1894)]
(no debugging symbols found)
0x00000033c0e0d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 160636

Thread 1 (Thread 46912496328480 (LWP 1894))

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



----------- .xsession-errors (158080 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 palfrey 2007-09-05 15:41:26 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 468977 ***