vorta
vorta copied to clipboard
Uncaught exception
I received this message on boot of my computer:
Uncaught exception, please file a report with this text at
https://github.com/borgbase/vorta/issues/new
Traceback (most recent call last):
File "/app/lib/python3.9/site-packages/vorta/application.py", line 186, in set_borg_details_result
self.scheduler.reload_all_timers() # Start timer after Borg version is set.
File "/app/lib/python3.9/site-packages/vorta/scheduler.py", line 333, in reload_all_timers
self.set_timer_for_profile(profile.id)
File "/app/lib/python3.9/site-packages/vorta/scheduler.py", line 274, in set_timer_for_profile
self.create_backup(profile_id)
File "/app/lib/python3.9/site-packages/vorta/scheduler.py", line 380, in create_backup
msg = BorgCreateJob.prepare(profile)
File "/app/lib/python3.9/site-packages/vorta/borg/create.py", line 74, in prepare
ret = super().prepare(profile)
File "/app/lib/python3.9/site-packages/vorta/borg/borg_job.py", line 152, in prepare
ret['password'] = cls.keyring.get_password('vorta-repo', profile.repo.url)
File "/app/lib/python3.9/site-packages/vorta/keyring/secretstorage.py", line 50, in get_password
if self.is_unlocked:
File "/app/lib/python3.9/site-packages/vorta/keyring/secretstorage.py", line 66, in is_unlocked
return not (self.collection.is_locked() and self.collection.unlock())
File "/app/lib/python3.9/site-packages/secretstorage/collection.py", line 67, in unlock
return unlock_objects(self.connection, [self.collection_path])
File "/app/lib/python3.9/site-packages/secretstorage/util.py", line 151, in unlock_objects
dismissed, (signature, unlocked) = exec_prompt(connection, prompt)
File "/app/lib/python3.9/site-packages/secretstorage/util.py", line 138, in exec_prompt
assert dismissed is not None
AssertionError
Sometime after this, the backups were completing successfully, so I'm not really sure what the error is, so it's just copy and paste here as requested.
Linux Mint 20.3 Vorta 0.8.6
Seems to be a duplicate of #1267 and #1216. I think this is an issue of secretstorage. It therefore makes sense to open an issue there.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.