Kup keeps failing, even with all previous backups deleted

[gustavo1998]

What do I need to do to make Kup starting from scratch again? I deleted the entire content of the backup directory but it still fails. This is the log:

error: inflate: data stream error (invalid distance too far back)
fatal: pack has bad object at offset 748970957: inflate returned -3
b'pack-fe27e1faa6f365c08d2ff83607ef261ffebf044d' git verify: failed (1)

error: inflate: data stream error (invalid distance too far back)
fatal: pack has bad object at offset 39600373: inflate returned -3
b'pack-f1fb0ee2aa6df061ee068c5764160acf30a84741' git verify: failed (1)

fatal: pack is corrupted (SHA1 mismatch)
b'pack-0a0bcbc727e0676b4ec8be7d69e48f217c182cf1' git verify: failed (1)

fatal: pack has bad object at offset 809494946: inflate returned -5
b'pack-446cf2b3d887f3a1e46347116b4802473832277d' git verify: failed (1)

Exit code: 1
Kup did not successfully complete the bup backup job: failed to generate recovery info.​

[claydoh]

I don't use the stock version, it hasn't seen a new release in a bit, though the code is somewhat actively developed, it can be buggy like this.

I don't know how to restart the kup-daemon correctly, other than a logout/reboot, so often any changes or nuking requires this for changes to take effect.

You may need to nuke any plans, and recreate them (after a new login), or duplicate them, and remove the originals, and see what happens at the next login
Log files with better info are in ~/.cache/kup/
The config file is ~/config/kuprc -nuking this will reset things, but still requires reloading the daemon

An option to try would be to temporarily disable generating recovery information and verifying integrity for the plan, and seeing if that helps, after a new login.

[gustavo1998]

Thanks, temporarily disable generating recovery information and rebooting seem to have helped. Working now again.