-
Notifications
You must be signed in to change notification settings - Fork 202
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 console problems (systrayiconplugin.py, maybe OpenSuse) #1677
Comments
Hello diwaffm, The To your primary problem: I assume that the I would suggest to update to the latest version 1.4.3 and try again. In the changlog of that version you can see that there are some modifications related to that component. Best, |
Hi buhtz, thanks for you answer. Ciao |
backintime-1.4.1-91.1.noarch works for me on Tumbleweed |
Thanks for reporting. Then it seems to be a more complex problem. "aryoda" will jump in but not so soon I guess. |
Thanks for the link and the info! I will see, if it finishes successfully - but so far, it seems to be working. Ciao |
Thanks for checking out. |
The manually initiated backup has now been successfully completed. However, I made the observation - which I do not know whether it is specifically related to this - that the phython process remained active after the backup. Ciao Dirk |
Sounds serious. Something is hanging or blocking in the back. |
This is, where I found the open processes, but I don't know, why this happens - and my knowledge at Linux may not be good enough to dig in deeper...
|
I discovered in your initial post how you start BIT:
BIT is not intended to be started via sudo. We have another related issue to this #1683 and think about how to improve the error message in case BIT is started via "sudo". But I am not sure if "sudo" is the reason for your problem. Please tell us more about your snapshot profile |
Hi!
I'm using BackInTime V1.4.1-3.2 (openSuSe).
Since I'm not in front of the computer, I'm checking the Backup via SSH / console.
Finding, that the last backup happend back in mid february, I wanted to dive in deeper.
The last backup was successfully created and the log is showing this.
But that's all for this profile (as well as for the other 2)
So I wanted to start BackInTime manually:
sudo backintime --profile EMKGHEU01 backup --debug
This gives me
Since nothin happens here any further, I wanted to cancel the backup and 2 more lines were shown:
Assuming, the backup process is starting now (since a lot of phython processes were running), I left the programm running over night - but nothing happens.
No further infos her nor at syslog.
Any Ideas?
Thanks
dirk
The text was updated successfully, but these errors were encountered: