...
A simple command to delete this lock file will do the trick: rm /home/$USER/.config/google-chrome/SingletonLock
The $USER variable will be expanded to be the username of the user who executed the command.
...
Alternatively, a user can use the file manager to navigate to /home/$USER/.config/google-chrome/ and remove the SingletonLockfile.
Crash reason 2:
There is a standing issue where two computers in the CS Lab (TedCodd and Ritchie) are not able to open a recent version of Google Chrome. The Chromium team is aware of the issue and the bug report is here: https://bugs.chromium.org/p/chromium/issues/detail?id=1493307
...
The files to delete are located within the user's profile directory /home/$USER/.mozilla/firefox/*.default/ where * is a placeholder for Firefox's profile hash. The specific files to delete are lock and .parentlock. This one line command should remove those files:
rm /home/$USER/.mozilla/firefox/*.default*/lock
File manager fix
In your preferred file manager, you are able to navigate to the directory which holds the lock on Firefox in /home/$USER/.mozilla/firefox/*.default/ Since it is impossible to know what the user profile's hash is and if they are using a default profile versus a custom profile, it is recommended to go each folder that has default or default-release appended.
