View Single Post
Old 11-16-2024, 08:47 PM   #10095
JimmXinu
Plugin Developer
JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.JimmXinu ought to be getting tired of karma fortunes by now.
 
JimmXinu's Avatar
 
Posts: 7,025
Karma: 4604635
Join Date: Dec 2011
Location: Midwest USA
Device: Kobo Clara Colour running KOReader
Quote:
Originally Posted by John Maverick View Post
Yes. FFF Seems to try opening the page in the default browser of the OS, but nothings happens
...
Yes, it works from Calibre. If click in the story id in Calibre the page of the story is opened in the Browser. It works with the default browser or choosing an specific browser from the setting "openers_by_scheme".
I did not recall correctly.

FFF imports webbrowser from python's standard lib and calls open(). Calibre jumps through a bunch of Qt hoops to call QDesktopServices.openUrl(qurl) OR runs a subprocess to call CLI program xdg-open.

I assume that something in your OS update either broke or 'secured' python's webbrowser as called from FFF.

Are you sufficiently python savvy to try testing it with a basic script? Or investigating if it's a per-program security thing?

Anyone else see this? I'm not real thrilled with the idea of adding a whole subprocess forking, but I could consider it if this is going to be a common problem.
JimmXinu is offline   Reply With Quote