New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 783737 link

Starred by 3 users

Issue metadata

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

Blocking:
issue 822035



Sign in to add a comment

Inhibit screensaver when using Google Hangouts

Reported by orsch...@gmail.com, Nov 10 2017

Issue description

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

Steps to reproduce the problem:
1. Start a Hangouts call in a new browser tab https://hangouts.google.com/hangouts/_...
2. Don't move your mouse

What is the expected behavior?
I expected Chrome to inhibit the screensaver (dim & turn off screen after inactivity). This feature is already present when watching videos.

What went wrong?
Instead, my screen dimmed after a while and then ultimately turned off while being on the Hangouts call.

I have to constantly move the mouse for this to not happen.

Did this work before? N/A 

Chrome version: 62.0.3202.89  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 27.0 r0

I tested this on Chrome 62 and Ubuntu 17.10.
 
Components: Blink>WakeLock
Labels: Needs-Triage-M62
Cc: krajshree@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Ubuntu 14.04 using chrome stable #62.0.3202.89 and latest dev #64.0.3260.2

Following are the steps followed to reproduce the issue.
------------
1. Started a Hangouts call in a new browser tab https://hangouts.google.com
2. Didn't move the mouse.
3. Observed that chrome did not dimm out and turn off while being on the Hangouts call.

orschiro@ - Could you please check the issue on latest dev #64.0.3260.2 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!
		

Comment 4 by orsch...@gmail.com, Nov 14 2017

Dear krajshree,

Just tried on dev  64.0.3260.2 on Ubuntu 18.04 but yes it dims after a while of not moving the mouse. I followed exactly your steps and used a new profile.

What else can I try?
Project Member

Comment 5 by sheriffbot@chromium.org, Nov 14 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by scheib@chromium.org, Nov 15 2017

Components: -Blink>WakeLock Blink>Media
I believe Media is what should be keeping the screen unlocked when an Hangouts call is active.
Labels: TE-NeedsTriageFromMTV
Unable to reproduce this issue on Ubuntu 14.04 and this issue may reproduce on Ubuntu 17.10 and 18.4 as per comment #0 and 4 which are not available here.
Hence, requesting MTV team to look into this issue for further triage.

Thank you..!!

Comment 8 by orsch...@gmail.com, Nov 16 2017

Requesting more Ubuntu people to reproduce:

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732694
Master bug for Ubuntu: https://launchpad.net/bugs/1697373. This is caused by xwayland not supporting DPMS, and chromium skipping the power saving block if DPMS is not supported.
And I confirm that in an X11 session, screen dimming/blanking inhibit works as expected in chromium. It's a wayland-specific problem.

Comment 11 by orsch...@gmail.com, Nov 17 2017

> It's a wayland-specific problem.

Oh true, I haven't come to think it's a Wayland problem! Indeed, I had tested all this under Wayland. Hence, can confirm that only the Ubuntu Wayland session seems to be affected. Sadly, Wayland is the default on Ubuntu now.
Components: -Blink>Media Blink>WebRTC
Hangouts uses WebRTC.
Components: -Blink>WebRTC
Removing Blink>WebRTC since this is not WebRTC specific, as per #9 and #10.
The disabling of the power-saving blocking when DPMS is not enabled appears to have been introduced to resolve  bug 111239  , in which power-saving blocking was causing DPMS to be re-enabled even if it had been manually disabled. The root cause of that problem seems to have been a KDE bug: https://bugs.kde.org/show_bug.cgi?id=295164 . The KDE bug has been fixed for a long time (since the end of 2012), so I wonder if this workaround (which is now causing problems on Wayland) is still necessary?
Components: Internals>Media>Video
Cc: dalecur...@chromium.org
Status: Untriaged (was: Unconfirmed)
dale, this bug is wayland specific bug. It complains systems turns screensaver mode during video playback. I couldn't repro this bug on my Linux device, The original bug was found during Hangout. 
dcan you assign appropriately?
Cc: -dalecur...@chromium.org
Owner: dalecur...@chromium.org
Status: Assigned (was: Untriaged)
give to dale to start ball.
Blocking: 822035
Cc: reve...@chromium.org dalecur...@chromium.org
Owner: ----
Status: Available (was: Assigned)
This is the same as issue 822035.

Sign in to add a comment