I tested the official version (3.1.1, amd64 debs) but was unable to reproduce the bug.
While installing and removing packages, I noticed that I was able to to get one successful save when the Ubuntu version's -gnome and -gtk packages were not installed. However, the bug reappeared at the next attempt. This gave me the feeling that the time/number of cycles/available processing power it takes to save AutoRecovery information is somehow central to this. Without -gnome and -gtk it happens quicker. I also tried to stress my system (urandom > null on each CPU core) while running the official version which made AutoRecovery take longer than with the Ubuntu version but was unable to make it fail.
- It seems to be Ubuntu-specific
- It seems to be related to time/number of cycles/available processing power of AutoRecovery
I tested the official version (3.1.1, amd64 debs) but was unable to reproduce the bug.
While installing and removing packages, I noticed that I was able to to get one successful save when the Ubuntu version's -gnome and -gtk packages were not installed. However, the bug reappeared at the next attempt. This gave me the feeling that the time/number of cycles/available processing power it takes to save AutoRecovery information is somehow central to this. Without -gnome and -gtk it happens quicker. I also tried to stress my system (urandom > null on each CPU core) while running the official version which made AutoRecovery take longer than with the Ubuntu version but was unable to make it fail.
- It seems to be Ubuntu-specific
- It seems to be related to time/number of cycles/available processing power of AutoRecovery