Bug 451869 – crash in Rhythmbox Music Player: nothing

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 451869 - crash in Rhythmbox Music Player: nothing


Summary:	crash in Rhythmbox Music Player: nothing


Status:	RESOLVED DUPLICATE of bug 336370

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.9.6
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-28 13:14 UTC by hanan.vax
Modified:	2007-06-28 13:17 UTC

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

Description hanan.vax 2007-06-28 13:14:22 UTC

What were you doing when the application crashed?
nothing


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

Memory status: size: 275603456 vsize: 275603456 resident: 32907264 share: 17076224 rss: 32907264 rss_rlim: -1
CPU usage: start_time: 1183033872 rtime: 1956 utime: 1509 stime: 447 cutime:4 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47610606191584 (LWP 20427)]
[New Thread 1124362576 (LWP 20464)]
[New Thread 1115969872 (LWP 20460)]
[New Thread 1082132816 (LWP 20459)]
[New Thread 1107310928 (LWP 20458)]
[New Thread 1090525520 (LWP 20457)]
[New Thread 1107577168 (LWP 20456)]
[New Thread 1098918224 (LWP 20444)]
0x00002b4d34a9c7f6 in poll () from /lib/libc.so.6

+ Trace 144314

Thread 6 (Thread 1090525520 (LWP 20457))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 g_logv
from /usr/lib64/libglib-2.0.so.0
#6 g_log
from /usr/lib64/libglib-2.0.so.0
#7 g_assert_warning
from /usr/lib64/libglib-2.0.so.0
#8 gst_asf_demux_parse_data
at gstasfdemux.c line 497
#9 gst_asf_demux_chain
at gstasfdemux.c line 389
#10 gst_pad_alloc_buffer
from /usr/lib64/libgstreamer-0.10.so.0
#11 gst_pad_push
from /usr/lib64/libgstreamer-0.10.so.0
#12 gst_type_find_element_get_type
from /usr/lib/gstreamer-0.10/libgstcoreelements.so
#13 gst_pad_alloc_buffer
from /usr/lib64/libgstreamer-0.10.so.0
#14 gst_pad_push
from /usr/lib64/libgstreamer-0.10.so.0
#15 gst_pad_alloc_buffer
from /usr/lib64/libgstreamer-0.10.so.0
#16 gst_pad_push
from /usr/lib64/libgstreamer-0.10.so.0
#17 gst_base_src_get_type
from /usr/lib64/libgstbase-0.10.so.0
#18 gst_task_set_lock
from /usr/lib64/libgstreamer-0.10.so.0
#19 g_thread_pool_push
from /usr/lib64/libglib-2.0.so.0
#20 g_thread_create_full
from /usr/lib64/libglib-2.0.so.0
#21 start_thread
from /lib/libpthread.so.0
#22 clone
from /lib/libc.so.6
#23 ??

Comment 1 Christian Kirbach 2007-06-28 13:17:06 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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