I far as I can tell, this is caused by ~/.config/unity-tweak-tool/pid.lockfile not being deleted on exit. After a while the pid in that file can be another random process, and trying to connect to it on startup as a unity-tweak-tool process will crash.
Workaround is to manually delete ~/.config/unity-tweak-tool/pid.lockfile when this happens
I far as I can tell, this is caused by ~/.config/ unity-tweak- tool/pid. lockfile not being deleted on exit. After a while the pid in that file can be another random process, and trying to connect to it on startup as a unity-tweak-tool process will crash.
Workaround is to manually delete ~/.config/ unity-tweak- tool/pid. lockfile when this happens