Bug 384124 – crash in Rhythmbox Music Player: Clicking the "Next" to g...

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 384124 - crash in Rhythmbox Music Player: Clicking the "Next" to g...


Summary:	crash in Rhythmbox Music Player: Clicking the "Next" to g...


Status:	RESOLVED DUPLICATE of bug 361681

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:	2006-12-09 18:22 UTC by john.elements
Modified:	2006-12-22 20:49 UTC

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

Description john.elements 2006-12-09 18:22:07 UTC

What were you doing when the application crashed?
Clicking the "Next" to go onto the next song


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

Memory status: size: 129884160 vsize: 0 resident: 129884160 share: 0 rss: 19300352 rss_rlim: 0
CPU usage: start_time: 1165456164 rtime: 0 utime: 79753 stime: 0 cutime:77342 cstime: 0 timeout: 2411 it_real_value: 0 frequency: 9

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

(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 -1228646736 (LWP 17053)]
[New Thread -1354765408 (LWP 840)]
[New Thread -1336046688 (LWP 836)]
[New Thread -1269630048 (LWP 17064)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 92853

Thread 1 (Thread -1228646736 (LWP 17053))

#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 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 ??
from /usr/lib/libgthread-2.0.so.0
#10 ??
from /usr/lib/libgthread-2.0.so.0
#11 ??
#12 ??
from /usr/lib/libgthread-2.0.so.0
#13 ??
from /usr/lib/libgthread-2.0.so.0
#14 ??
#15 ??
from /usr/lib/libgthread-2.0.so.0
#16 _nl_default_dirname
from /lib/tls/i686/cmov/libc.so.6
#17 ??
from /usr/lib/libgthread-2.0.so.0
#18 ??
from /usr/lib/libgstaudio-0.10.so.0
#19 ??
#20 ??
#21 gst_audio_sink_get_type
from /usr/lib/libgstaudio-0.10.so.0
#22 gst_audio_sink_get_type
from /usr/lib/libgstaudio-0.10.so.0
#23 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#24 gst_object_unref
from /usr/lib/libgstreamer-0.10.so.0
#25 gst_object_unparent
from /usr/lib/libgstreamer-0.10.so.0
#26 gst_base_audio_sink_get_type
from /usr/lib/libgstaudio-0.10.so.0
#27 ??
from /usr/lib/gstreamer-0.10/libgstalsa.so
#28 ??
#29 ??
#30 __after_morecore_hook
from /lib/tls/i686/cmov/libc.so.6
#31 ??
from /usr/lib/libgobject-2.0.so.0
#32 ??
from /usr/lib/gstreamer-0.10/libgstalsa.so
#33 ??
from /usr/lib/libgobject-2.0.so.0
#34 ??
#35 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#36 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#37 gst_object_unref
from /usr/lib/libgstreamer-0.10.so.0
#38 gst_message_new_eos
from /usr/lib/libgstreamer-0.10.so.0
#39 gst_mini_object_unref
from /usr/lib/libgstreamer-0.10.so.0
#40 gst_bus_pop
from /usr/lib/libgstreamer-0.10.so.0
#41 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#42 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#43 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#44 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#45 main
#0 __kernel_vsyscall

Comment 1 Jonathan Matthew 2006-12-09 22:26:30 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 André Klapper 2006-12-22 20:49:44 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 361681 ***