Vmplayer + dbus -hal

arubin · 01-07-2008, 04:57 PM

Has anyone come across this problem (not specific to Slackware)? Vmplayer will not run with dbus enabled and hal disabled. To run vmplayer you must either disable dbus or enable hal.

So for the present I have re-enabled hal. I was wondering if it might not be preferable to disable dbus.

evilDagmar · 01-09-2008, 02:11 AM

Umm... considering that dbus and HAL work hand-in-hand with each other, this shouldn't come as any suprise to you. Dbus wasn't meant just to let user-land processes talk to each other (because that is more easily solved with other mechanisms), it was meant specifically to be a reasonable interface for userland things to talk to kernel-space things. Run them both, or run neither of them because only one of them is far less than half as useful as both of them.

arubin · 01-09-2008, 03:20 AM

I am finding this whole dbus/hal business very difficult to get my head round and I am unable to find good documentation. I like Slackware because I feel that I am in control but with dbus/hal I feel that I am losing control.

Toods · 01-09-2008, 08:33 AM

Quote:

Originally Posted by arubin

I am finding this whole dbus/hal business very difficult to get my head round and I am unable to find good documentation. I like Slackware because I feel that I am in control but with dbus/hal I feel that I am losing control.

It's easy to de-activate HAL if you wish:

Quote:

chmod -x /etc/rc.d/rc.hald and uncomment the /dev/cdrom line in /etc/fstab

arubin · 01-09-2008, 09:28 AM

Indeed it is. But if I do then I cannot run vmplayer without de-activating dbus. So we are back to my original question - should I be de-activating dbus? If it simply gets me back to a Slackware 11 type configuration that might be something to consider.