Bug 1271784 - calibre doesn't run
Summary: calibre doesn't run
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: calibre
Version: 22
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-14 17:46 UTC by Stefan Seefeld
Modified: 2016-07-19 18:55 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 18:55:48 UTC
Type: Bug


Attachments (Terms of Use)

Description Stefan Seefeld 2015-10-14 17:46:22 UTC
An attempt to start calibre yields the error:



Traceback (most recent call last):
  File "/usr/bin/calibre", line 20, in <module>
    sys.exit(calibre())
  File "/usr/lib64/calibre/calibre/gui_launch.py", line 59, in calibre
    init_dbus()
  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

Comment 1 Kevin Fenzi 2015-10-14 19:48:07 UTC
Can you provide the output of: 

rpm -qa | grep dbus | sort

Comment 2 Stefan Seefeld 2015-10-14 21:11:58 UTC
Sure:

abrt-dbus-2.6.1-5.fc22.x86_64
dbus-1.8.20-1.fc22.x86_64
dbus-glib-0.104-1.fc22.x86_64
dbus-libs-1.8.20-1.fc22.x86_64
dbusmenu-qt-0.9.3-0.10.20150604.fc22.x86_64
dbusmenu-qt5-0.9.3-0.10.20150604.fc22.x86_64
dbus-python-1.2.0-7.fc22.x86_64
dbus-sharp-0.7.0-12.fc22.x86_64
dbus-sharp-glib-0.5.0-10.fc22.x86_64
dbus-x11-1.8.20-1.fc22.x86_64
dleyna-connector-dbus-0.2.0-4.fc22.x86_64
kf5-kdbusaddons-5.14.0-1.fc22.x86_64
ndesk-dbus-0.6.1a-16.fc21.x86_64
ndesk-dbus-glib-0.4.1-17.fc21.x86_64
python3-dbus-1.2.0-7.fc22.x86_64
python-slip-dbus-0.6.4-1.fc22.noarch

Comment 3 Kevin Fenzi 2015-10-14 22:42:07 UTC
This should be provided by dbus-glib I think. 

Can you do: 

rpm -V dbus-glib

and 

ldd /usr/bin/dbus-binding-tool

and provide the output here?

Comment 4 Stefan Seefeld 2015-10-14 22:43:38 UTC
        linux-vdso.so.1 (0x00007ffd52df4000)
        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)
        /lib64/ld-linux-x86-64.so.2 (0x000055c970b3e000)
        libpcre.so.1 => /lib64/libpcre.so.1 (0x00007ffb28e24000)

Comment 5 Stefan Seefeld 2015-10-14 22:55:33 UTC
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.

Comment 6 Kevin Fenzi 2015-10-14 23:30:35 UTC
Ah, that would do it. 

Yeah, I could look at pointing it to /usr/bin/python2 there.

Glad you got it tracked down.

Comment 7 Fedora End Of Life 2016-07-19 18:55:48 UTC
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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.