So It crash's Wifi when you click on the bottom right settings bar when you signing in and its loading then the screen will go clack then on and the Wifi does not work.
Reported by
gome...@kmsd.edu,
Nov 29
|
||||||||
Issue description<b>Chrome Version: <From about:version: Google Chrome x.x.x.x></b> <b>Chrome OS Version: <From about:version: Platform x.x.x.x></b> <b>Chrome OS Platform: <Make/model of computer running Chrome OS></b> <b>Network info: <network, encryption type, router model (if known)></b> Please specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1)You can fix this by changeing the bottem bar and that will fix it (2) (3) Expected Result: I think this is all I have two say but (Please bring back the old keyboard for the command finder (Ctrl alt /-?) That was why better. Actual Result: How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) What is the impact to the user, and is there a workaround? If so, what is it? Please provide any additional information below. Attach a screen shot or log if possible. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Nov 30
I believe that the reporter here is referring to an unknown action relating to attempting to open an unspecified settings panel while either the desktop or a web page in Chrome is loading, in either an unknown version of Chrome or an unknown Chrome OS version, causing the WLAN driver to abort. I recommend this issue be closed, as it seems to be isolated. Furthermore, from the vague description, I would bet that the issue stems from faulty drivers for the WLAN radio, a corrupt WPA_supplicant or what could be one of 100 different issues. Since this issue is likely tied to faulty hardware or corrupt or outdated drivers (in my experience 90% of the time the cause for hardware anomalies), it is off topic. However, if a hardware failure is caused by a function of the browser, that is concerning, since a browser should not be directly accessing a raw device, it could be signs of a buffer overflow. But it sounds more like it's an issue with opening the system settings, which has been a bug prevalent in the base linux kernel for many years. The kernel's interaction with a small number of certain WLAN radios triggers an unknown event which causes wpa_supplicant to terminate and require the adapter be brought down, wpa_supplicant restarted (or force terminated as it occasionally hangs) and then the WLAN radio brought back up. Enabling promiscuous mode seems to increase the occurrence. Still it's isolated and driver related, not relevant here.
,
Nov 30
Can you add the old command keyboard back that's better?
,
Nov 30
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 30
Still waiting on the crash from chrome://crashes
,
Nov 30
I don't know what you mean?
,
Nov 30
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 30
You indicated there was a crash and we'd like some information on the crash. We require the server crash id from chrome://crashes. (you can type that in the URL bar).
,
Nov 30
,
Nov 30
Forget about the glitch, but can you guys send just my Chromebook an update so I have the old command finder where it was a keyboard because I like that one so much more if so please respond.
,
Nov 30
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 15
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by dtapu...@chromium.org
, Nov 29