New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 630819 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Cannot run Chrome after update

Reported by reinl...@gmail.com, Jul 23 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0

Steps to reproduce the problem:
1. Run google-chrome
2. Terminal displayed 'Aborted' message

What is the expected behavior?
Chrome should launch properly

What went wrong?
Chrome cannot start

Crashed report ID: No

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? No 

Chrome version: 52.0.2743.82  Channel: stable
OS Version: Mint 17.2 64 bit
Flash Version: Shockwave Flash 11.2 r202

I attached the core file.
 

Comment 1 by reinl...@gmail.com, Jul 23 2016

Output of google-chrome –no-sandbox:

[6044:6044:0722/191940:ERROR:browser_main_loop.cc(231)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the sandbox on.

Aborted

[0722/191940:ERROR:nacl_helper_linux.cc(307)] NaCl helper process running without a sandbox!

Most likely you need to configure your SUID sandbox correctly


Output of google-chrome --enable-logging --v=1:

[4225:4225:0722/182418:VERBOSE1:breakpad_linux.cc(1836)] Breakpad disabled

[1:1:0722/182418:VERBOSE1:zygote_main_linux.cc(600)] ZygoteMain: initializing 2 fork delegates

[1:1:0722/182418:VERBOSE1:nacl_fork_delegate_linux.cc(145)] NaClForkDelegate::Init()

[1:1:0722/182418:VERBOSE1:nacl_fork_delegate_linux.cc(145)] NaClForkDelegate::Init()

[1:1:0722/182418:INFO:systeminfo.cc(82)] Available number of cores: 4

I tried these command options:
--disable-gpu
--disable-extensions
--disable-d3d11
--disable-local-storage
--disable-notifications
--disable-offline-pages
--disable-plugin-power-saver
--disable-plugins-discovery
--disable-sync
--disable-translate
--disable-webgl
--no-experiments

but got 'Aborted' messages again. 

I have also tried reinstalling Chrome and removing ~/.config/google-chrome and still had the same result.
@Developers: No crash-ids are available because chrome crashes way too soon!

same experience, 
ubuntu 14.04 / 64-bit, 
chrome version: 52.0.2743.82
uname: Linux ncc1701u 3.13.0-92-generic #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

attached file is the ~/.config/google-chrome/chrome_debug.log
following: 
> google-chrome --enable-logging --v=1


chrome_debug.log
410 bytes View Download
additional context:

The noted failure is experienced if I login using Ubuntu Default window manager.

google-chrome-stable starts without issue if I select KDE Plasma Workspace option prior to login.


additional:
same chrome version (52.0.2743.82) still works ubuntu 16.04

uname: Linux sys76 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

under the default ubuntu desktop (no KDE Plasma option installed on this machine)


Cc: durga.behera@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Ubuntu 14.04 LTS(Unity) using 52.0.2743.82.Could you please review the screen cast and update the thread accordingly.
630819_July_26.ogv
1.6 MB View Download
Video's audio was just static. From the images, looks like you're requesting the chrome://version tab information, once chrome has started. 

Attempting to start chrome from the command line produces an aborted message without allowing the opportunity to enter 'chrome://version' in the address bar. Indeed, there is never a chrome window created.

Other ideas ?
Labels: Hotlist-ConOps
saw the Needs-Feedback tag. Anything I can do ?

Components: Internals>Installer
I just downloaded Chrome 52.0.2743.116 and it can run on Linux Mint 17.2.
Cc: rnimmagadda@chromium.org
@reinld17: Can we go ahead and close this issue as per the comment #11?

Thank you.
Yes, please. Thanks for fixing this.
Labels: -Needs-Feedback
Status: WontFix (was: Unconfirmed)
Closing this issue as per the comment #13
Fantastic. Much thanks.
How would I take a look at the  delta that fixed  it ?

Sign in to add a comment