Comment 8 for bug 318146

I don't see anything obviously wrong with those depends (i.e. I don't see you depending on 'libbreak-my-build').

I can say that your preferences are exceedingly normal (you only seemed to change one setting -- how often to automatically backup). So that doesn't seem like you have an unexpected setup or odd input that deja-dup chokes on.

The backtrace you gave me doesn't have any symbols, which if you compiled with --enable-debug, indicates to me it's going way off the deep end. I'd expect to see at least some deja-dup symbols there. Instead it seems memory is very corrupted.

So I'm stumped. Without being able to reproduce this, I can't do much.

Maybe try turning gcc optimizations off? Is this on a non x86 architecture?