mscore -F does not delete ~/.config/MuseScore/MuseScore2.ini.lock, causing musescore to freeze whenever try to modify the .ini
Can replicate on Lubuntu 15.04 both on nightly f07d7bb via mscore nightly ppa and on 2.0.2 via kxstudio ppa.
If ~/.config/MuseScore/MuseScore2.ini.lock exists before trying to perfom any operation that would modify the ~/.config/MuseScore/MuseScore2.ini file, then musescore will freeze. If this .lock file is removed, then the mscore is unfrozen and execution continues as normal. Executing mscore -F does not remove this .lock file. Since mscore -F is intended to force a revert into factory settings, my suggested fix is for mscore -F to forcibly remove this .lock file if it exists.
note: the ubuntu nightly .ini file is called ~/.config/MuseScore/MuseScoreDevelopment.ini and its corresponding lock file is /.config/MuseScore/MuseScoreDevelopment.ini.lock
A reason why the lock would be created and not destroyed is if for some reason the semaphore was created during an action that would modify the .ini file, but execution quit before the action was completed.
replication steps in ubuntu 15.04:
touch ~/.config/MuseScore/MuseScore2.ini.lock (or corrsponding development version)
then open musescore and try to perform any action that would modify the .ini file (e.g. file open, Open).
Diagnosis discussion: https://musescore.org/en/node/74891