When I open any * .fb2 file with ebook-viewer program (from the calibre package), I get a program window with all controls, but in the page area there is only a big white "?" on blue background.
Maybe some library is missing?
Welcome!
Important information-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities
News
-- Introducing our new Website
-- MX Linux on social media: here
Current releases
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here
New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules
[SOLVED]ebook-viewer from calibre package doesn't work properly
Re: [SOLVED]ebook-viewer from calibre package doesn't work properly
The problem solved by installing calibre and calibre-bin packages from the debian-backports repository.
Re: [SOLVED]ebook-viewer from calibre package doesn't work properly
What version did you have installed that had the problems?
Re: [SOLVED]ebook-viewer from calibre package doesn't work properly
calibre-2.75.1+dfsg-1
upgrade to calibre-3.31.0+dfsg-1~bpo9+1 solved the problem.
upgrade to calibre-3.31.0+dfsg-1~bpo9+1 solved the problem.
Re: [SOLVED]ebook-viewer from calibre package doesn't work properly
Hmmm-we've had 3.31 in the main MX repo since Sept. 8, so I was worried that ours had some issue that the backports didn't. But I'm a bit puzzled as to why it it didn't show up as an upgrade for you...
BTW, it looks like 3.31 is the end of the line for ours and backports native Calibre builds, since 3.32 builds fails on a Stretch base with some kind of Python error. But maybe someone will come up with a workaround for that...otherwise it's going to be portable/static versions if you want the latest releases.
BTW, it looks like 3.31 is the end of the line for ours and backports native Calibre builds, since 3.32 builds fails on a Stretch base with some kind of Python error. But maybe someone will come up with a workaround for that...otherwise it's going to be portable/static versions if you want the latest releases.