Chromium inaccessible
Solved
tetdeuf
Posted messages
31
Status
Member
-
UnDev -
UnDev -
Hello,
Since the upgrade to version 11.04 on Ubuntu, I can't open Chromium; the following message appears when I try to open this browser.
The profile appears to be in use by process 2108 on host andre-desktop. If you are sure that no other process is using this profile, delete the file /home/andre/.config/chromium/SingletonLock and restart Chromium.
I don’t understand what this means; I previously had Firefox and Chromium, and everything worked perfectly... if someone could explain... thank you in advance.
Configuration: Linux / Firefox 5.0
Since the upgrade to version 11.04 on Ubuntu, I can't open Chromium; the following message appears when I try to open this browser.
The profile appears to be in use by process 2108 on host andre-desktop. If you are sure that no other process is using this profile, delete the file /home/andre/.config/chromium/SingletonLock and restart Chromium.
I don’t understand what this means; I previously had Firefox and Chromium, and everything worked perfectly... if someone could explain... thank you in advance.
Configuration: Linux / Firefox 5.0
1 answer
Basically, Chromium "locks" your user profile (stored in /home/andre/.config/chromium) for the entire time you are using Chromium. The purpose of such a lock is to prevent you from launching Chromium multiple times.
In theory, it is supposed to unlock when you close Chromium. However, if you exited Chromium improperly or it crashed, a residual lock might still exist in your profile.
In this case, Chromium asks you to check whether the lock is warranted (in other words, to check that you don't already have an instance of Chromium running). Each process (each task) is identified by a PID (process identifier), which is an integer. Chromium suspects that process 2108 is another instance of Chromium and therefore refuses to launch.
There are two possibilities:
1) Either Chromium is indeed already running, and it's normal for it to refuse to launch again
2) Or a residual lock is blocking everything, and you need to delete that lock.
Start by opening a terminal:
http://doc.ubuntu-fr.org/terminal
1) Chromium is already running!
You can check if Chromium is running by looking at the running processes, for example with the command:
If a line appears with the value 2108, it's likely that an instance of Chromium is already in the process of launching, so the warning from Chromium is justified. You can then decide whether to kill this process or not:
For more details:
http://www.mistra.fr/tutoriel-linux-processus.html
2) It's a residual lock
A lock is generally an empty file or one that contains the PID of the process that created it. Deleting a lock simply involves removing this file. The path to this lock is specified in the error message. Thus, you can delete it, for example, with the command:
Then Chromium should launch correctly.
Good luck.
In theory, it is supposed to unlock when you close Chromium. However, if you exited Chromium improperly or it crashed, a residual lock might still exist in your profile.
In this case, Chromium asks you to check whether the lock is warranted (in other words, to check that you don't already have an instance of Chromium running). Each process (each task) is identified by a PID (process identifier), which is an integer. Chromium suspects that process 2108 is another instance of Chromium and therefore refuses to launch.
There are two possibilities:
1) Either Chromium is indeed already running, and it's normal for it to refuse to launch again
2) Or a residual lock is blocking everything, and you need to delete that lock.
Start by opening a terminal:
http://doc.ubuntu-fr.org/terminal
1) Chromium is already running!
You can check if Chromium is running by looking at the running processes, for example with the command:
ps aux | grep chromium
If a line appears with the value 2108, it's likely that an instance of Chromium is already in the process of launching, so the warning from Chromium is justified. You can then decide whether to kill this process or not:
kill -9 2108
For more details:
http://www.mistra.fr/tutoriel-linux-processus.html
2) It's a residual lock
A lock is generally an empty file or one that contains the PID of the process that created it. Deleting a lock simply involves removing this file. The path to this lock is specified in the error message. Thus, you can delete it, for example, with the command:
rm /home/andre/.config/chromium/SingletonLock
Then Chromium should launch correctly.
Good luck.
Thank you very much for your knowledge and availability.
Great, the second solution worked!