New install on Precise Server AMD 64bit.
sudo apt-get install rygel.
Look at the paths! Looks like the dev (jens) has left some testing code in the package...
alord@precise:~$ rygel
MediaExport-CRITICAL **: file /home/jens/Source/rygel/src/plugins/media-export/rygel-media-export-dbus-service.vala: line 32: unexpected error: Error spawning command line `dbus-launch --autolaunch=c3b3d5675b366aa02d9349650000022d --binary-syntax --close-stderr': Failed to execute child process "dbus-launch" (No such file or directory) (g-exec-error-quark, 8)
Rygel-Message: New plugin 'MediaExport' available
External-CRITICAL **: file /home/jens/Source/rygel/src/plugins/external/rygel-external-plugin-factory.vala: line 51: uncaught error: Error spawning command line `dbus-launch --autolaunch=c3b3d5675b366aa02d9349650000022d --binary-syntax --close-stderr': Failed to execute child process "dbus-launch" (No such file or directory) (g-exec-error-quark, 8)
MPRIS-CRITICAL **: file /home/jens/Source/rygel/src/plugins/mpris/rygel-mpris-plugin-factory.vala: line 51: uncaught error: Error spawning command line `dbus-launch --autolaunch=c3b3d5675b366aa02d9349650000022d --binary-syntax --close-stderr': Failed to execute child process "dbus-launch" (No such file or directory) (g-exec-error-quark, 8)
No, I didn't. That is a by-product of vala's code generator.
While the messages look scary, you can completely ignore them. If it really is crashing, please add a core dump.
Rygel does nothing here because XDG directories are apparently not configured for users on ubuntu-server. You have to add paths manually by copying /etc/rygel.conf to $HOME/.config and modifying the "uris" key in the [MediaExport] section.