Browser closes when trying to log in to chrome
Reported by
igorme...@gmail.com,
May 29 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 Steps to reproduce the problem: 1 - After new installation of Chrome. 2 - Using network firewall with authentication. 3 - Open any website to perform the authentication request on the network firewall. 4 - Click with the button of the doll, to try to authenticate google. 5 - Click the button to log in to chrome. 6 - At this point the browser closes. What is the expected behavior? Open the screen to log in to synchronize the user data for this machine. What went wrong? As you contact the personnel responsible for the firewall, chrome is trying to access something from the internet without passing authentication on the firewall. Crashed report ID: 0 How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? N/A Chrome version: Google Chrome 58.0.3029.110 (Versão oficial) 64 bits Revisão 691bdb490962d4e6ae7f25c6ab1fdd0faaf19cd0-refs/branch-heads/3029@{#830} SO Linux JavaScript V8 5.8.283.38 Flash 24.0.0.189 internal-not-yet-present Agente do usuário Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Linha de comando /usr/bin/google-chrome-stable --flag-switches-begin --flag-switches-end Caminho do executável /opt/google/chrome/google-chrome Caminho de perfil /home/usuario/.config/google-chrome/Default Channel: stable OS Version: Linux S0549 4.9.0-3-amd64 #1 SMP Debian 4.9.25-1 (2017-05-02) x86_64 GNU/Linux Flash Version: Shockwave Flash 22.0 r0 I do not know which version stopped working because I was using it normally and syncing everything. But after I formatted the machine, with that informed version, I noticed the problem. I talked to other colleagues, and also the staff responsible for the firewall, and their machines also had the problem after leaving the user and trying to authenticate in the latest version. Not to mention that in my other machine with Windows 10 also occurred the problem.
,
May 30 2017
,
May 30 2017
Correct Chrome Version: Chromium 58.0.3029.81 (Developer Build) built on Debian 9.0, running on Debian 9.0 (64-bit) Revision 282d60fedefa2a065674798acbf1af61c127c8b6 OS Linux JavaScript V8 5.8.283.32 Flash 22.0.0.209 /usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36 Command Line /usr/lib/chromium/chromium --show-component-extension-options --ignore-gpu-blacklist --no-default-browser-check --disable-pings --media-router=0 --enable-remote-extensions --ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so --ppapi-flash-version=22.0.0.209 --flag-switches-begin --flag-switches-end Executable Path /usr/lib/chromium/chromium Profile Path /home/usuario/.config/chromium/Default
,
May 31 2017
Unable to reproduce the issue on Ubuntu 14.04 using chrome stable #58.0.3029.110 (Developer Build) Built on Ubuntu. Following are the steps followed to reproduce the issue. ------------ 1. Navigated to a google authenticated site. 2. Clicked on the button to sign into the page. 3. Observed that the page requiring google authentication opened without any issues and did not observe any crash. igormenin@ - Could you please check this issue on chrome stable #58.0.3029.110 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. If possible please provide a sample URL to test the issue. Thanks...!!
,
Aug 1 2017
There is no valid updates happened in the last few months, closing the issue. Feel free to reopen if needed. |
||||
►
Sign in to add a comment |
||||
Comment 1 by igorme...@gmail.com
, May 29 2017