Fixed
Status Update
No update yet.
Comments
ma...@chromium.org
It's supposed to show a message box, but looks like something got changed and it no longer works (judging by the second log message).
ma...@chromium.org
[Empty comment from Monorail migration]
ma...@chromium.org
[Empty comment from Monorail migration]
bu...@chromium.org
The following revision refers to this bug:
https://chromium.googlesource.com/chromium/src.git/+/947004dd444068ea03e24441fed34e038c938d59
commit 947004dd444068ea03e24441fed34e038c938d59
Author: mattm@chromium.org <mattm@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date: Wed May 07 15:59:02 2014 +0000
SimpleMessageBoxViews: UI message loop does not need to be running on Linux.
Fixes ProcessSingletonDialogLinux not showing a dialog.
BUG=367048
TEST=run "mkdir /tmp/locktest && ln -s fakehost-1234 /tmp/locktest/SingletonLock && chrome --user-data-dir=/tmp/locktest". A dialog should appear allowing you to quit or unlock the profile. If you click quit, /tmp/locktest/SingletonLock file should remain untouched. If you click unlock, chrome should launch normally.
Review URL:https://codereview.chromium.org/261753015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@268793 0039d316-1c4b-4281-b951-d872f2087c98
commit 947004dd444068ea03e24441fed34e038c938d59
Author: mattm@chromium.org <mattm@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date: Wed May 07 15:59:02 2014 +0000
SimpleMessageBoxViews: UI message loop does not need to be running on Linux.
Fixes ProcessSingletonDialogLinux not showing a dialog.
BUG=367048
TEST=run "mkdir /tmp/locktest && ln -s fakehost-1234 /tmp/locktest/SingletonLock && chrome --user-data-dir=/tmp/locktest". A dialog should appear allowing you to quit or unlock the profile. If you click quit, /tmp/locktest/SingletonLock file should remain untouched. If you click unlock, chrome should launch normally.
Review URL:
git-svn-id: svn://
bu...@chromium.org
------------------------------------------------------------------
r268793 | mattm@chromium.org | 2014-05-07T15:59:02.771557Z
Changed paths:
Mhttp://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/views/simple_message_box_views.cc?r1=268793&r2=268792&pathrev=268793
SimpleMessageBoxViews: UI message loop does not need to be running on Linux.
Fixes ProcessSingletonDialogLinux not showing a dialog.
BUG=367048
TEST=run "mkdir /tmp/locktest && ln -s fakehost-1234 /tmp/locktest/SingletonLock && chrome --user-data-dir=/tmp/locktest". A dialog should appear allowing you to quit or unlock the profile. If you click quit, /tmp/locktest/SingletonLock file should remain untouched. If you click unlock, chrome should launch normally.
Review URL:https://codereview.chromium.org/261753015
-----------------------------------------------------------------
r268793 | mattm@chromium.org | 2014-05-07T15:59:02.771557Z
Changed paths:
M
SimpleMessageBoxViews: UI message loop does not need to be running on Linux.
Fixes ProcessSingletonDialogLinux not showing a dialog.
BUG=367048
TEST=run "mkdir /tmp/locktest && ln -s fakehost-1234 /tmp/locktest/SingletonLock && chrome --user-data-dir=/tmp/locktest". A dialog should appear allowing you to quit or unlock the profile. If you click quit, /tmp/locktest/SingletonLock file should remain untouched. If you click unlock, chrome should launch normally.
Review URL:
-----------------------------------------------------------------
pr...@chromium.org
Thanks for the prompt fix!
mi...@gmail.com
[Comment Deleted]
mi...@gmail.com
You could also use:
rm -rf ~/.config/google-chrome/Singleton*
rm -rf ~/.config/google-chrome/Singleton*
[Deleted User] <[Deleted User]>
is...@google.com
This issue was migrated from crbug.com/chromium/367048?no_tracker_redirect=1
[Multiple monorail components: UI>Aura, UI>Browser>Profiles]
[Monorail components added to Component Tags custom field.]
[Multiple monorail components: UI>Aura, UI>Browser>Profiles]
[Monorail components added to Component Tags custom field.]
ad...@gmail.com
It's 10 years later and this is not fixed.
Can confirm that the rm -rf ~/.config/google-chrome/Singleton* fix still works.
le...@gmail.com
Occured today for me. Fixed as above.
co...@gmail.com
Bug is still actual. Tried ten different solutions, only
`rm -rf ~/.config/google-chrome/Singleton*` worked.
`rm -rf ~/.config/google-chrome/Singleton*` worked.
kr...@gmail.com
this bug still valid, happened on me today.
I'm on Google Chrome 126.0.6478.126 (Official Build) (64-bit), Ubuntu 22.04.
rm -rf ~/.config/google-chrome/Singleton* fixes the issue, chrome able to start, profile data seems intact.
hc...@google.com
I also just encountered this. Since this bug is so old and mattm@ appears to have moved teams, I've filed
kr...@google.com
Same so +1 the new bug/ticket.
sv...@st6.io
+1 Same thing, Fixed it on ubuntu 22.04 with
rm -rf ~/snap/chromium/common/chromium/Singleton*
ja...@gmail.com
Bug still exists on Ubuntu 24.04 LTS, Chrome Version 136.0.7103.92 (Official Build) (64-bit). Fixed with
rm -rf ~/.config/google-chrome/Singleton*
Description
Chrome Version : 36.0.1951.5
OS Version: Ubuntu 12.04
What steps will reproduce the problem?
What is the expected result?
Chrome should start as usual.
What happens instead of that?
[11959:11959:0425/103243:ERROR:process_singleton_linux.cc(306)] The profile appears to be in use by another Google Chrome process (16053) on another computer (primiano1.lon.corp.google.com). Chrome has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chrome.
[11959:11959:0425/103243:ERROR:simple_message_box_views.cc(204)] Unable to show a dialog outside the UI thread message loop: Google Chrome - The profile appears to be in use by another Google Chrome process (16053) on another computer (primiano1.lon.corp.google.com). Chrome has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chrome.
This is a pretty frustrating experience, as there is no indication on how to unlock the profile.
I had to figure out myself through code-search that I had to remove the Singleton* files under .config/google-chrome-unstable. I'm pretty sure that we can do a better job (for instance, expanding a bit the error message string)
Also please note that I got the message only by trying to start Chrome from the command line. The end-user experience is even worse, as clicking on the chrome logo in the taskbar just ends up doing nothing.
Can we make this a msgbox at least?
UserAgentString: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/36.0.1951.5 Safari/537.36