Bug 411468 – crash in Rhythmbox Music Player: reproducir temas mp3

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 411468 - crash in Rhythmbox Music Player: reproducir temas mp3


Summary:	crash in Rhythmbox Music Player: reproducir temas mp3


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-02-24 04:29 UTC by gerardocordoba2211
Modified:	2007-02-24 11:53 UTC

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

Description gerardocordoba2211 2007-02-24 04:29:02 UTC

What were you doing when the application crashed?
reproducir temas mp3


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

Memory status: size: 183488512 vsize: 0 resident: 183488512 share: 0 rss: 24236032 rss_rlim: 0
CPU usage: start_time: 1172291247 rtime: 0 utime: 243 stime: 0 cutime:225 cstime: 0 timeout: 18 it_real_value: 0 frequency: 6

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 -1228298048 (LWP 4793)]
[New Thread -1382872160 (LWP 4848)]
[New Thread -1315533920 (LWP 4847)]
[New Thread -1374479456 (LWP 4844)]
[New Thread -1366086752 (LWP 4841)]
[New Thread -1349301344 (LWP 4838)]
[New Thread -1332319328 (LWP 4833)]
[New Thread -1323926624 (LWP 4832)]
[New Thread -1290355808 (LWP 4825)]
[New Thread -1281963104 (LWP 4824)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 113423

Thread 1 (Thread -1228298048 (LWP 4793))

#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 ??
#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 James "Doc" Livingston 2007-02-24 11:53:02 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 ***