You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I've been using BackInTime for quite some time now and I recently discovered that my automatically scheduled backups weren't running any more. So, I checked my config but couldn't find anything. I noticed, however, that the field for the SSH private key was empty. So I thought I would just re-enter my password and hope for the best (as a side note, I have the 'Save password to keyring' option enabled).
Unfortunately, when I then clicked on 'OK' to save the config, BIT just crashed. journalctl gave the following:
System Info:
OS: Manjaro 20.2.1
Kernel: 5.10.15-1-MANJARO
DE: Plasma
WM: KWin
backintime: 1.2.1 (installed from the community repo)
I hope this helps to find the cause of the bug. If you need more info I'm happy to help.
Thanks in advance!
The text was updated successfully, but these errors were encountered:
FMeinicke
changed the title
AttributeError: 'TempPasswordThread' object has no attribute 'isAlive'
AttributeError: 'TempPasswordThread' object has no attribute 'isAlive' (Python 3.9)
Feb 19, 2021
Hi,
I've been using BackInTime for quite some time now and I recently discovered that my automatically scheduled backups weren't running any more. So, I checked my config but couldn't find anything. I noticed, however, that the field for the SSH private key was empty. So I thought I would just re-enter my password and hope for the best (as a side note, I have the 'Save password to keyring' option enabled).
Unfortunately, when I then clicked on 'OK' to save the config, BIT just crashed.
journalctl
gave the following:Click to expand log
System Info:
OS: Manjaro 20.2.1
Kernel: 5.10.15-1-MANJARO
DE: Plasma
WM: KWin
backintime: 1.2.1 (installed from the community repo)
I hope this helps to find the cause of the bug. If you need more info I'm happy to help.
Thanks in advance!
The text was updated successfully, but these errors were encountered: