Linux: Cannot relaunch Chrome with remote debugging enabled.

[JanPolasek]

On my Mint 15, when I try to launch Live Preview, Brackets shows dialog window that I have to relaunch Chrome, so I click relaunch, but nothing is happening and terminal shows up this error:

google-chrome: no process found

I think it's because process name of Chrome is 'chrome' and not 'google-chrome'

[thefirstofthe300]

This is a problem that I have also been having but couldn't fix because I really don't know C++ yet.

The way I have worked around this problem is killing chrome pkill chrome and using Live Preview to start Chrome. Once Chrome is running again, you can use it however you want.

The issue for the bug I filed way back when is #3992. This is what you are referring to right?

If you have C++ knowledge, you could probably take a whack at implementing the suggestion @redmunds had.

[JanPolasek]

Yes, #3992 is the same bug, I didn't know it was filled, I couldn't find it anywhere.

killing Chrome and launching it with live preview works, but if I accidentally close live preview chrome windows, I have to kill all my ~50 tabs and that isn't nice.

Sadly, I don't have C++ knowledge, I'm just a web developer.

[thefirstofthe300]

I wouldn't expect you to be able to find the issue because I filed it a
couple months ago and it was closed before Linux support really got rolling.

On Sat, Aug 10, 2013 at 3:07 PM, JanPolasek notifications@github.comwrote:

Yes, #3992 #3992 is the same
bug, I didn't know it was filled, I couldn't find it anywhere.

killing Chrome and launching it with live preview works, but if I
accidentally close live preview chrome windows, I have to kill all my ~50
tabs and that isn't nice.

Sadly, I don't have C++ knowledge, I'm just a web developer.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4740#issuecomment-22448377
.

Danny Seymour
dannyseeless@gmail.com

[hollec]

I have the same problem in Ubuntu 13.04. Without actually testing this, I believe a minor modification needs to be made to appshell_extensions_gtk.cpp in brackets-shell. In CloseLiveBrowser, the line

system("killall -9 google-chrome &");

most likely needs to be changed to

system("killall -9 chrome &");

The actual executable is still google-chrome, so GetPathToLiveBrowser may not need to be touched.

[thefirstofthe300]

I can confirm that half of the issue is fixed with @hollec's suggestion.
However, Chrome is not wanting to launch afterwards.

On Sun, Aug 11, 2013 at 3:31 PM, Chris notifications@github.com wrote:

I have the same problem in Ubuntu 13.04. Without actually testing this, I
believe a minor modification needs to be made to
appshell_extensions_gtk.cpp in brackets-shellhttps://github.com/adobe/brackets-shell.
In CloseLiveBrowser, the line

system("killall -9 google-chrome &");

most likely needs to be changed to

system("killall -9 chrome &");

The actual executable is still google-chrome, so _GetPathToLiveBrowser_may not need to be touched.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4740#issuecomment-22466841
.

Danny Seymour
dannyseeless@gmail.com

[jasonsanjose]

The original bug reported here is fixed by adobe/brackets-shell#317 (thanks to @macie). A similar change needs to happen in CloseLiveBrowser to close a running instance of the browser if debugging isn't enabled.