Bug 359491 – crash in Rhythmbox Music Player: Nothing, actually. Maybe...

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 359491 - crash in Rhythmbox Music Player: Nothing, actually. Maybe...


Summary:	crash in Rhythmbox Music Player: Nothing, actually. Maybe...


Status:	RESOLVED DUPLICATE of bug 359083

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-10-04 04:11 UTC by Everett Guerny
Modified:	2006-10-07 03:01 UTC

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

Description Everett Guerny 2006-10-04 04:11:45 UTC

What were you doing when the application crashed?
Nothing, actually. Maybe my external HDD went idle, which contained all of my tracks.


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

Memory status: size: 154722304 vsize: 0 resident: 154722304 share: 0 rss: 40652800 rss_rlim: 0
CPU usage: start_time: 1159934393 rtime: 0 utime: 3222 stime: 0 cutime:2925 cstime: 0 timeout: 297 it_real_value: 0 frequency: 10

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1228822864 (LWP 11327)]
[New Thread -1341146208 (LWP 11796)]
[New Thread -1332753504 (LWP 11795)]
[New Thread -1324360800 (LWP 11794)]
[New Thread -1315968096 (LWP 11793)]
[New Thread -1307575392 (LWP 11792)]
[New Thread -1263535200 (LWP 11791)]
[New Thread -1271927904 (LWP 11790)]
[New Thread -1297106016 (LWP 11789)]
[New Thread -1280320608 (LWP 11788)]
[New Thread -1239643232 (LWP 11785)]
[New Thread -1288713312 (LWP 11371)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 74423

Thread 1 (Thread -1228822864 (LWP 11327))

#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 *__GI_raise
from /lib/tls/i686/cmov/libc.so.6
#6 *__GI_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 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 rhythmdb_property_model_prop_changed_cb
at rhythmdb-property-model.c line 506
#11 rb_marshal_VOID__BOXED_INT_POINTER_POINTER
at rb-marshal.c line 363
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#15 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#16 rhythmdb_query_model_entry_changed_cb
at rhythmdb-query-model.c line 874
#17 rb_marshal_VOID__BOXED_POINTER
at rb-marshal.c line 408
#18 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#22 emit_entry_changed
at rhythmdb.c line 791
#23 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#24 rhythmdb_commit_internal
at rhythmdb.c line 915
#25 rhythmdb_volume_mounted_cb
at rhythmdb-monitor.c line 398
#26 g_cclosure_marshal_VOID__OBJECT
from /usr/lib/libgobject-2.0.so.0
#27 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#31 gnome_vfs_volume_monitor_emit_pre_unmount
from /usr/lib/libgnomevfs-2.so.0
#32 gnome_vfs_volume_monitor_client_get_type
from /usr/lib/libgnomevfs-2.so.0
#33 dbus_connection_dispatch
from /usr/lib/libdbus-1.so.3
#34 dbus_server_setup_with_g_main
from /usr/lib/libdbus-glib-1.so.2
#35 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#36 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#37 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#38 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#39 main
at main.c line 372
#0 __kernel_vsyscall

Comment 1 Jonathan Matthew 2006-10-04 11:00:58 UTC

This is likely related to bug 359083.

Comment 2 Jonathan Matthew 2006-10-07 03:01:26 UTC

This was a consequence of bug 359083.

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