Issue 367048 in chromium: Cannot start chrome after changing hostname

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: OS-Linux Type-Bug Pri-2 Cr-UI-Browser-Profiles

New issue 367048 by primi...@chromium.org: Cannot start chrome after
changing hostname
http://code.google.com/p/chromium/issues/detail?id=367048

Chrome Version : 36.0.1951.5
OS Version: Ubuntu 12.04

What steps will reproduce the problem?
1. Change the hostname of the machine.
2. Reboot
3. Start chrome

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




--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Status: Started

Comment #3 on issue 367048 by ma...@chromium.org: Cannot start chrome after
changing hostname
http://code.google.com/p/chromium/issues/detail?id=367048

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #4 on issue 367048 by bugdro...@chromium.org: Cannot start chrome
after changing hostname
http://code.google.com/p/chromium/issues/detail?id=367048#c4

The following revision refers to this bug:

https://chromium.googlesource.com/chromium/src.git/+/947004dd444068ea03e24441fed34e038c938d59

commit 947004dd444068ea03e24441fed34e038c938d59
Author: ma...@chromium.org
<ma...@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

[chro...@googlecode.com]

Comment #5 on issue 367048 by bugdro...@chromium.org: Cannot start chrome
after changing hostname
http://code.google.com/p/chromium/issues/detail?id=367048#c5

------------------------------------------------------------------
r268793 | ma...@chromium.org | 2014-05-07T15:59:02.771557Z

Changed paths:
M
http://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

-----------------------------------------------------------------

[chro...@googlecode.com]

Updates:
Status: Fixed

Comment #6 on issue 367048 by ma...@chromium.org: Cannot start chrome after
changing hostname

http://code.google.com/p/chromium/issues/detail?id=367048

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #8 on issue 367048 by mihalcea...@gmail.com: Cannot start chrome

after changing hostname
http://code.google.com/p/chromium/issues/detail?id=367048

Quick fix:
rm -rf .config/google-chrome/Singleton*

[chro...@googlecode.com]

Comment #9 on issue 367048 by mihalcea...@gmail.com: Cannot start chrome

after changing hostname
http://code.google.com/p/chromium/issues/detail?id=367048

You could also use:
rm -rf ~/.config/google-chrome/Singleton*

[chro...@googlecode.com]

Comment #10 on issue 367048 by FranckJu...@gmail.com: Cannot start chrome

after changing hostname
http://code.google.com/p/chromium/issues/detail?id=367048

rm -rf ~/.config/chromium/Singleton*

is working for me.

thanks !