Germar Reitze
Germar Reitze
Okay, I fixed suspend on my machine but I'm still not able to reproduce the bug here. Please run `backintime backup --debug` from terminal and post the output here. There...
Ah, okay. I didn't found a way to inhibit suspend with `root`, yet. The normal method is using DBus SessionBus. But `root` has no SessionBus.
That would get quite ugly. There must be an other way. I just have to search for it... :wink:
Please run `sudo nano /etc/udev/rules.d/99-backintime-$(whoami).rules` and replace `>/dev/null` at the end with ``` --debug 2>&1 >/tmp/bitudev.log ``` do not start BiT again because it would overwrite the rule. Just plug...
This shouldn't be related to additional profiles because the lock in question is used per profile. Please post the return of `crontab -l`
I can't reproduce this here, sorry. Please send me you `~/.config/backintime/config`
Still no errors here, sorry. Please make a test with a simple user-callback which just returns all args ``` #!/bin/bash echo $@ ``` add `--debug` to both commands in crontab...
I just made myself a new Fedora 25 VM and tried to reproduce this. But I'm sorry to say that I can't reproduce your result. BiT just react like it...
Nope. That's all pure python code. Do you use any fancy filesystems for your /home or /tmp?
> Does BIT use an rsync server somehow? No, it doesn't > I thought when using a SSH profile snapshot there is no rsync-server but an ssh-server (at remote machine)...