When I was referring to the latest version of backintime, I was referring to the latest version provided through the Chakra repositories… as that would be logical to assume… that would be 1.1.20-2…
Sourcing outside the repositories providided by and for the OS may cause instabilities… that argument can be read plenty of times in multiple threads on several topics!
While the argument above might not be true for backintime, I must stress it’s a backup application - though just be a gui still for rsync.
I hope you can understand that I am not readily chosing this solution for a backup application, for e.g. a music player I would do that.
Luckily one can just copy paste from the desired backup folder backintime makes for each backup…
I am not some linux wizard, but I did find out it had to do with bug #552 fixed under the 1.1.22 release - if I am correct could have been solved simply by editing one of the py scripts.
Why it messed up my other backup drive with ntfs I haven’t found out yet.
This problem has nothing to with the chakra team, apart from maybe accepting the newer version in the repos - which as I have understood happens with tested stability.
Sorry for my lengthy reply, I hope you understand, and that I am just caring for my data.
Off topic, I did a complete reinstall of my system, wiped suse too and put back the goedel 2017.03 release this morning… it might be even that my cheap laptop isn’t all that great, and that I really have to review some problems on new hardware I plan to get within a couple of months.