-
Notifications
You must be signed in to change notification settings - Fork 331
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
Removing DRM from an Adobe Digital Editions failed #238
Comments
Have a look at using the DeACSM plugin instead of ADE. |
Update: Fixed it by myself. For the interested one who want to know how and for people having the same issue here is a explanation. There was an other issue. The exception showed in the log was caused, because there where no *.der key written under
in the initial setup of ADE in DeDRM. The cause where insufficient permissions of flatpak. I ran ADE with wine IN BOTTLES. Bottels (a wine management tool like PlayOnLinux) doesn't have permissions to do stuff in home and so doen't have this either. Then the next error occured. But that was a known one (Link1, Link2) that is fixed in the current master. After building DeDRM by my own from the current master branch, I got it working. Well, it tooks nearly five ours, but I learned some interesting stuff. |
Closed it, because the issue is fixed in the next release |
Question / bug report
I tried to import a file downloaded by Adobe Digital Editions. It shows up, but the DRM was not removed.
The WINEPREFIX is set up correct with ADE, vcredists, .NET 4.5 and Python 3.11.
While digging deeper in the log i found an exception in adobekey.py. You can see it in the attached log.
Additional informations:
I'm running Debian 12 with Python 3.10, Wine 7.0.1, Calibre 6.10 and DeDRM 10.0.3.
I also tried it on Windows 11, the same error occured.
Which version of Calibre are you running?
6.10
Which version of the DeDRM plugin are you running?
v10.0.3
If applicable, which version of the Kindle software are you running?
ADE: 4.5.11
Log output
The text was updated successfully, but these errors were encountered: