Bug 376790 – crash in Sound Juicer CD Extractor: Ripping Fourty Licks by ...

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 376790 - crash in Sound Juicer CD Extractor: Ripping Fourty Licks by ...


Summary:	crash in Sound Juicer CD Extractor: Ripping Fourty Licks by ...


Status:	RESOLVED DUPLICATE of bug 362896

Product:	sound-juicer
Classification:	Applications
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-18 21:51 UTC by pianoboy3333
Modified:	2006-11-19 19:56 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description pianoboy3333 2006-11-18 21:51:15 UTC

What were you doing when the application crashed?
Ripping Fourty Licks by the Rolling Stones into 192 kbps MP3's. To ~/music/


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 85270528 vsize: 0 resident: 85270528 share: 0 rss: 20393984 rss_rlim: 0
CPU usage: start_time: 1163886418 rtime: 0 utime: 14696 stime: 0 cutime:14332 cstime: 0 timeout: 364 it_real_value: 0 frequency: 4

Backtrace was generated from '/usr/bin/sound-juicer'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227601504 (LWP 23641)]
[New Thread -1279177824 (LWP 23676)]
[New Thread -1246839904 (LWP 23674)]
[New Thread -1238447200 (LWP 23673)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 87550

Thread 4 (Thread -1238447200 (LWP 23673))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 __fsetlocking
from /lib/tls/i686/cmov/libc.so.6
#8 free
from /lib/tls/i686/cmov/libc.so.6
#9 g_free
from /usr/lib/libglib-2.0.so.0
#10 gst_buffer_get_type
from /usr/lib/libgstreamer-0.10.so.0
#11 gst_mini_object_unref
from /usr/lib/libgstreamer-0.10.so.0
#12 ??
from /usr/lib/gstreamer-0.10/libgstlame.so
#13 ??
#14 ??
#15 ??
#16 g_static_rec_mutex_lock
from /usr/lib/libglib-2.0.so.0
#17 gst_pad_send_event
from /usr/lib/libgstreamer-0.10.so.0
#18 gst_pad_push_event
from /usr/lib/libgstreamer-0.10.so.0
#19 gst_base_transform_get_type
from /usr/lib/libgstbase-0.10.so.0
#20 gst_pad_send_event
from /usr/lib/libgstreamer-0.10.so.0
#21 gst_pad_push_event
from /usr/lib/libgstreamer-0.10.so.0
#22 gst_base_transform_get_type
from /usr/lib/libgstbase-0.10.so.0
#23 gst_pad_send_event
from /usr/lib/libgstreamer-0.10.so.0
#24 gst_pad_push_event
from /usr/lib/libgstreamer-0.10.so.0
#25 gst_base_transform_get_type
from /usr/lib/libgstbase-0.10.so.0
#26 gst_pad_send_event
from /usr/lib/libgstreamer-0.10.so.0
#27 gst_pad_push_event
from /usr/lib/libgstreamer-0.10.so.0
#28 gst_proxy_pad_do_query_type
from /usr/lib/libgstreamer-0.10.so.0
#29 gst_pad_send_event
from /usr/lib/libgstreamer-0.10.so.0
#30 gst_pad_push_event
from /usr/lib/libgstreamer-0.10.so.0
#31 gst_queue_get_type
from /usr/lib/gstreamer-0.10/libgstcoreelements.so
#32 gst_task_set_lock
from /usr/lib/libgstreamer-0.10.so.0
#33 g_thread_pool_push
from /usr/lib/libglib-2.0.so.0
#34 g_thread_create_full
from /usr/lib/libglib-2.0.so.0
#35 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#36 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 Christian Kirbach 2006-11-19 19:56:51 UTC

crash in gstreamer
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 362896 ***