If you're using xfmedia, you may have already noticed that the recent dbus upgrade to 0.33 breaks it. xfmedia 0.8.0, available in the AUR here,uses dbus 0.23.
The good news is that the current development version works with dbus 0.33, so the next release should be all OK again. And if you really can't wait, checking it out and building it is very straightforward - see the website for details.
It does? I haven't experienced any problem...
$ pacman -Q | grep dbus
$ pacman -Q | grep xfmedia
$ ps aux | grep bus
1000 2975 0.0 0.2 2496 736 ? S 12:19 0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-se
1000 2976 0.0 0.3 2092 1068 ? Ss 12:19 0:00 dbus-daemon --fork --print-pid 8 --print-addres
1000 9094 0.0 0.1 3556 584 pts/0 R+ 17:22 0:00 grep bus
I am listening to music on xfmedia right now.
I am a gated community.
Interesting. Mine bombed, and I noted the following on the xfmedia site:
In order to enable remote control support, D-BUS version 0.23 or greater is required. The new API in the 0.3x series is supported in the current Subversion trunk.
I reckon I'll stick with the Subversion checkout anyway, now that I've gone to the bother if compiling it. I'll revert to an ABS build whenever the next release comes out.
Here's the error message I got, if anyone's interested:
$ xfmedia xfmedia: error while loading shared libraries: libdbus-glib-1.so.0: cannot open shared object file: No such file or directory
My system has libdbus-glib-1.so.1, which is a symlink to libdbus-glib-1.so.1.0.0.
You know, I thought I could let this go, but it seems I can't (the phrase "Get a life" springs to mind ). If you're still interested, Stonecrest, would you mind doing the following and posting the results?
(If you're xfmedia binary is in a different directory, adjust accordingly).