I'm asking because Ubooquity keeps user settings in files it creates when running.

If it can't create the files, settings will be lost when Ubooquity is stopped.

You can check if the settings files are properly created (and modified) when you run Ubooquity. Easiest one to check: preferences.json

Two points that are new to Ubooquity 2.0.X (just in case it could help):

• there are two different ports: one for the library (2202), one for the admin page (2203)
• by default, the admin page can not be reached from an external machine, you have to explicitely allow remote administration (either on the desktop UI if your run Ubooquity by clicking on the jar, or using the --remoteadmin command line argument)

No no, you did not order me. :)

My bad, english is not my first language, so I don't always manage to express exactly what I mean.

I'm just afraid sometimes that people donate hoping some specific feature in exchange.

So I try to explain I can't commit on anything.

Sometimes even (like right now) when there was no request in the first place.

Part of the "I don't care about the outside world" way of doing things of Apple. :/

You're not the only one annoyed by this: https://stackoverflow.com/questions/10924236/mac-zip-compress-without-macosx-folder

Please don't feel obliged to give anything.

Ubooquity is a hobby for me, I don't expect money in return. I do appreciate when people donate, of course, but feature implementation is not and will never be linked to donations.

Just a heads-up, I'm going to change the bookmark API in the next version.

I'm going to use Json structures instead of plain text (with additional data: a "finished" flag and a "last update timestamp").

I prefer to do it right now an try to keep the API stable afterwards.

Thnaks for the info.

Not much I can do except upgrade the PDFBox version whenever a new one is released.

I plan to allow pluging external PDF renderers in the future though.

Thanks for your feedback, glad you found a workaround.

PDF support is unfortunately far from perfect.

I have plans to improve it, but it will take time.

Does your execution directory have proper acces rights (read and write) for the user you are running your command with ?

Thanks for the proposal, but there is nothing I can do against file corruption: this is managed at a level (the database library) that is not run by my code.

As for the root cause, I can only guess the process was killed brutally at some point (power outage perhaps).