DoC Computing Support Group


Differences between revisions 1 and 7 (spanning 6 versions)
Revision 1 as of 2014-02-07 21:02:22
Size: 1454
Editor: ldk
Comment:
Revision 7 as of 2015-10-02 15:29:57
Size: 1940
Editor: ldk
Comment:
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 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.
Line 23: Line 23:
find ~/.mozilla/firefox -name lock -type l -exec rm {} \;
find ~/.mozilla/firefox -name .parentlock -size 0 -exec rm {} \;
cd
\
find ~/.mozilla/firefox -name lock -type l -exec rm {} \;
\find ~/.mozilla/firefox -name .parentlock -size 0 -exec rm {} \;
Line 30: Line 31:
find ~/.thunderbird -name lock -type l -exec rm {} \;
find ~/.thunderbird -name .parentlock -size 0 -exec rm {} \;
cd
\
find ~/.*thunderbird -name lock -type l -exec rm {} \;
\find ~/.*thunderbird -name .parentlock -size 0 -exec rm {} \;
Line 36: Line 38:
rm ~/.config/google-chrome/SingletonLock \rm -f ~/.config/google-chrome/SingletonLock
Line 39: Line 41:
If the above does not fix the problem:

{{{
mv "~/.config/google-chrome/Default/Web Data" "~/.config/google-chrome/Default/Web Data.bak"
mv "~/.config/google-chrome/Default/History" "~/.config/google-chrome/Default/History.bak"
}}}
Line 41: Line 49:
rm ~/.config/chromium/SingletonLock \rm -f ~/.config/chromium/SingletonLock
Line 44: Line 52:
If the above does not fix the problem:

{{{
mv "~/.config/chromium/Default/Web Data" "~/.config/chromium/Default/Web Data.bak"
mv "~/.config/chromium/Default/History" "~/.config/chromium/Default/History.bak"
}}}
Line 46: Line 60:
rm ~/workspace/.metadata/.lock \rm -f ~/workspace/.metadata/.lock

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

cd
\find ~/.mozilla/firefox -name lock -type l -exec rm {} \;
\find ~/.mozilla/firefox -name .parentlock -size 0 -exec rm {} \;

Thunderbird

cd
\find ~/.*thunderbird -name lock -type l -exec rm {} \;
\find ~/.*thunderbird -name .parentlock -size 0 -exec rm {} \;

Google Chrome

\rm -f ~/.config/google-chrome/SingletonLock

If the above does not fix the problem:

mv "~/.config/google-chrome/Default/Web Data" "~/.config/google-chrome/Default/Web Data.bak" 
mv "~/.config/google-chrome/Default/History" "~/.config/google-chrome/Default/History.bak" 

Chromium

\rm -f ~/.config/chromium/SingletonLock

If the above does not fix the problem:

mv "~/.config/chromium/Default/Web Data" "~/.config/chromium/Default/Web Data.bak" 
mv "~/.config/chromium/Default/History" "~/.config/chromium/Default/History.bak" 

Eclipse

\rm -f ~/workspace/.metadata/.lock
 
 

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