Release: 2.0.9.104 (Canary) 2024-08-21

Hmm… It should have been fixed:

Did you run any versions in between 2.0.8.1 and 2.0.9.104? The logic checks for both an old and new. If a database on the new path is found, that database is found. If you had 2.0.9.100 installed, it would have created the new database, causing it to ignore the old one.

I have posted the description here.

To replicate this, you had:

  • Setup a backup on Ubuntu with 2.0.8.1, which made a backup of %HOME% (checking the user folder)
  • Update to 2.0.9.104
  • Fails to backup due to missing %HOME% folder

Is that accurate? What version of Ubuntu is this?