An attempt to start calibre yields the error:
Traceback (most recent call last):
File "/usr/bin/calibre", line 20, in <module>
File "/usr/lib64/calibre/calibre/gui_launch.py", line 59, in calibre
File "/usr/lib64/calibre/calibre/gui_launch.py", line 39, in init_dbus
from dbus.mainloop.glib import DBusGMainLoop, threads_init
ImportError: No module named dbus.mainloop.glib
Can you provide the output of:
rpm -qa | grep dbus | sort
This should be provided by dbus-glib I think.
Can you do:
rpm -V dbus-glib
and provide the output here?
libdbus-glib-1.so.2 => /lib64/libdbus-glib-1.so.2 (0x00007ffb2b057000)
libdbus-1.so.3 => /lib64/libdbus-1.so.3 (0x00007ffb2ae0e000)
libgio-2.0.so.0 => /lib64/libgio-2.0.so.0 (0x00007ffb2aa8f000)
libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x00007ffb2a83d000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007ffb2a503000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x00007ffb2a2d8000)
libc.so.6 => /lib64/libc.so.6 (0x00007ffb29f18000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007ffb29cfc000)
libffi.so.6 => /lib64/libffi.so.6 (0x00007ffb29af3000)
libgmodule-2.0.so.0 => /lib64/libgmodule-2.0.so.0 (0x00007ffb298ef000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007ffb296eb000)
libz.so.1 => /lib64/libz.so.1 (0x00007ffb294d4000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007ffb292b0000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007ffb29095000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007ffb28e24000)
OK, some investigation on my side reveals the cause of the issue:
/usr/bin/calibre invokes as interpreter `/usr/bin/env python` which resolves in my case to a non-system Python installation that doesn't have the 'dbus' package installed. I hacked the script to hardcode /usr/bin/python, and now it's working fine.
I'm not sure what the system policy is for this, but it seems for a system-provided Python-based executable it might be better to hardcode the interpreter precisely to not depend on the user-specific PATH variable.
Ah, that would do it.
Yeah, I could look at pointing it to /usr/bin/python2 there.
Glad you got it tracked down.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.