Last October murmur systemd unit file was replaced by a more sophisticated one (Type=dbus). Unfortunately it does not work on arm. Apparently murmur crashes if started this way. <W>2014-06-05 23:29:22.134 Initializing settings from /etc/murmur/murmur.ini (basepath /etc/murmur) <W>2014-06-05 23:29:22.136 OpenSSL: OpenSSL 1.0.1g 7 Apr 2014 <W>2014-06-05 23:29:22.507 ServerDB: Opened SQLite database /var/lib/murmur/murmur.sqlite <W>2014-06-05 23:29:22.547 DBus registration succeeded <W>2014-06-05 23:29:22.554 MurmurIce: Endpoint "tcp -h 127.0.0.1 -p 6502" running <W>2014-06-05 23:29:22.725 Murmur 1.2.6 (1.2.6) running on X11: Gentoo Base System release 2.2: Booting servers <W>2014-06-05 23:29:22.774 1 => Server listening on [::]:64738 <W>2014-06-05 23:29:22.827 1 => Announcing server via bonjour <W>2014-06-05 23:29:22.876 1 => Not registering server as public <W>2014-06-05 23:29:22.876 Object::connect: No such slot MurmurDBus::userTextMessage(const User *, const TextMessage &) <C>2014-06-05 23:29:22.877 Caught SIGTERM, exiting <W>2014-06-05 23:29:22.877 Killing running servers This was the only issue I found on arm. If it is started manually or using the old simpler unit file then murmur works fine. So if this issue is fixed then I guess murmur can be keyworded on arm. [ebuild R *] media-sound/murmur-1.2.6 USE="dbus ice zeroconf -debug -pch" 0 kB
It appears that once version 1.3 hits, murmur will provide an upstream systemd unit file: https://github.com/mumble-voip/mumble/blob/master/scripts/murmur.service
The systemd unit where this behavior was seen has long been replaced and no longer uses Type=dbus. If this is still an issue please file a new bug.
