Bug 459487 – crash in Rhythmbox Music Player: Restarted DBUS - after s...

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 459487 - crash in Rhythmbox Music Player: Restarted DBUS - after s...


Summary:	crash in Rhythmbox Music Player: Restarted DBUS - after s...


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-23 10:43 UTC by egilam
Modified:	2007-07-25 10:53 UTC

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

Description egilam 2007-07-23 10:43:41 UTC

Version: 0.10.1

What were you doing when the application crashed?
Restarted DBUS - after suspend to disk, the wireless connection is not recovered so DBUS must be restarted. Rhythmbox has usually just quit when restarting DBUS, not crashed before.


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: Amaranth

Memory status: size: 99225600 vsize: 99225600 resident: 32985088 share: 18288640 rss: 32985088 rss_rlim: 4294967295
CPU usage: start_time: 1185187039 rtime: 191 utime: 176 stime: 15 cutime:3 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 -1229343040 (LWP 9768)]
[New Thread -1311245424 (LWP 9820)]
[New Thread -1235870832 (LWP 9818)]
[New Thread -1268786288 (LWP 9777)]
(no debugging symbols found)
0xb7efa7f2 in ?? () from /lib/ld-linux.so.2

+ Trace 149927

Thread 1 (Thread -1229343040 (LWP 9768))

#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 rb_marshal_VOID__BOXED_INT_POINTER_POINTER
from /usr/lib/librhythmbox-core.so.0
#12 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_override_class_closure
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_new
#17 rb_marshal_VOID__BOXED_POINTER
from /usr/lib/librhythmbox-core.so.0
#18 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_override_class_closure
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 rhythmdb_emit_entry_deleted
#23 g_hash_table_foreach
from /usr/lib/libglib-2.0.so.0
#24 rhythmdb_load
#25 rhythmdb_init_monitoring
#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_override_class_closure
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_shutdown_private
from /usr/lib/libgnomevfs-2.so.0
#33 gnome_vfs_daemon_set_current_connection
from /usr/lib/libgnomevfs-2.so.0
#34 gnome_vfs_daemon_set_current_connection
from /usr/lib/libgnomevfs-2.so.0
#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 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#38 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#39 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#40 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#41 main
#0 ??
from /lib/ld-linux.so.2



----------- .xsession-errors (5079 sec old) ---------------------
WARNING: DCOPReply<>: cast to 'QString' error
WARNING: DCOPReply<>: cast to 'QString' error
WARNING: DCOPReply<>: cast to 'QString' error
WARNING: DCOPReply<>: cast to 'QString' error
kbuildsycoca running...
Reusing existing ksycoca
kio (KService*): WARNING: Invalid Service : media_realfolder.desktop
kbuildsycoca: WARNING: '/usr/share/applications/kde/ark.desktop' specifies undefined mimetype/servicetype 'application/x-tbz2'
kbuildsycoca: WARNING: 'katepart.desktop' specifies undefined mimetype/servicetype 'text/x-fortran'
kbuildsycoca: WARNING: '/usr/share/applications/gnome-theme-installer.desktop' specifies undefined mimetype/servicetype 'application/x-gnome-theme-package'
kbuildsycoca: WARNING: '/usr/share/applications/nautilus-folder-handler.desktop' specifies undefined mimetype/servicetype 'x-directory/gnome-default-handler'
kbuildsycoca: WARNING: '/usr/share/applications/nautilus-folder-handler.desktop' specifies undefined mimetype/servicetype 'x-directory/normal'
kbuildsycoca: WARNING: '/usr/share/applications/nautilus-folder-handler.desktop' specifies undefined mimetype/servicetype 'application/x-gnome-saved-search'
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Jonathan Matthew 2007-07-25 10:53:49 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 ***