Backintime hangs with 'Working: Save permission'

I also experienced this problem just today. I am running Ubuntu 9.10 64-bit. I have been using Back In Time for a while with no apparent problems until this happened. I finally had to rebvoot. I cannot find any log files that might. It is not clear where Backintime stores its data. I tried looking under /root/.local/share/backintime, but its is empty. I looked there because I run Back in Time as superuser. The version number is 0.9.26.

I'm seeing the same problem on Ubuntu 10.04 beta 1 (now beta 2) with v9.26-3

I have two jobs scheduled. One writes my a copy of my home directory using my account the other runs as root and saves /etc, /usr/local, /opt, /var. Both write to the same folder. So far it's been working ok. I just use browse as root to check the contents of those saved using root privileges. I did find that doing things this way (two accounts writing in the folder) meant that it was important the a user account job created the folder in the first place, otherwise it wouldn't be able to write in the folder.

(the destination is an nfs share on a remote box which has always worked perfectly)

The advantage of having everything in one folder is the ability to browse all the snapshots in one place (it would be nice to have a color coded display for those made with root privilege).

It's the user priv version that's hanging. I've noticed that the last couple of snapshots end with -000000. As both root and user jobs are scheduled daily and now seem to run at midnight which might suggest that there are two different jobs trying to lock the same destination but I presume not if others have the same problem running a single job as root?

The top level folder of the last snapshot has a lock, the files and folders underneath it show locks (and, yes, owner root root). I don't know if this is normal during a job or not.

sudo chown -R username:users snapshotname

didn't make any difference to completing the job.

I've since found this

Quote

If you run /usr/bin/backintime as root, it uses /etc/backintime/config for configuration.
If you wish to run backintime as a regular user, copy the /etc/backintime/config file to ~/.config/backintime/config.

Unquote

here: http://distractedfocus.blogspot.com/2010/03/backintime-on-centos-5x.html

which I hadn't really thought about (i.e., two config files).

I'd be happy to have the option to just run as root with the ability to restore original ownership. I haven't checked if this is the current default, sorry.

I'll switch for now to just doing everything with root and worry about ownership if I need to do a restore.

I'm attaching an extract from the log file which does seem to suggest resource contention between root and user accounts.

sysog file excerpt attached

I think this is fixed in beta version. Please give try it.

Bug reappeared in Ubuntu Lucid 64 bit (new install).

I had this happen to me on a 32-bit Ubuntu Lucid install, using version 1.0.10.

Sorry, this happened when I was running backintime as root. I only have it configured to do one type of backup, without a schedule. It seems to have completed the backup and just hung on Saving Permissions... Will try to replicate the problem tomorrow.

I have this bug in 14.04, version 1.0.34

It shows Saving Permissions when I start it, before it does a backup

please remove ~/.local/share/backintime/worker.message. This should make the message disappear.