-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to load DeDRM_calibre_plugin with calibre 4.1 on Fedora 31 #928
Comments
I don’t know about the DeDRM plugin in particular, but Calibre is currently a python 2 application. Work is underway to make it Python 3 compliant, but it is not yet complete and I suspect that many plugins won’t be updated until Calibre itself is ready. See https://calibre-ebook.com/download_linux for info about installing under Linux. |
This is not true, Calibre already supports Python 3, at least on my system (Fedora 31) Calibre 4.1 is built and running with Python 3. Seems there is no workaround to load DeDRM from Python 3 Calibre. Hi DeDRM maintainers, is there any plan on supporting Python 3 for DeDRM_calibre_plugin? |
Doing nothing but running I guess a work around would be to try to get a calibre flatpak running it under py2 ? I don't know if the hardware support would work though. |
I can only confirm it. |
It is massive pain, but boxes and F30 came to the rescue. |
DeDRM plugin works on fedora 31 with calibre 3.48.0 installed. The rpm from F30 does not run but a binary install with the command below works: sudo -v && wget -nv -O- https://download.calibre-ebook.com/linux-installer.sh | sudo sh /dev/stdin install_dir=/usr/local version=3.48.0 |
Similar results with Calibre 4.5 on Fedora 31 with Python 3.
|
@audetto did you find a workaround? If so, what was your solution? |
I also installed F30 in Boxes. That is quite an easy workaround as workarounds goes. I guess some of us experiencing most pain will eventually start porting the python 2 code... |
And there is already a Py3 conversion going on: #931 |
The Flatpak image on flathub works with OBOK without special configuration:
|
That's great information and I might end up installing it (even though a voice within me whispers that developers and users are becoming lazy when they prefer keeping and installing old frameworks and blobs, filling up our hard disks with redundant libraries within flatpaks, snaps and appimages, and hindering progress). - insert old man yells at cloud image here - |
There's ongoing work to port the library to py3k, this has been fine in the interim. :) |
I am running FC-31 and Calibre 4.12.0. [But I was able to successfully install the other recommended plugin: kfx-input.zip] Looking at that line of code, I commented it out (it's just a print statement after all) to see what would happen. Well, a similar print statement on line 179 threw an exception. Unfortunately, it was inside an exception handling block so clearly I was screwed. I could not figure out what was wrong, so I googled this issue and found this and other pages. Reading it all, it seemed clear that the issue had to do with Calibre and Python 3 incompatibilities and that there was nothing to be done until the Calibre folks addressed the issue. Out of curiosity, I imported the AZW4 Kindle Fire file for the Kindle eBook I recently bought. The import succeeded w/o incident, so I took the next step of converting it to PDF expecting to see decryption errors of some type. WTF!!! It worked!!! I have no idea why. Maybe something in the kfx-input plugin? Maybe the Kindle file I purchased was not encrypted? Dunno, but I got what I wanted and don't wish to make a career over the DeDRM plugin issue. Has Amazon stopped encrypting their Kindle books? Just thought I'd pass this on. Rich |
As I said in the other issue, that book must have already been DRM-free. Some publishers allow their books to be sold without it. Most of the big publisher still require it though. |
ElleKayEm - thank you. |
For anyone still trying to get this to work. Installing Calibre from the tarball worked for me on Fedora 32. Download the calibre tarball. https://download.calibre-ebook.com/3.48.0/ Then install it. Change the path of course. sudo mkdir -p /opt/calibre && sudo rm -rf /opt/calibre/* && sudo tar xvf /path/to/downloaded/calibre-tarball.txz -C /opt/calibre && sudo /opt/calibre/calibre_postinstall Then go through the process of installing the deDRM plugin. I installed version 6.8. |
You can go up to calibre 4.23 with DeDRM 6.8. |
+1, this bug occurs with latest Calibre 5.x! Can't use DeDRM in Calibre 5.4.2. |
@strarsis |
Try the 7.0.0 betas |
Hi,
I'm running calibre 4.1 on Fedora 31 which has Python3 as default, while loading "DeDRM_plugin.zip", I got error messages as below:
And this is the calibre info:
It seems the DeDRM plugin only support python2, is there a workaround for me to load and enable the plugin? Fedora 31 has Python3.7 as default, but Python2.7 is also available.
The text was updated successfully, but these errors were encountered: