SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I guess that when aaa_elflibs was changed on 19 July 2019, the removal of libicudata.so.* and others killed calibre-3.40.1 from alien slackbuilds. I spent hours recompiling calibre to find that it also will not run. Help.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,070
Rep:
A foolproof alternative is to use Kovid Goyal's own install script (see https://calibre-ebook.com/download_linux ) since it also installs all dependencies. Of course I generally prefer proper slackware packages, but in some cases I've found it simpler just to install the bin files into /opt, instead of building or waiting for packages of upgraded programs that I use frequently.
Thanks very much for letting me know about icu4c-compat. Calibre works again.
Compiling calibre on an older Vaio laptop was a torture. I stopped checking on the build after 8 hours, and let the computer run overnight. Even though the slackbuild reported that it had successfully built calibre-3.40.1-i586-1alien.txz, calibre would not run, and actually had failed to build any calibre binaries. Not sure what happened, but it's working fine again. Thanks.
A foolproof alternative is to use Kovid Goyal's own install script (see https://calibre-ebook.com/download_linux ) since it also installs all dependencies. Of course I generally prefer proper slackware packages, but in some cases I've found it simpler just to install the bin files into /opt, instead of building or waiting for packages of upgraded programs that I use frequently.
My SlackBuild just packages what the install script installs.
Again a big thanks for your script which I have just used to update to the latest Calibre. Nice script and Calibre is an absolutely amazing application!
Thanks for the info andrew.46. This has been pretty annoying.
I ended up doing all io related device operations via a filemanager.
Indeed! It was like an old friend suddenly turned on me when Calibre failed to produce my books . On my own system I have solved the issue by compiling a new kernel (5.2.5 although anything after 4.19.50 should do the trick) with this patch.... Calibre now runs as before.
A foolproof alternative is to use Kovid Goyal's own install script
Another foolproof alternative were if mr Kovid Goyal could provide just a one file AppImage. I even emailed him asking for that months ago, but never got any answer.
Is anyone having any joy with this on a stock current setup yet?
Neither Alien's 4.2.0 or the SBo Calibre-bin 4.5.0 work here with my Kindle Paperwhite 3 without first reverting kernel commit bd8309de0d60838eef6fb575b0c4c7e95841cf73.
With that commit reverted all is good
Without, stock, much unhappiness...
Code:
[ 5077.306338] sd 2:0:0:0: [sdc] tag#0 access beyond end of device
[ 5077.306354] blk_update_request: I/O error, dev sdc, sector 17 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
[ 5077.306363] Buffer I/O error on dev sdc1, logical block 1, lost async page write
etc etc, with failed transfers, a corrupted and read-only filesystem on the Kindle.
Another foolproof alternative were if mr Kovid Goyal could provide just a one file AppImage. I even emailed him asking for that months ago, but never got any answer.
I was putting some thought into building a Docker image that could be used to build a Calibre AppImage, but as soon as I actually wrote those words I realized how ridiculous they were.
Keep in mind that a Calibre AppImage these days should really have its own bundled Python 2 interpreter, as the port to Python 3 is still a work in progress.
Is anyone having any joy with this on a stock current setup yet?
Neither Alien's 4.2.0 or the SBo Calibre-bin 4.5.0 work here with my Kindle Paperwhite 3 without first reverting kernel commit bd8309de0d60838eef6fb575b0c4c7e95841cf73.
With that commit reverted all is good
Without, stock, much unhappiness...
I am still routinely reversing that commit when I rebuild a kernel, I feel a little better that somebody else has bumped into the same issue...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.