1457
Comment:
|
1456
|
Deletions are marked like this. | Additions are marked like this. |
Line 12: | Line 12: |
lock files they are considered ''stale''. Their presence may prevent subsequent | lock files they are considered ''stale''. Their presence may stop subsequent |
Line 30: | Line 30: |
find ~/.thunderbird -name lock -type l -exec rm {} \; find ~/.thunderbird -name .parentlock -size 0 -exec rm {} \; |
find ~/.*thunderbird -name lock -type l -exec rm {} \; find ~/.*thunderbird -name .parentlock -size 0 -exec rm {} \; |
Unlocking Applications
Your graphical session on a departmental Linux computer may, from time to time, be interrupted by some unforeseen event:
- power disconnection or failure.
- network outage.
- system crash.
At your next graphical session, you may find that some applications have left behind lock files. If there is no running application associated with these lock files they are considered stale. Their presence may stop subsequent launch of applications that check to prevent more than one application instance being run at a time.
Please find below commands to run in a terminal to remove stale lock files for a number of common applications. After running the relevant commands, you should then be able to launch the affected applications.
Please note: if you have exceeded your quota, you should address that first.
Firefox
find ~/.mozilla/firefox -name lock -type l -exec rm {} \; find ~/.mozilla/firefox -name .parentlock -size 0 -exec rm {} \;
Thunderbird
find ~/.*thunderbird -name lock -type l -exec rm {} \; find ~/.*thunderbird -name .parentlock -size 0 -exec rm {} \;
Google Chrome
rm ~/.config/google-chrome/SingletonLock
Chromium
rm ~/.config/chromium/SingletonLock
Eclipse
rm ~/workspace/.metadata/.lock