Browser refuses to start when using an account with 2 factor authentication
Reported by
ken.w.h...@gmail.com,
Jan 4 2018
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. Delete ~/.config/chromium if browser wont start 2. Install fresh copy of chromium 3. login to browser with 2 factor auth enabled gmail account 4. close and reopen browser (fails to reopen) What is the expected behavior? Browser should be able to at least display "aw snap" and fail but it wont even do that. What went wrong? It continues to stay on the process table and never displays a window frame. Did this work before? N/A Chrome version: 61.0.3163.100 Channel: stable OS Version: Red Hat Enterprise Linux Server release 6.9 Flash Version: disabled The problem does not happen when I use the same steps on an account without two factor authentication. $ ps auxww | grep chrom user1 6689 2.9 0.0 910948 63316 ? Sl 11:09 0:01 /opt/chromium-browser/chromium-browser --enable-plugins --enable-extensions --enable-user-scripts --enable-printing --enable-sync --auto-ssl-client-auth user1 6696 0.0 0.0 6224 564 ? S 11:09 0:00 /opt/chromium-browser/chrome-sandbox /opt/chromium-browser/chromium-browser --type=zygote user1 6697 0.0 0.0 475224 26056 ? S 11:09 0:00 /opt/chromium-browser/chromium-browser --type=zygote user1 6699 0.0 0.0 475224 7612 ? S 11:09 0:00 /opt/chromium-browser/chromium-browser --type=zygote user1 6790 0.4 0.0 536060 45348 ? Sl 11:09 0:00 /opt/chromium-browser/chromium-browser --type=gpu-process --field-trial-handle=14339888317805519058,3453384656664272865,131072 --supports-dual-gpus=false --gpu-driver-bug-workarounds=9,23,27,50,59,63,73,84,95,97,104 --disable-gl-extensions=GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent --disable-accelerated-video-decode --gpu-vendor-id=0x10de --gpu-device-id=0x13f1 --gpu-driver-vendor=Nvidia --gpu-driver-version=384.59 --gpu-driver-date --service-request-channel-token=CEC287C823A802F7B4025993CB7F3FD9
,
Jun 28 2018
Crash report not available. Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested. |
||
►
Sign in to add a comment |
||
Comment 1 by dtapu...@chromium.org
, Jun 8 2018