Bug 462292 – crash in Rhythmbox Music Player: listening to a shoutcast...

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 462292 - crash in Rhythmbox Music Player: listening to a shoutcast...


Summary:	crash in Rhythmbox Music Player: listening to a shoutcast...


Status:	RESOLVED DUPLICATE of bug 452703

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.10.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-31 21:11 UTC by zielinski.andrew
Modified:	2007-08-02 10:53 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description zielinski.andrew 2007-07-31 21:11:14 UTC

Version: 0.10.1

What were you doing when the application crashed?
listening to a shoutcast stream


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist

Memory status: size: 143507456 vsize: 143507456 resident: 41562112 share: 20189184 rss: 41562112 rss_rlim: 4294967295
CPU usage: start_time: 1185904079 rtime: 40548 utime: 36197 stime: 4351 cutime:4 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1229142336 (LWP 10518)]
[New Thread -1339270256 (LWP 18632)]
[New Thread -1330877552 (LWP 18627)]
[New Thread -1296282736 (LWP 12027)]
[New Thread -1232405616 (LWP 10540)]
[New Thread -1259340912 (LWP 10539)]
[New Thread -1285985392 (LWP 10538)]
[New Thread -1284744304 (LWP 10533)]
[New Thread -1267958896 (LWP 10529)]
(no debugging symbols found)
0xb7f247f2 in ?? () from /lib/ld-linux.so.2

+ Trace 151936

Thread 1 (Thread -1229142336 (LWP 10518))

#0 ??
from /lib/ld-linux.so.2
#1 __waitpid_nocancel
from /lib/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
from /lib/ld-linux.so.2
#5 raise
from /lib/i686/cmov/libc.so.6
#6 abort
from /lib/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 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 rhythmdb_property_model_new
#11 rhythmdb_property_model_new
#12 rb_marshal_VOID__BOXED_INT_POINTER_POINTER
from /usr/lib/librhythmbox-core.so.0
#13 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_override_class_closure
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#17 rhythmdb_query_model_new
#18 rb_marshal_VOID__BOXED_POINTER
from /usr/lib/librhythmbox-core.so.0
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_override_class_closure
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 rhythmdb_emit_entry_deleted
#24 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#25 rhythmdb_load
#26 rhythmdb_shutdown
#27 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#28 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#29 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#30 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#31 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#32 main
#0 ??
from /lib/ld-linux.so.2



----------- .xsession-errors ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-08-02 10:53:59 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 452703 ***