-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
ModuleNotFoundError: No module named libadobe #92
Comments
I get this output from running
Lots of errors, though I suspect some are expected since this is meant to be portable across multiple OSes. |
Okay installing DeDRM first made was what I needed to do to make this work. Unfortunately it doesn't work, if I import an acsm file it stays an acsm file, but that's separate to this issue. For this issue it'd be nice if there was a more comprehensive README + better error messages. |
Installing DeDRM is not needed for this plugin to function in general. I suspect a Calibre restart or computer restart might have solved this particular problem. During the bundling, it fails to compile the keyextract code since you don't have the proper compiler installed, but that should't stop the plugin from functioning since it's only needed on Linux anyways, not on Windows or MacOS. If the plugin fails to turn ACSM files into EPUBs, there's another error so you'll need to run Calibre in debug mode and check the logs again (or post them here). I know the error handling for the plugin isn't always the greatest, most of the issues come from the fact that the plugin needs to load 3rd-party python plugins (which almost no other Calibre plugin does) and that doesn't always work properly. |
Bug description
Same repro steps as in: #72. Seems like #88 perhaps didn't fix it for MacOS. I'm using the default
sed
.I cloned the repo from master (commit 27bd953).
I get this error:
Operating system
MacOS
Which version of Calibre are you running?
7.12.0
Which version of the ACSM Input plugin are you running?
From commit 27bd953
Import type
No response
Further information
No response
The text was updated successfully, but these errors were encountered: