Getting error when starting mopidy daemon in arch linux


#1

sudo systemctl status mopidy
● mopidy.service - Mopidy music server
Loaded: loaded (/usr/lib/systemd/system/mopidy.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2018-05-07 13:52:32 CEST; 1min 42s ago
Process: 1291 ExecStart=/usr/bin/mopidy --config /usr/share/mopidy/conf.d:/etc/mopidy/mopidy.conf (code=exited, status=1/FAILURE)
Main PID: 1291 (code=exited, status=1/FAILURE)

Mai 07 13:52:32 whitepearl mopidy[1291]: import pykka.debug
Mai 07 13:52:32 whitepearl mopidy[1291]: File “/usr/lib/python2.7/site-packages/pykka/init.py”, line 2, in
Mai 07 13:52:32 whitepearl mopidy[1291]: from pykka.actor import Actor, ActorRef, ThreadingActor
Mai 07 13:52:32 whitepearl mopidy[1291]: File “/usr/lib/python2.7/site-packages/pykka/actor.py”, line 3, in
Mai 07 13:52:32 whitepearl mopidy[1291]: import threading as _threading
Mai 07 13:52:32 whitepearl mopidy[1291]: File “/usr/lib/python2.7/site-packages/pykka/threading.py”, line 7, in
Mai 07 13:52:32 whitepearl mopidy[1291]: from pykka.actor import Actor
Mai 07 13:52:32 whitepearl mopidy[1291]: ImportError: cannot import name Actor
Mai 07 13:52:32 whitepearl systemd[1]: mopidy.service: Main process exited, code=exited, status=1/FAILURE
Mai 07 13:52:32 whitepearl systemd[1]: mopidy.service: Failed with result ‘exit-code’.

mopidy.conf only default
[core]
cache_dir = /var/cache/mopidy
config_dir = /etc/mopidy
data_dir = /var/lib/mopidy

[logging]
config_file = /etc/mopidy/logging.conf
debug_file = /var/log/mopidy/mopidy-debug.log

[local]
data_dir = /var/lib/mopidy/local
media_dir = /var/lib/mopidy/media

[m3u]
playlists_dir = /var/lib/mopidy/playlists


#2

I have the same problem. Mopidy won‘t start on ArchLinux and Antergos. The error is the same, however, the error information quote from jasondaigo is not complete.

More details:
mopidy --deps
Traceback (most recent call last):
File “/usr/bin/mopidy”, line 11, in
load_entry_point(‘Mopidy==2.1.0’, ‘console_scripts’, ‘mopidy’)()
File “/usr/lib/python2.7/site-packages/pkg_resources/init.py”, line 476, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File “/usr/lib/python2.7/site-packages/pkg_resources/init.py”, line 2700, in load_entry_point
return ep.load()
File “/usr/lib/python2.7/site-packages/pkg_resources/init.py”, line 2318, in load
return self.resolve()
File “/usr/lib/python2.7/site-packages/pkg_resources/init.py”, line 2324, in resolve
module = import(self.module_name, fromlist=[‘name’], level=0)
File “/usr/lib/python2.7/site-packages/mopidy/main.py”, line 18, in
import pykka.debug
File “/usr/lib/python2.7/site-packages/pykka/init.py”, line 2, in
from pykka.actor import Actor, ActorRef, ThreadingActor
File “/usr/lib/python2.7/site-packages/pykka/actor.py”, line 3, in
import threading as _threading
File “/usr/lib/python2.7/site-packages/pykka/threading.py”, line 7, in
from pykka.actor import Actor
ImportError: cannot import name Actor

Installed versions of mopidy dependencies:
python2: 2.7.15-1
python2-pykka: 1.2.0-2
python2-setuptools: 1:39.2.0-2
python2-requests: 2.18.4-3
gstreamer: 1.14.1-1
gst-python2: 1.14.1-1
gst-plugins-good: 1.14.1-1
gst-plugins-ugly: 1.14.1-1
python2-tornado: 4.5.3-1
gst-plugins-base: 1.14.1-1


#3

I tried a few things today and got mopidy to work again. I’m not totally sure what exactly did the trick, but I think it was:

  • Remove the package python2-pykka (sudo pacman -Rdd python2-pykka)
  • Check if the folder /usr/lib/python2.7/site-packages/pykka is gone; if not, delete it
  • Reinstall the package python2-pykka (sudo pacman -S python2-pykka)

#4

Yes! That did the trick, thank you!

I’m guessing something got messed up when installing/upgrading packages using pip(2) and pacman simultaneously, but I couldn’t figure out why completely re-installing the packages didn’t fix the problem. It seems the problematic files in pykka remained even after uninstalling the python2-pykka package.