View Single Post
Old 06-22-2025, 12:47 AM   #584
tomsem
Grand Sorcerer
tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.
 
Posts: 6,968
Karma: 27060153
Join Date: Apr 2009
Location: USA
Device: iPhone 15PM, Kindle Scribe, iPad mini 6, PocketBook InkPad Color 3
Quote:
Originally Posted by 0jay View Post
Thanks for your input, no joy this route either, similar error message.
If you are using HomeBrew (as I am) the workaround is to:

quit calibre

brew unlink openssl@3


launch calibre

-- install, configure and run the plugin and decode ASCM --

quit calibre

brew link openssl@3

The plugin will remain installed and configured but won't run until you run the 'unlink' command and re-launch calibre.

openssl@3 is a dependency for a number of brew-installed packages, including python3.

(to view dependency tree: brew deps --tree --installed)

Not very far upthread someone posted a proposed solution, but someone needs to test and create a PR for it.

Currently I average only 1 use of the plugin per month and do this on a Windows machine, since it works fine there and it is also where I have the Windows for PC deDRM setup in case I need it. I might otherwise forget to do the brew link step and run into problems running other things.

Last edited by tomsem; 06-22-2025 at 12:50 AM.
tomsem is online now   Reply With Quote