The problem is that the Java version you are using does not contain the UI framework used by Ubooquity.

To fix that, either:

• use the official Oracle JRE (or JDK) instead of OpenJDK
• try using the "--headless" command line option that will disable the desktop UI, allowing Ubooquity to run without these libraries (no guarantee of success though).

In any case I recommend using the Oracle version of Java.

Advanced search has been on my todo list for as far as I can remember (boolean operators would be part of this feature, they're not completely trivial to add). But for now I still have a lot of items I consider of higher priority.

So not in a near future I'm afraid...

To be honest I don't remember having tested a custom workdir with a custom log configuration.

My advice is to always use an absolute path for the custom log config file.

Now perhaps that's an issue when using a container...

Elouan's right, the font issue impacts only the epub online reader. Your issue is something different.

Unfortunately I can't help much (I don't have a NAS).

As I wrote earlier, the database file is entirely managed by the database library used by Ubooquity (H2, which is a very widely used, very robust library).

Now, between Ubooquity 1.10.1 and 2.0.0, I updated the H2 version from 1.4.187 to 1.4.193.

This should not have caused any issue, but funny side effects that happen only on specific setups are always possible.

So I built two special versions of Ubooquity 2.1.0:

• One with H2 1.4.187 (the one used in Ubooquity 1.10.1)
• One with H2 1.4.196 (the latest one available, in case a recent change has fixed your issue)

So if you're still interested in using Ubooquity 2.x, you can try these versions in case they work better for you.

Of course, I would be interested in knowing the result of your tests. I don't know if it could be enough to pinpoint the cause of your issue, but you never know...

The logs displayed in the admin interface are limited to 1000 lines.

This log page is intended to provide an idea of the last events that happened on the server, not parse and display the full log file, that can be quite big depending o the logger configuration.

For a complete review of the logs, looking at the original log file like you did is the right thing to do.

Already planned (no ETA though).

See this post for a workaround.

Nice ! I didn't know this one. :)

Ubooquity needs writing authorization on the files located in its working directory.

Did you happen to launch Ubooquity manually the first time (allowing to create all its files with user A) then as a service (with user B, hence the rights problem) ?

Same answer as above: send me a link where I can download an example of mobi file for which Ubooquity does not correctly guess the cover, and I'll take a look to see if the extraction algorithm can be improved.