Christian Buhtz

We have not modified the remove snapshots code yet. But might it be possible to check again with the latest BIT version and give us some more instructions to reproduce...

I assume that @lamyergeier mixed user- and root-crontab here. There is also no feedback from the reporter for over 4 months. I vote for close.

Dear @freder , can you report back please if you are still able to reproduce your problem with the latest version (1.3.3) of BIT?

I've seen this, too in 1.3.4-dev. But again I can't reproduce it for sure. But I do see a trail and need to further investigate the code. https://github.com/bit-team/backintime/blob/72ced78a5ee3c7803e0cba16e11698af4d883535/qt/snapshotsdialog.py#L342-L347 There are...

Frederic we are currently working (#1682) on the snapshots dialog and its compare feature. Can you somehow reproduce the problem with a newer version of BIT and can you provide...

My apologize. Something went wrong. I just tried to update your `Zocker1999NET:dbus-notifications` to the current state of `bit-team/backintime:dev`. I rolled back my last commit with ``` git reset --hard HEAD^...

I figured out how to update/sync the fork with current upstream state. I also modified the TravisCI setup with `apt install libdbus-glib*` and `pip install dbus-python`. The tests on AMD64...

I did some research about the basic functionality and behavior of user-callback. As a side-product I created some unit-tests (#1639) but they won't help solving this actual PR. To my...

> is called by BiT **after** `self.config.PLUGIN_MANAGER.unmount(self.profile_id)` (=> user-callback) which is strange I think because it should be called after above unmount so that we don't need a `postUnmount` at...

I have seen this with 1.3.4-dev but wasn't able to reproduce it for sure. 😄 The trigger seems to be the diff dialog but the output provided and I've seen...