Bugzilla – Bug 114926
banshee not starting at all
Last modified: 2005-09-05 20:38:06 UTC
banshee Unhandled Exception: DBus.DBusException: Unable to determine the address of the message bus in [0x0003e] (at /usr/src/packages/BUILD/dbus-0.35.2/mono/Bus.cs:46) DBus.Bus:GetBus (BusType busType) in [0x00001] (at /usr/src/packages/BUILD/dbus-0.35.2/mono/Bus.cs:23) DBus.Bus:GetSessionBus () in <0x0001b> Banshee.DBusServer:.ctor () in <0x00045> Banshee.Core:.ctor () in <0x0002f> Banshee.Core:get_Instance () in <0x001db> Banshee.BansheeEntry:Main (System.String[] args) should have all necessary dbus packages installed: # rpm -qa | grep dbus dbus-1-mono-0.35.2-4 dbus-1-qt-32bit-0.35.2-4 dbus-1-0.35.2-4 dbus-1-glib-0.35.2-4 dbus-1-qt-0.35.2-4 dbus-1-32bit-0.35.2-4 dbus-1-glib-32bit-0.35.2-5 dbus is running as well: # ps ax | grep dbus 13983 ? Ss 0:00 /usr/bin/dbus-daemon --system 16840 pts/5 S+ 0:00 grep dbus
happens regardless if banshee is the i386 or x86_64 build
running LD_DEBUG=symbols LD_DEBUG_OUTPUT=b.out banshee I notice: 2115: symbol=g_module_check_init; lookup in file=/usr/lib/libdbus-1.so.1 2115: symbol=g_module_check_init; lookup in file=/lib/libnsl.so.1 2115: symbol=g_module_check_init; lookup in file=/lib/tls/libc.so.6 2115: symbol=g_module_check_init; lookup in file=/lib/ld-linux.so.2 2115: /usr/lib/libdbus-1.so.1: error: symbol lookup error: undefined symbol: g_module_check_init (fatal) 2115: symbol=g_module_unload; lookup in file=/usr/lib/libdbus-1.so.1 2115: symbol=g_module_unload; lookup in file=/lib/libnsl.so.1 2115: symbol=g_module_unload; lookup in file=/lib/tls/libc.so.6 2115: symbol=g_module_unload; lookup in file=/lib/ld-linux.so.2 2115: /usr/lib/libdbus-1.so.1: error: symbol lookup error: undefined symbol: g_module_unload (fatal)
Btw. my error message on i386 is: banshee Unhandled Exception: System.ApplicationException: Sqlite error in [0x0017d] (at /usr/src/packages/BUILD/mono-1.1.8.3/mcs/class/Mono.Data.SqliteClient/Mono.Data.SqliteClient/SqliteCommand.cs:256) Mono.Data.SqliteClient.SqliteCommand:ExecuteReader (CommandBehavior behavior, Boolean want_results, System.Int32 rows_affected) in [0x00005] (at /usr/src/packages/BUILD/mono-1.1.8.3/mcs/class/Mono.Data.SqliteClient/Mono.Data.SqliteClient/SqliteCommand.cs:211) Mono.Data.SqliteClient.SqliteCommand:ExecuteReader (CommandBehavior behavior) in [0x00002] (at /usr/src/packages/BUILD/mono-1.1.8.3/mcs/class/Mono.Data.SqliteClient/Mono.Data.SqliteClient/SqliteCommand.cs:205) Mono.Data.SqliteClient.SqliteCommand:ExecuteReader () in [0x00001] (at /usr/src/packages/BUILD/mono-1.1.8.3/mcs/class/Mono.Data.SqliteClient/Mono.Data.SqliteClient/SqliteCommand.cs:184) Mono.Data.SqliteClient.SqliteCommand:ExecuteScalar () in <0x0005f> Banshee.Database:QuerySingle (System.Object query) in <0x0002c> Banshee.Database:TableExists (System.String table) in <0x001c2> Banshee.Database:ExecuteSqlStatements (System.Collections.ArrayList statements) in <0x00032> Banshee.Database:InitializeTables () in <0x00062> Banshee.Database:.ctor (System.String dbname, System.String dbpath) in <0x0005b> Banshee.Library:ReloadDatabase () in <0x0004b> Banshee.Library:.ctor () in <0x000a4> Banshee.Core:.ctor () in <0x0001f> Banshee.Core:get_Instance () in <0x00155> Banshee.BansheeEntry:Main (System.String[] args)
I noticed that banshee links against both sqlite and sqlite2: x40:~ # rpm -q --requires banshee |grep sqlite sqlite mono-data-sqlite x40:~ # rpm -q --requires mono-data-sqlite |grep sqlite sqlite2
I really doubt that banshee using two sqlite libraries will work correctly.
Is this a clean install aj? if not, you may want to remove ~/.config/sonance and ~/.config/banshee.
I removed those already. No difference. The banshee from beta3 works using the helix engine, the one from beta4 fails.
I have the exactly same problem with banshee... on a beta3 upgraded to beta4. I used to work ok with gstreamer in beta3, but now in beta4 gives the same error Andreas reported. Daniel
I've submitted an updated banshee, its working for me, (I never saw the above errors though).
I just tested your banshee and it works for me on i386.
ok, the dbus error messages turned out to be a missing part in my private .xinitrc/.xsession. The global one start dbus-launch