Bug 373944 – crash in Rhythmbox Music Player: Restarting a few service...

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 373944 - crash in Rhythmbox Music Player: Restarting a few service...


Summary:	crash in Rhythmbox Music Player: Restarting a few service...


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-11-11 17:45 UTC by Alexander “weej” Jones
Modified:	2006-11-11 22:53 UTC

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

Description Alexander “weej” Jones 2006-11-11 17:45:48 UTC

What were you doing when the application crashed?
Restarting a few services


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

Memory status: size: 137818112 vsize: 0 resident: 137818112 share: 0 rss: 33685504 rss_rlim: 0
CPU usage: start_time: 1163255134 rtime: 0 utime: 52340 stime: 0 cutime:51188 cstime: 0 timeout: 1152 it_real_value: 0 frequency: 4

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 -1228634448 (LWP 6535)]
[New Thread -1253409888 (LWP 10745)]
[New Thread -1309910112 (LWP 10743)]
[New Thread -1331471456 (LWP 10742)]
[New Thread -1323078752 (LWP 10741)]
[New Thread -1270588512 (LWP 6550)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 85489

Thread 1 (Thread -1228634448 (LWP 6535))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 874
#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 IA__g_logv
#8 IA__g_log
#9 IA__g_assert_warning
#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 IA__g_closure_invoke
at gclosure.c line 490
#13 signal_emit_unlocked_R
at gsignal.c line 2440
#14 IA__g_signal_emit_valist
at gsignal.c line 2199
#15 IA__g_signal_emit
at gsignal.c line 2243
#16 rhythmdb_query_model_entry_changed_cb
at rhythmdb-query-model.c line 899
#17 rb_marshal_VOID__BOXED_POINTER
at rb-marshal.c line 408
#18 IA__g_closure_invoke
at gclosure.c line 490
#19 signal_emit_unlocked_R
at gsignal.c line 2440
#20 IA__g_signal_emit_valist
at gsignal.c line 2199
#21 IA__g_signal_emit
at gsignal.c line 2243
#22 emit_entry_changed
at rhythmdb.c line 791
#23 IA__g_hash_table_foreach
at ghash.c line 662
#24 rhythmdb_commit_internal
at rhythmdb.c line 915
#25 rhythmdb_volume_mounted_cb
at rhythmdb-monitor.c line 398
#26 IA__g_cclosure_marshal_VOID__OBJECT
at gmarshal.c line 636
#27 IA__g_closure_invoke
at gclosure.c line 490
#28 signal_emit_unlocked_R
at gsignal.c line 2440
#29 IA__g_signal_emit_valist
at gsignal.c line 2199
#30 IA__g_signal_emit
at gsignal.c line 2243
#31 _gnome_vfs_volume_monitor_mounted
at gnome-vfs-volume-monitor.c line 769
#32 read_volumes_from_daemon
at gnome-vfs-volume-monitor-client.c line 234
#33 dbus_try_activate_daemon_helper
at gnome-vfs-dbus-utils.c line 69
#34 dbus_filter_func
at gnome-vfs-dbus-utils.c line 98
#35 dbus_connection_dispatch
from /usr/lib/libdbus-1.so.3
#36 dbus_server_setup_with_g_main
from /usr/lib/libdbus-glib-1.so.2
#37 IA__g_main_context_dispatch
at gmain.c line 2045
#38 g_main_context_iterate
at gmain.c line 2677
#39 IA__g_main_loop_run
at gmain.c line 2881
#40 IA__gtk_main
at gtkmain.c line 1024
#41 main
at main.c line 381
#0 __kernel_vsyscall

Comment 1 Jonathan Matthew 2006-11-11 22:53:19 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 359083 ***