Opened 7 years ago

Last modified 11 months ago

#11214 needs_information defect

Gmail talkgadget/hangouts/chat infinite loop

Reported by: cypherpunks Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-usability-website
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Version: Tor Browser Bundle
*please relocate to appropriate thread if incorrect*

Gmail allows for two types of chat: by default, hangouts, and by choice, legacy chat. These operate in a frame on the lower left of Gmail. Legacy chat works, but reverting to legacy chat from hangouts is impossible from Tor Browser Bundle, where an infinite loop interferes.

  1. Gmail load attempted with restrictive NoScript settings. Options appear: loosen restrictions, or use HTML only.
  2. is whitelisted in NoScript, as well as (optionally) some of the following domains:
  3. Page is reloaded. The following error message appears in the lower left chat frame: "Something's not right. We're having trouble connecting to Google. We'll keep trying...\n This may be caused by network or proxy issues. <a href="">Learn more</a>.
  4. is whitelisted in NoScript, as recommended on the linked support page. Gmail is refreshed.

Infinite loop:

  1. Hangouts loads, with contact list visible. Within seconds, it disappears and is replaced with a Sign In button.
  2. The Sign In button is clicked. A pop-up appears with a log-in page from domain Password is entered; user signs in. Page declares success, instructs user to close pop-up and refresh Gmail.
  3. Go to step 5.

This bug prevents users from being able to use Google chat at all, since reverting to legacy chat requires accessing the main menu in talkgadget/hangouts.

Tried many combinations of NoScript whitelists. None works.

Child Tickets

Change History (10)

comment:1 Changed 7 years ago by cypherpunks

Keywords: hangouts added

comment:2 Changed 7 years ago by cypherpunks

This bug was mentioned on
Copied below

On February 19th, 2014 Anonymous said:

GMail is broken, when you allow in NoScript. When you login and GMail loads GTalk / Hangouts after showing the main window with your mails, the site redirect you to the login page and asks for your password again. This is an infinit loop. When you block the address it works fine. I found a similar behavior on eBay. Seems like a bug. This is very annoying. I would like to report this, but I don't understand the bug tracker system.

On February 24th, 2014 arma said:

Could be an issue with HTTPS-Everywhere, or could be an issue with Tor Browser's changes.

You might ask on IRC if anybody can help you use the bugtracker.

Version 0, edited 7 years ago by cypherpunks (next)

comment:3 Changed 7 years ago by gk

Keywords: tbb-usability-website added; gmail google bundle hangouts removed

comment:4 Changed 7 years ago by cypherpunks

Last edited 7 years ago by cypherpunks (previous) (diff)

comment:5 Changed 6 years ago by Illmarinen

I encountered this bug and found this Ticket. Decided to try and help further diagnose / reproduce it since it has not been touched for a while and appears to still be occurring.


TOR 3.6.2
Firefox 24.6.0

HTTPEverywhere both Enabled and Disabled.

NoScript Temporarily Allow (in this order and with page refreshes):

Mail visible -- expected
Problem message -- expected

Infinite automatic login attempt loop -- color-changing ball
Problem message -- expected

Login, able to open contact search box, however no further progress
Problem message -- expected.

No change.

Reproduces reported bug.
Left pane falls back to a login prompt to manually login within few seconds.
Manually logging in indicates success and that the page can be refreshed.
Refreshing page reproduces reported bug; infinite loop.

Original message indicates causes the issue, but my order narrows it down to

I hope this helps.

comment:6 Changed 6 years ago by erinn

Keywords: needs-triage added

comment:7 Changed 6 years ago by cypherpunks

Similiar problem reported here. It mentions google is blocking proxies.!topic/hangouts/YDP7W2dwhQk

Therfore I can conclude google is blocking tor exit nodes

comment:8 Changed 6 years ago by cypherpunks

Component: Tor bundles/installationTor Browser
Owner: changed from erinn to tbb-team

comment:9 Changed 3 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:10 Changed 11 months ago by gk

Keywords: needs-triage removed
Status: newneeds_information

Is that still an issue with Tor Browser 9? If so, please provide steps to reproduce.

Note: See TracTickets for help on using tickets.