Hmm… It should have been fixed:
opened 01:41AM - 05 Jun 24 UTC
closed 12:22PM - 01 Aug 24 UTC
- [x ] I have searched open and closed issues for duplicates.
- [ ] I have sear… ched the [forum](https://forum.duplicati.com) for related topics.
----------------------------------------
## Environment info
- **Duplicati version**: 2.0.9.100_canary_2024-05-30
- **Backend**: Google Drive
## Description
Installed new canary on Macbook Pro (M2) Sonoma 14.5, killed old mono64 tasks [Duplicati] (2.0.7.103_canary_2024-04-19), started new Duplicati (2.0.7.103_canary_2024-04-19); no backup configs shown on GUI.
## Steps to reproduce
1. see above
- **Actual result**:
no backup configs show on GUI
- **Expected result**:
pre-existing (6) backup configs shown on GUI
## Screenshots
## Debug log
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.
ts678:
Maybe, if not too revealing about problems with current scheme. Or maybe post it somewhere.
The issue captures the main need, which is how to deal with the additional challenges it raises.
These do go somewhat hand-in-hand, as people will want to know the usefulness of more pain.
I have posted the description here .
katertje:
and updated a Ubuntu machine,
Duplicati didn’t know what to do with the %HOME% folder that was set up in the backup, so unselected that.
apart from that, noticed that the first backup was a full one.
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?