ebook-viewer broken?

[jgaiser]

Callibre 2.60

Don't use it a lot, but trying to use it this morning, first from the app and then command line:

DeDRM v6.1.0: In __init__
DeDRM v6.1.0: In load_resources
DeDRM v6.1.0: verdir /home/jerryg/.config/calibre/plugins/DeDRM/6.1.0
DeDRM v6.1.0: In initialize
Traceback (most recent call last):
File "site.py", line 66, in main
File "site-packages/calibre/gui_launch.py", line 69, in ebook_viewer
File "site-packages/calibre/gui2/viewer/main.py", line 27, in <module>
File "site-packages/calibre/utils/monotonic.py", line 7, in <module>
RuntimeError: Failed to load the monotonic module with error: /opt/calibre/lib/python2.7/site-packages/calibre/plugins/monotonic.so: undefined symbol: clock_gettime

Edit:
Tried a re-install - Install failures - Ideas??

Failed to find directory to install bash completions, using default.

____________________ WARNING ____________________
Setting up completion failed with error:
__________________________________________________


Traceback (most recent call last):
File "site-packages/calibre/linux.py", line 748, in setup_completion
File "site-packages/calibre/linux.py", line 506, in write_completion
File "site-packages/calibre/gui2/viewer/main.py", line 27, in <module>
File "site-packages/calibre/utils/monotonic.py", line 7, in <module>
RuntimeError: Failed to load the monotonic module with error: /opt/calibre/lib/python2.7/site-packages/calibre/plugins/monotonic.so: undefined symbol: clock_gettime

[kovidgoyal]

https://www.mobileread.com/forums/sho...d.php?t=275536

[jgaiser]

Thanks Kovid. Looks like it's time to update from Ubuntu 12.04

[DiapDealer]

Originally Posted by jgaiser

Thanks Kovid. Looks like it's time to update from Ubuntu 12.04

Looks like the next version of calibre will have the viewer working again (if I understood Kovid correctly) regardless of the glibc version. So you can hold off for a while longer if you like (not that I would discourage you from upgrading).

[pbarnrob]

My experience (under LUbuntu 14.04, LXDE on an old Dell) after installing calibre 2.60;
now the reader doesn't start!
Just as recommended,
-----
phil@BorgLU:~$ calibre
Traceback (most recent call last):
File "site-packages/calibre/gui2/viewer/documentview.py", line 1387, in resizeEvent
File "site-packages/calibre/gui2/viewer/main.py", line 767, in viewport_resize_started
AttributeError: 'DocumentView' object has no attribute 'last_loaded_path'
Traceback (most recent call last):
File "site-packages/calibre/gui2/viewer/documentview.py", line 1387, in resizeEvent
File "site-packages/calibre/gui2/viewer/main.py", line 767, in viewport_resize_started
AttributeError: 'DocumentView' object has no attribute 'last_loaded_path'
-----
Hope that's some help, Kovid! Love it otherwise!

[jgaiser]

Originally Posted by DiapDealer

Looks like the next version of calibre will have the viewer working again (if I understood Kovid correctly) regardless of the glibc version. So you can hold off for a while longer if you like (not that I would discourage you from upgrading).

Yeah I finally noticed. But... It's getting to be time to really start thinking about moving on. Don't need bleeding edge but heck, Ubuntu is up to 16.04 LTS. Maybe time to even consider a different distribution.

[kovidgoyal]

Originally Posted by DiapDealer

Looks like the next version of calibre will have the viewer working again (if I understood Kovid correctly) regardless of the glibc version. So you can hold off for a while longer if you like (not that I would discourage you from upgrading).

Indeed, the next version of calibre should work with glibc 2.15 (which is what Ubuntu 12.04 has). You can even see that it passes tests on that OS (the test include loading the problematic module) here: https://travis-ci.org/kovidgoyal/calibre

[pbarnrob]

When I go looking tor the things that aren't working, that whole area, instead of '.py' bytecode, is full of '.pyo' bytecodes.
Could this be something that's (helping) break the reader?

[eschwartz]

No. *.pyo optimized bytecode is the cached version of what the python interpreter would have translated the *.py source code into, during the process of running. When *.pyo files exist the *.py files are actually ignored entirely.
Distributing an application as *.pyo files is pretty standard for compiled binary applications. It speeds it up, saves space, and even provides rudimentary protection for closed-source binaries.

The calibre binary download has always distributed *.pyo files.