I recall seeing the same traceback right after the big qt5 update and privately emailing the calibre maintainer about it. The problem was with python2-sip. What fixed calibre for me was to rebuild python2-sip after a fix was pushed (I believe it was this one https://git.slackbuilds.org/slackbuilds/commit/python/python2-sip?h=14.2&id=fa749a3a4df86ad32c6314cd03fc3793e830d787), then rebuild PyQt5, and then rebuild calibre.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Sunday, December 2, 2018 9:40 PM, Petar Petrov <slackal...@gmail.com> wrote: > hi all, > > calibre does not start. It shows this in the terminal: > > Failed to run pipe worker with command: from calibre.utils.ipc.pool > import run_main, worker_main; run_main(worker_main) > Traceback (most recent call last): > File "/usr/bin/calibre-parallel", line 20, in <module> > > sys.exit(main()) > > > File "/usr/lib64/calibre/calibre/utils/ipc/worker.py", line 180, in main > exec (sys.argv[-1]) > File "<string>", line 1, in <module> > File "/usr/lib64/calibre/calibre/utils/ipc/pool.py", line 392, in run_main > with closing(Client(address, authkey=key)) as conn: > File "/usr/lib64/python2.7/multiprocessing/connection.py", line 169, in Client > c = SocketClient(address) > File "/usr/lib64/python2.7/multiprocessing/connection.py", line 308, > in SocketClient > s.connect(address) > File "/usr/lib64/python2.7/socket.py", line 228, in meth > return getattr(self._sock,name)(*args) > socket.error: [Errno 111] Connection refused > > regards, > > Petar _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/