Changes between Initial Version and Version 2 of Ticket #6044


Ignore:
Timestamp:
2015-08-08T13:17:35+02:00 (10 years ago)
Author:
michael2402
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #6044

    • Property Priority critical → major
    • Property Summary [data loss] preferences_backup overwritten when preferences gets damaged → preferences_backup overwritten when preferences gets damaged
    • Property Cc michael2402 added

  • Ticket #6044 – Description

    initial v2  
    11My computer crashed and as a result, preferences file got truncated to zero size (XFS filesystem does this to files that got damaged). As a result, once I started JOSM again after the computer crashed, josm loaded, the preferences_backup got immediately overwritten by default config (as the file was empty), therefore backup preferences got lost.
    2 
    32I think the preferences_backup in current implementation is pointless (I lost my preferences and I had to restore the file from backup), as it seems to be written on every preferences change.
    43To server any useful purpose, the preferences should be copied to preferences_backup only on successful, non-crash exit (so if you notice your preferences are lost after starting JOSM, you§ll have still your preferences in preferences%backup, that could still be saved aside and then used to restore your old preferences)