Issue metadata
Sign in to add a comment
|
voice search.. You are not connected to the Internet
Reported by
vus...@gmail.com,
May 30 2018
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux aarch64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/66.0.3359.181 Chrome/66.0.3359.181 Safari/537.36 Example URL: voice search icon in new tab Steps to reproduce the problem: 1. browser open 2. search icon click 3. message : You are not connected to the Internet What is the expected behavior? What went wrong? Web surfing works well quickly. Nvidia TX2 28.2(aarch64) Raspberry PI works.. why does TX2 not work? Did this work before? Yes Chrome version: 66.0.3359.181 Channel: n/a OS Version: NVIDIA TX2 28.2 aarch64 Flash Version:
,
May 30 2018
Can you send a view or something showing that you are connected to the internet and its only voice search that's not working? Best yet, open a web page open, open a new tab, and open another new tab. In one new tab, go to about:net-internals. Then switch to the tab with the web page and click a link. (This will show the network is active.) Then go to the other new tab and click on the voice search icon. Witness the error message. Go back to the tab with about:net-internals and click on the arrow in the top-right to stop collecting network data. Save that network data and upload it to this bug.
,
May 31 2018
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
,
May 31 2018
attach the file. help me. thanks.
,
May 31 2018
please explain in detail.
,
May 31 2018
,
May 31 2018
Looks like we're getting an ERR_SPDY_PROTOCOL_ERROR from the upstream server. Not sure if H2 is expected instead of QUIC.
,
May 31 2018
What can I do? Help.
,
May 31 2018
I tried it on another desktop with ubuntu 16.04 installed, but the same thing happened.
,
May 31 2018
It is expected to be an API-Key problem of chrome browser. It worked well for two years until a few days ago. https://www.google.com/speech-api/full-duplex/v1/down?key=AIzaSyDGQzx0c0ptZVDriLi9Wblo2voeLnmPq-o Can not I use the Speech API in chrome?
,
May 31 2018
The log attached to comment #5 shows that Chrome receives a RST_STREAM with error code INTERNAL_ERROR on stream 1, after receiving a number of data frames. The server in question is google.com. 3514: HTTP2_SESSION www.google.com:443 (DIRECT) Start Time: 2018-05-30 21:05:35.869 t=1845 [st= 0] +HTTP2_SESSION [dt=139+] --> host = "www.google.com:443" --> proxy = "DIRECT" t=1845 [st= 0] HTTP2_SESSION_INITIALIZED --> protocol = "h2" --> source_dependency = 3513 (SOCKET) t=1845 [st= 0] HTTP2_SESSION_SEND_SETTINGS --> settings = ["[id:1 (SETTINGS_HEADER_TABLE_SIZE) value:65536]","[id:3 (SETTINGS_MAX_CONCURRENT_STREAMS) value:1000]","[id:4 (SETTINGS_INITIAL_WINDOW_SIZE) value:6291456]"] t=1845 [st= 0] HTTP2_SESSION_UPDATE_RECV_WINDOW --> delta = 15663105 --> window_size = 15728640 t=1846 [st= 1] HTTP2_SESSION_SEND_WINDOW_UPDATE --> delta = 15663105 --> stream_id = 0 t=1847 [st= 2] HTTP2_SESSION_SEND_HEADERS --> exclusive = true --> fin = false --> has_priority = true --> :method: POST :authority: www.google.com :scheme: https :path: /speech-api/full-duplex/v1/up?key=AIzaSyDGQzx0c0ptZVDriLi9Wblo2voeLnmPq-o&pair=ECB221599A038998&output=pb&lang=ko-KR&pFilter=2&maxAlternatives=4&app=chromium&endpoint=1&interim content-type: audio/x-flac; rate=16000 referer: https://www.google.co.kr/ user-agent: Mozilla/5.0 (X11; Linux aarch64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/66.0.3359.181 Chrome/66.0.3359.181 Safari/537.36 accept-encoding: gzip, deflate, br accept-language: en-US,en;q=0.9 --> parent_stream_id = 0 --> source_dependency = 3507 (HTTP_STREAM_JOB) --> stream_id = 1 --> weight = 147 t=1847 [st= 2] HTTP2_SESSION_SEND_DATA --> fin = false --> size = 1251 --> stream_id = 1 t=1848 [st= 3] HTTP2_SESSION_UPDATE_SEND_WINDOW --> delta = -1251 --> window_size = 64284 t=1848 [st= 3] HTTP2_SESSION_SEND_HEADERS --> exclusive = true --> fin = true --> has_priority = true --> :method: GET :authority: www.google.com :scheme: https :path: /speech-api/full-duplex/v1/down?key=AIzaSyDGQzx0c0ptZVDriLi9Wblo2voeLnmPq-o&pair=ECB221599A038998&output=pb user-agent: Mozilla/5.0 (X11; Linux aarch64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/66.0.3359.181 Chrome/66.0.3359.181 Safari/537.36 accept-encoding: gzip, deflate, br accept-language: en-US,en;q=0.9 --> parent_stream_id = 1 --> source_dependency = 3507 (HTTP_STREAM_JOB) --> stream_id = 3 --> weight = 147 t=1896 [st= 51] HTTP2_SESSION_RECV_SETTINGS t=1896 [st= 51] HTTP2_SESSION_SEND_SETTINGS_ACK t=1896 [st= 51] HTTP2_SESSION_RECV_SETTING --> id = "3 (SETTINGS_MAX_CONCURRENT_STREAMS)" --> value = 100 t=1896 [st= 51] HTTP2_SESSION_UPDATE_STREAMS_SEND_WINDOW_SIZE --> delta_window_size = 983041 t=1896 [st= 51] HTTP2_SESSION_RECV_SETTING --> id = "4 (SETTINGS_INITIAL_WINDOW_SIZE)" --> value = 1048576 t=1896 [st= 51] HTTP2_SESSION_RECV_SETTING --> id = "6 (SETTINGS_MAX_HEADER_LIST_SIZE)" --> value = 16384 t=1896 [st= 51] HTTP2_SESSION_RECV_WINDOW_UPDATE --> delta = 983041 --> stream_id = 0 t=1896 [st= 51] HTTP2_SESSION_UPDATE_SEND_WINDOW --> delta = 983041 --> window_size = 1047325 t=1896 [st= 51] HTTP2_SESSION_RECV_SETTINGS_ACK t=1902 [st= 57] HTTP2_SESSION_RECV_HEADERS --> fin = false --> :status: 403 date: Thu, 31 May 2018 01:05:35 GMT content-type: text/html; charset=UTF-8 server: S3 v1.0 content-length: 1798 x-xss-protection: 1; mode=block x-frame-options: SAMEORIGIN alt-svc: hq=":443"; ma=2592000; quic=51303433; quic=51303432; quic=51303431; quic=51303339; quic=51303335,quic=":443"; ma=2592000; v="43,42,41,39,35" --> stream_id = 1 t=1904 [st= 59] HTTP2_SESSION_RECV_DATA --> fin = false --> size = 1380 --> stream_id = 1 t=1904 [st= 59] HTTP2_SESSION_UPDATE_RECV_WINDOW --> delta = -1380 --> window_size = 15727260 t=1905 [st= 60] HTTP2_SESSION_RECV_DATA --> fin = false --> size = 418 --> stream_id = 1 t=1905 [st= 60] HTTP2_SESSION_UPDATE_RECV_WINDOW --> delta = -418 --> window_size = 15726842 t=1905 [st= 60] HTTP2_SESSION_RECV_HEADERS --> fin = false --> :status: 403 date: Thu, 31 May 2018 01:05:35 GMT content-type: text/html; charset=UTF-8 server: S3 v1.0 content-length: 1705 x-xss-protection: 1; mode=block x-frame-options: SAMEORIGIN alt-svc: hq=":443"; ma=2592000; quic=51303433; quic=51303432; quic=51303431; quic=51303339; quic=51303335,quic=":443"; ma=2592000; v="43,42,41,39,35" --> stream_id = 3 t=1907 [st= 62] HTTP2_SESSION_RECV_DATA --> fin = false --> size = 1705 --> stream_id = 3 t=1907 [st= 62] HTTP2_SESSION_UPDATE_RECV_WINDOW --> delta = -1705 --> window_size = 15725137 t=1907 [st= 62] HTTP2_SESSION_RECV_DATA --> fin = true --> size = 0 --> stream_id = 3 t=1907 [st= 62] HTTP2_SESSION_UPDATE_RECV_WINDOW --> delta = 1705 --> window_size = 15726842 t=1907 [st= 62] HTTP2_SESSION_PING --> is_ack = false --> type = "received" --> unique_id = 0 t=1907 [st= 62] HTTP2_SESSION_PING --> is_ack = true --> type = "sent" --> unique_id = 0 t=1907 [st= 62] HTTP2_SESSION_RECV_RST_STREAM --> error_code = "2 (INTERNAL_ERROR)" --> stream_id = 1 t=1908 [st= 63] HTTP2_SESSION_UPDATE_RECV_WINDOW --> delta = 1380 --> window_size = 15728222 t=1908 [st= 63] HTTP2_SESSION_UPDATE_RECV_WINDOW --> delta = 418 --> window_size = 15728640 t=1984 [st=139]
,
May 31 2018
,
Jun 1 2018
As a result of the debugging, I suspect Api-keys. key = AIzaSyDGQzx0c0ptZVDriLi9Wblo2voeLnmPq-o I have replaced it at runtime level as shown below. (http://www.chromium.org/developers/how-tos/api-keys) nvidia @ tegra-ubuntu: / etc $ cat chrome_dev.conf GOOGLE_API_KEY = AIzaSyD6QPO81ZBnN0KPa4nULHrlAgJQsMfp_Zw GOOGLE_DEFAULT_CLIENT_ID = ****************** GOOGLE_DEFAULT_CLIENT_SECRET = ******************* But in chrome: // net-internals, the key does not seem to be replaced. How do I change the keys in my chrome in ubuntu?
,
Jun 1 2018
I tried to change via 'export GOOGLE_API_KEY = "****"' but it is not reflected.
,
Jun 1 2018
Maybe INTERNAL_ERROR is not the most appropriate responce. 403 or such might be better. Filed internal issue 81540591.
,
Jul 2
It seems like the root of the problem is the API keys you are using. The server is refusing your request, this is not a bug in Chrome. Using an official Chrome binary with the API key it ships with should solve your problem. It is possible that your API keys has expired, its rights have been changed, or its quota has been exceeded. Since this is not a problem with Chrome, I'm closing this issue. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by mmenke@chromium.org
, May 30 2018