-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backintime 1.1.8 crashes on startup if it is executed as user #473
Comments
Thanks Ronan! This is caused by adding debug messages in |
This still looks like a race condition to me. Even with the patches here, I still get that warning every so often:
|
@catalin-hritcu Please use this patch with:
and post the output if the warning appear again |
I'm trying it now and will report back. Please note though, that this prints something for me even when there is no warning:
Is this expected behavior? |
Note that this output goes away if I install the [Added:] Apparently |
I've tried starting backintime at least 100 times and since installing
Not sure whether the two are in any way correlated though ... |
Absolutly. That was the source for the warning. But since we only serve one There is |
I still get
|
I just had a look at So, if you don't have There are two ways to fix this:
tl;dr I'd call this a bug of |
Hi guys!
When I try to run backintime 1.1.8 as user, it crashes with the following message:
Notice that it works if backintime is executed as root. Everything was fine with version 1.1.6.
I tracked the problem and it turns out that what is causing this issue is the line 18 of
configfile.py
:The cause is: when I run backintime as user, then
keyring = None
intools.py
. This trigger the following code:that outputs the aforementioned error. Otherwise, if I run as root, then
keyring != None
and that code will not be executed.As a temporary fix, I notice that if I add
import tools
beforeimport logger
inconfigfile.py
, then everything works.Can anyone tell me if this is the proper fix for the problem?
Regards,
Ronan
The text was updated successfully, but these errors were encountered: