DoC Computing Support Group


Differences between revisions 1 and 2
Revision 1 as of 2014-02-07 21:02:22
Size: 1454
Editor: ldk
Comment:
Revision 2 as of 2014-02-08 10:14:10
Size: 1457
Editor: ldk
Comment:
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
a number of common applications. After running the relevant commands, you should be
able to launch the affected application(s).
a number of common applications. After running the relevant commands, you should then be
able to launch the affected applications.

Unlocking Applications

Your graphical session on a departmental Linux computer may, from time to time, be interrupted by some unforeseen event:

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 prevent 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
 
 

guides/linux/locked-apps (last edited 2023-10-25 09:54:37 by ldk)