Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1764311

Summary:	When something stops inhibiting screen blanking, don't directly blank the screen
Product:	[Fedora] Fedora	Reporter:	taaem
Component:	mutter	Assignee:	Florian Müllner <fmuellner>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	fmuellner, gnome-sig, jadahl, otaylor, philip.wyett, walters
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	mutter-3.34.1-9.fc31 mutter-3.34.1-11.fc31	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-15 03:01:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description taaem 2019-10-22 17:43:10 UTC

Description of problem:
When something stops inhibiting screen blanking, don't directly blank the screen

The scenario: You're watching a movie or a video on eg. YouTube, the video is over and auto play kicks in. Since the last user interaction is longer ago then the configured screen blanking timeout, the screen directly starts to turn off, before the next video can start and I have to log in again. This may be bothering for a lot of people.

Version-Release number of selected component (if applicable):
3.34.1

How reproducible:
always

Steps to Reproduce:
1. Watch a video that is longer than the timeout for the screen blanking
2. wait until the video is over

Actual results:
The screen directly turns off

Expected results:
The screen blanking timeout should start at that time.

Additional info:
This bug already has a fix but it didn't went into 3.34.1 but it may be an improvement, that people would appreciate for Fedora 31.
The related merge request is: https://gitlab.gnome.org/GNOME/mutter/merge_requests/836

Comment 1 Fedora Update System 2019-11-11 16:14:10 UTC

FEDORA-2019-c9e297f88f has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-c9e297f88f

Comment 2 Fedora Update System 2019-11-12 11:01:53 UTC

FEDORA-2019-4c65e7710a has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-4c65e7710a

Comment 3 Fedora Update System 2019-11-13 04:56:37 UTC

gnome-shell-3.34.1-3.fc31, mutter-3.34.1-9.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-c9e297f88f

Comment 4 Fedora Update System 2019-11-13 10:52:27 UTC

gnome-shell-3.34.1-4.fc31, mutter-3.34.1-11.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-4c65e7710a

Comment 5 Fedora Update System 2019-11-15 03:01:52 UTC

gnome-shell-3.34.1-4.fc31, mutter-3.34.1-11.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.