Comment 11 for bug 692635

~/.config/lottanzb/log already contains all debug messages, no matter if LottaNZB was launched using --debug or not. The problem is that the crashes are not caused by unhandled exceptions in Python, but by nasty segmentation faults in the low-level GUI libaries (GTK, etc.) used by LottaNZB. This is why the problem is so hard to track down. The only possible way to get somewhat reasonable data is by running LottaNZB using GDB and wait for a crash to happen, so that one is given a stacktrace.