New issue
Advanced search Search tips

Issue 871633 link

Starred by 6 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Cannot log into Hangouts using the extension

Reported by adefa...@gmail.com, Aug 7

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.23 Safari/537.36

Steps to reproduce the problem:
1. Start Chrome Browswer, notice that Hangouts is not connected
2. Open Hangouts extensions, you see essentially an empty screen with "Sign in to Chrome to get started".
3. Click Sign in and a browser window is popped up which is totally empty with the URL of https://hangouts.google.com/webchat/blank?undefined&pli=1

What is the expected behavior?
That I would get signed into Hangouts

What went wrong?
Presented an empty web page with no way to sign in.

Did this work before? Yes The one previous to this version - Don't remember the number but it was 68.x .<something>

Chrome version: 69.0.3497.23  Channel: beta
OS Version: Ubuntu 8.4
Flash Version: 

This morning I noticed that I was not logged into the Hangouts extension on my Ubuntu 18.04 desktop. It said to sign in so I clicked the button to sign in. Another Chrome window popped up with the URL of https://hangouts.google.com/webchat/blank?undefined&pli=1 and indeed the page was blank. No way to login!

Of course I'm signed into my Chrome browser windows already and I tried removing and re-adding the Chrome extension for Hangouts but it still fails the same way. Hangouts works on my Android phone.

https://hangouts.google.com works and I can make phone calls through https://voice.google.com. It's just the Hangouts extension that fails to work.

Oh and BTW, can we get rid of the menu that is in Ubuntu 18.04 for Hangouts. I have to click on it and the only selection is "Google Hangouts". This causes an extra click. In the past just clicking on the Hangouts icon in the notification area would just bring up the Hangouts extension window. As I always say, you gain nothing by providing the user with a menu with only one selection! If that's the case, then just do the selection when the user clicks on the menu option!
 
Labels: Needs-Triage-M69 Needs-Bisect
Labels: Triaged-ET Needs-Feedback
Unable to reproduce the issue reported version #69.0.3497.23 and on latest chrome #70.0.3514.0 on Ubuntu 17.10, by following below steps.

Steps:
=====
1.Launched chrome.
2.Navigated to chrome://apps
3.Added extension Hangouts/
4.Clicked sign in on browser pop up which navigated to sign in page, but did not observe any empty page.

Attached screencast for reference.
@Reporter: Could you please review the attached screen-cast and confirm if anything being missed here and request you to retry this issue with fresh profile without any extensions/apps or reset all the flags and let us know if issue still persists.

Thanks.!
871633.webm
10.6 MB View Download
Well it fails for me. I've included a screencast too. I have the Hangouts extension already installed and I'm already signed in to Google Chrome but when I start the extension it asks me to sign in and presents me a blank page.
Screencast_00000.mp4
2.8 MB View Download
Project Member

Comment 4 by sheriffbot@chromium.org, Aug 7

Cc: swarnasree.mukkala@chromium.org
Labels: -Needs-Feedback
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
I have the same issue, been there for a few weeks now. My issue is on the windows platform with M70.
Components: Platform>Extensions
Labels: Needs-Feedback
As per comment#3 unable to repro the issue by signing into the google and adding hangouts extension, on reported version #69.0.3497.23 using Ubuntu 17.10. Could anyone from Platform>Extensions please have a look into the issue.

Attached screencast for reference.

Thanks.!
871633(1).webm
7.1 MB View Download
@ I coudn't reproduce the issue as well. 

Linux 69.0.3497.23 HP Z440 desktop version. OS: Debian Rodete. 
I think there's a good chance this is the same bug as crbug.com/875020. I'm going to hold off duping these bugs because 875020 is restricted, just FYI for folks who may work on this.
Sorry I don't have permissions to view that link...
Project Member

Comment 10 by sheriffbot@chromium.org, Aug 18

Labels: -Needs-Feedback
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
Cc: kkaluri@chromium.org
Labels: TE-NeedsTriageFromHYD
Retried to reproduce the issue on Windows 10 and Ubuntu 17.10 and unable to reproduce the issue by using Hangouts extension(version 2018.515.419.1).
As per comments #2 and #6, as this issue is not reproduced at TE end, CC'ing kkaluri@ from RVG Issue 875020 for further action on this issue and adding 'TE-NeedsTriageFromHYD' label.

Thanks..
Components: Blink>Paint
Owner: schenney@chromium.org
adefaria@gmail.com, can you post your about:gpu info here? To do this, type about:gpu in the url bar, then click the "copy all" button, then paste the result here.

Stephen, can you track the tracking down of this on our side?
Attached
gpu.info
127 KB Download
Cc: schenney@chromium.org
Components: -UI Internals>GPU>Scheduling
NextAction: 2018-09-10
Owner: ----
I can nag people. Scheduling seems the most likely cause, but maybe it's something else.

I shouldn't own it until it is confirmed and reproduced. I track it anyway because it remains Unconfirmed and Blink>Paint is a component.
Labels: -Needs-Bisect -TE-NeedsTriageFromHYD
Still we are unable to reproduce the issue on debian Rodate using chrome reported version-69.0.3497.23 & latest beta-69.0.3497.42 as per steps in C#0 & video in C#3 & mentioned the same in C#2,6 & 11.

Tried different cases:
--------------------
Case 1. Launch chrome, install extension & click on hangouts extension , click on sign in button & able to sign in successfully.
Case 2. Once user sign in to chrome browser , automatically google hangout extension also gets signed in (if extension is already added).
Case 3. If user is not signed in to chrome browser, then also user able to sign in google hangouts successfully without any issue(if extension is already added).

Hence removing Needs-Bisect & TE-NeedsTriageFromHYD labels for now. Please add if required.
Thanks..!



Labels: Needs-Feedback
adefaria@gmail.com: you are using nouveour driver, which is not very stable. Chrome only allows it because those who install it usually are adventurous and know their way around.

Can you try running Chrome with --disable-gpu and see if the issue goes away? If yes, then likely it's a nouveour driver issue.
Nice try and I was hopeful but running with --disable-gpu doesn't change anything :-(
Project Member

Comment 18 by sheriffbot@chromium.org, Sep 1

Cc: zmo@chromium.org
Labels: -Needs-Feedback
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
Owner: rdevlin....@chromium.org
Status: Assigned (was: Unconfirmed)
Assigning to Devlin for extension triage.
Well miracles of miracles - this morning Chrome wanted to be relaunched and wham, the extension now works. I did not capture the previous version but the new version is Version 69.0.3497.81 (Official Build) unknown (64-bit)
Cc: rdevlin....@chromium.org
Owner: jawag@chromium.org
This looks like it's just a bug in the hangouts extension - it opens a window to https://hangouts.google.com/webchat/blank?undefined&pli=1, which is, in fact, a blank page.  So it doesn't look like it's a painting issue in Chrome, or something in the Chrome Extensions system.

jawag@, can you route this to the proper hangouts folks?
Issue 875020 has been merged into this issue.
The NextAction date has arrived: 2018-09-10
NextAction: ----
I've flagged this to the Hangouts team and they're taking a look.
Please do not miss my post which says that this is working fine for me now with Version 69.0.3497.81 of Chrome (Beta) and Version 2018.515.419.1 of the extension.
@adefaria Yep, thanks for making sure we saw it! :)

We're just making sure our bases are covered, since if you experienced this, there's a decent chance others have as well.  If it's already fixed for everyone, great! - but we should double-check just to make sure.
Unfortunately I am still seeing the issue with Chrome 71.0.3549.0 (windows / mac) and Hangouts 2018.515.419.1

Sign in to add a comment