That's by design: shared folder must be distinct, one cannot contain another.

Thanks to the file you sent me I was able to reproduce the issue and fix it. 

The fix will be in the next minor verion (3.0.3). :)

Thanks for the bug report.

I just did a few changes to the PDF rendering part to fix another bug. So you can either wait for Ubooquity 3.0.3 that will include these changes to check if your issue is fixed, or (even better) send me some examples of PDF file that triggers this error so that I can investigate them directly. My email: tom at vaemendis dot net.

I could not find a PDF containing a jbig2 image in my collection (I seem to have lost the one I used to test my implementation a few years ago).

Would have one that could be shared (or sent to tom at vamendis.net) so that I can use it to reproduce the issue on my side ?

Nice !

About the workarounds, if you think about modifications that would make this kind of theme easier to make, let me know.

I can't make any promises, but if some easy to make modification to Ubooquity's code can help, I might as well throw it in.

Hello Luis,

The logout button does not need the userName variable, it just redirects to the /?logout=true URL, which logs the user out.

Also, Ubooquity will not serve any page other than the login page if the user is not logged in. So I'm not sure I understand the use case for making the userName variable available on other pages.

Apart from displaying the currently logged user name on every page, what would you use it for ?

Have a  nice day !

You have several options. You can either:

• For Ubooquity 2: launch Ubooquity in headless mode (details here), Ubooquity will not try to use Java FX. But you will not have any desktop UI.
• For Ubooquity 2: use an Oracle JRE that contains Java FX
• Use Ubooquity latest version (3 beta) and any JDK over version 17

Indeed, looks like a dependency issue.

I didn't change anything around this lib recently, but there must be some side effect, perhaps from the Java version increase (8 to 17 was a pretty big jump).

I'll look at it so that it's fixed in the next update.

Thanks for the investigation, it helps a lot. :)

This error comes from the network call (to my server) that checks if a new Ubooquity version is available.

The server had an issue for a few days, it's been fixed now.

However, this error does not prevent Ubooquity from running at all.