Bug 470062 – crash in Rhythmbox Music Player: i turned the volume to m...

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 470062 - crash in Rhythmbox Music Player: i turned the volume to m...


Summary:	crash in Rhythmbox Music Player: i turned the volume to m...


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:	2007-08-24 22:52 UTC by barbtidlytastic
Modified:	2007-08-27 12:25 UTC

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

Description barbtidlytastic 2007-08-24 22:52:05 UTC

What were you doing when the application crashed?
i turned the volume to mute. then i left the house, so I don't know when it crashed.


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

Memory status: size: 109211648 vsize: 0 resident: 109211648 share: 0 rss: 25108480 rss_rlim: 0
CPU usage: start_time: 1187978956 rtime: 0 utime: 54561 stime: 0 cutime:52881 cstime: 0 timeout: 1680 it_real_value: 0 frequency: 16

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 -1228216656 (LWP 6316)]
[New Thread -1335899232 (LWP 16257)]
[New Thread -1274823776 (LWP 6394)]
[New Thread -1263682656 (LWP 6370)]
[New Thread -1252283488 (LWP 6326)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 157717

Thread 1 (Thread -1228216656 (LWP 6316))

#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 palfrey 2007-08-27 12:25:23 UTC

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 361681 ***