Bugzilla – Bug 134560
banshee - sudden death ...
Last modified: 2006-01-25 00:39:10 UTC
Banshee - for no apparent reason just stopped working for me: 0: Active Player Engine is now 'Helix' 1: Loaded PlayerEngine core: Helix 2: Loaded AudioCdPlayerEngine core: GStreamer Unhandled Exception: System.ApplicationException: Could not initialize HAL for CD Detection in [0x000c0] Banshee.AudioCdCore:.ctor () in [0x0015f] (at /usr/src/packages/BUILD/banshee-0.9.7/src/Core.cs:172) Banshee.Core:.ctor () in [0x0000b] (at /usr/src/packages/BUILD/banshee-0.9.7/src/Core.cs:73) Banshee.Core:get_Instance () in [0x000ef] (at /usr/src/packages/BUILD/banshee-0.9.7/src/Main.cs:78) Banshee.BansheeEntry:Main (System.String[] args) I have absolutely no clue why. Apparently haldaemon & the system dbus are both there & working; I logged out & logged in to check. michael@linux:/nld/home/michael> ps ax | grep dbus 6644 ? S 0:00 /sbin/dhclient -1 -lf /var/lib/dhcp/dhclient-eth1.leases -pf /var/run/dhclient-eth1.pid -e dhc_dbus=31 -x -d eth1 8223 ? S 0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/X11R6/bin/gnome 8224 ? Ss 0:00 dbus-daemon --fork --print-pid 8 --print-address 6 --session 8241 ? Ss 0:00 dbus-daemon --fork --print-pid 8 --print-address 6 --session 8242 ? S 0:00 /usr/bin/dbus-launch --exit-with-session /opt/gnome/bin/gnome-session 8710 pts/0 R+ 0:00 grep dbus I have a CD drive etc. Unfortunately there appears to be no way to disable (at the commandline) this integration; anyhow, somewhat irritating not to be able to play anything.
Have you been updated from plus at all? I had this problem with plus at one point. Latest plus with 0.9.11 seems to work fine.
nope - this is a fairly stock SL 10.0 - it seems (since also suspend/resume didn't work) that HALD / DBUS just got totally hosed for no apparent reason (both daemons were still running), and they refused to work on a re-start too so ... No idea what's up ...
If Banshee could not talk to HAL... well, that's a HAL problem :) However, I have beefed up failure handling for HAL and other components (Session-level D-Bus for remote control), to simply disable the feature instead of exiting on failure. With that fix in mind, and HAL being the actual problem, I'm going to go ahead and close this.