Description
Description
I have two profiles. The first one backs up really critical stuff to my BorgBase remote repo, the second one backs up my entire home directory to a NAS in my home network. Switching between those profiles takes a long time - about 25 seconds. During that time, the program window is unresponsive, Kubuntu greys out the window and says that Vorta "does not react" and offers me to kill the process.
Unfortunately, I can't pinpoint the exact version of Vorta where this issue occurred the first time. I believe it was introduced when the profiles were moved to the left side of the window, but I might be wrong.
Here is a screencast to show how long it takes (Repo location blurred out, of course): https://youtu.be/xVuywsOY4Go?si=yousLqS0vgW8sPF7
Reproduction
- I tried to reproduce the issue.
- I was able to reproduce the issue.
OS
Kubuntu 23.10
Version of Vorta
0.9.1
What did you install Vorta with?
Flatpak
Version of Borg
1.2.4
Logs
###### First, I do a manual backup to have a timestamp. (File paths are redacted for privacy reasons, the backup worked as expected)
2024-03-10 19:46:14,443 - vorta.keyring.abc - DEBUG - No module named 'objc'
2024-03-10 19:46:14,446 - vorta.keyring.abc - DEBUG - Using VortaKWallet5Keyring
2024-03-10 19:46:14,447 - vorta.borg.borg_job - DEBUG - Using VortaKWallet5Keyring keyring to store passwords.
2024-03-10 19:46:14,456 - vorta.keyring.kwallet - DEBUG - Retrieved password for repo ssh://user@server/path/to/repo
2024-03-10 19:46:14,689 - vorta.borg.jobs_manager - DEBUG - Add job for site 4
2024-03-10 19:46:14,690 - vorta.borg.jobs_manager - DEBUG - Start job on site: 4
2024-03-10 19:46:14,794 - vorta.borg.borg_job - INFO - Running command /app/bin/borg create --remote-path=/usr/local/bin/borg --list --progress --info --log-json --json --filter=AM -C lz4 --exclude-from /tmp/tmp3o0wty6i ssh://user@server/path/to/repo::archive-name /data/to/back/up
2024-03-10 19:46:16,367 - vorta.borg.borg_job - INFO - Creating archive at "ssh://user@server/path/to/repo::archive-name /data/to/back/up"
2024-03-10 19:47:10,242 - vorta.scheduler - INFO - Setting timer for profile 1
2024-03-10 19:47:10,259 - vorta.scheduler - DEBUG - Scheduling next run for 2024-03-10 20:26:31.443721
2024-03-10 19:47:10,351 - vorta.borg.jobs_manager - DEBUG - Finish job for site: 4
2024-03-10 19:47:10,351 - vorta.borg.jobs_manager - DEBUG - No more jobs for site: 4
###### Backup has finished w/o problems, right after that I clicked on another profile.
2024-03-10 19:47:39,923 - vorta.views.source_tab - DEBUG - Added item number 0 from 1
2024-03-10 19:47:39,924 - vorta.views.source_tab - DEBUG - Added item number 1 from 2
2024-03-10 19:47:39,925 - vorta.views.source_tab - DEBUG - Added item number 2 from 3
2024-03-10 19:47:39,925 - vorta.views.source_tab - DEBUG - Added item number 3 from 4
2024-03-10 19:47:39,926 - vorta.views.source_tab - DEBUG - Added item number 4 from 5
2024-03-10 19:47:39,926 - vorta.views.source_tab - DEBUG - Added item number 5 from 6
2024-03-10 19:47:39,926 - vorta.views.source_tab - DEBUG - Added item number 6 from 7
2024-03-10 19:47:39,927 - vorta.views.source_tab - DEBUG - Added item number 7 from 8
2024-03-10 19:47:39,927 - vorta.views.source_tab - DEBUG - Added item number 8 from 9
2024-03-10 19:47:39,928 - vorta.views.source_tab - DEBUG - Added item number 9 from 10
###### Only now, the profile was actually switched, and I could interact with Vorta again.