Em Dom, 2006-04-16 às 13:37 +0200, Christophe Dehais escreveu: > Here are my compilation options: > > --enable-daap --enable-tag-writing --enable-track-transfer > --enable-python --enable-libnotify --enable-musicbrainz > --with-mdns=avahi --with-rhythmdb-debug=2 --disable-lirc --with-dbus > > gtk+ is version 2.8.16 > gstreamer is version 0.10.4 > dbus is version 0.61 > > I run on debian testing where rhythmbox 0.9.3 is ok except a crash > when trying to launch 2 instances of rhythmbox. > I tested on 2 different systems with debian testing, same crash for > both. > > I have those messages before rhythmbox segfaults: > > ---------- > > (rhythmbox:19241): Rhythmbox-WARNING **: couldn't connect to session > bus: Unable to determine the address of the message bus > > (rhythmbox:19241): Rhythmbox-WARNING **: Unable to load icon > rhythmbox-tray-icon > > (rhythmbox:19241): Rhythmbox-WARNING **: Unable to load icon > rhythmbox-set-star > > (rhythmbox:19241): Rhythmbox-WARNING **: Unable to load icon > rhythmbox-unset-star > > (rhythmbox:19241): Rhythmbox-WARNING **: Unable to load icon > rhythmbox-podcast > > (rhythmbox:19241): Rhythmbox-WARNING **: Unable to load icon > rhythmbox-no-star > > (rhythmbox:19241): Rhythmbox-WARNING **: Unable to load icon > media-eject > > (rhythmbox:19241): GLib-CRITICAL **: g_file_get_contents: assertion > `filename != NULL' failed > > (rhythmbox:19241): Gtk-CRITICAL **: gtk_box_pack_start: assertion > `GTK_IS_WIDGET (child)' failed > > (rhythmbox:19241): Gtk-CRITICAL **: gtk_box_reorder_child: assertion > `GTK_IS_WIDGET (child)' failed > > (rhythmbox:19241): Gtk-CRITICAL **: gtk_box_pack_start: assertion > `GTK_IS_WIDGET (child)' failed > > (rhythmbox:19241): Gtk-CRITICAL **: gtk_toolbar_insert: assertion > `GTK_IS_TOOLBAR (toolbar)' failed > > (rhythmbox:19241): Gtk-CRITICAL **: gtk_toolbar_insert: assertion > `GTK_IS_TOOLBAR (toolbar)' failed > > ------------------- > > > hum, btw compiling with default options leads to the same behaviour. > > Even if it doesn't seem critical nor closely related, the first > warning about dbus seems strange to me. Maybe I didn't set up dbus > correctly on my system(s). >
Try: $ dbus-launch rhythmbox Or simply build rhythmbox without dbus support. Hope that helps, Evandro _______________________________________________ rhythmbox-devel mailing list rhythmbox-devel@gnome.org http://mail.gnome.org/mailman/listinfo/rhythmbox-devel
