RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1704378 - Bring in disable-screenshield from RHEL7
Summary: Bring in disable-screenshield from RHEL7
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-shell
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Florian Müllner
QA Contact: Desktop QE
Lucie Vařáková
URL:
Whiteboard:
: 1704379 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-29 15:53 UTC by Matthias Clasen
Modified: 2020-11-14 10:50 UTC (History)
6 users (show)

Fixed In Version: gnome-shell-extension-3.32.1-3.el8.noarch.rpm
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 22:14:04 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3553 0 None None None 2019-11-05 22:14:18 UTC

Description Matthias Clasen 2019-04-29 15:53:23 UTC 
We added a way to disable the screenshield in 7.7.
That needs to be available in RHEL8 too.
Comment 1 Matthias Clasen 2019-05-21 15:16:06 UTC 
*** Bug 1704379 has been marked as a duplicate of this bug. ***
Comment 2 Allan Day 2019-05-21 17:12:03 UTC 
The origin of this issue is that I speculated that some RHEL users who are used to a traditional Linux/UNIX desktop (primarily GNOME 2) might find the GNOME 3 lock screen to be uncomfortable - particularly the swipe action to remove the shield, and the two screens (shield then unlock screen).

The disable screenshield option that's in RHEL 7.7 uses an extension [1]. Florian can correct me if I'm wrong, but the impact of this seems to be limited: all it does is prevent the screen shield from activating in situations where the screen has blanked, but it hasn't locked. In many cases, it won't have any effect. In others, it will have some effect, but won't prevent users from encountering the screen shield. It also won't be applicable for organisations that require screen locking to be used.

To resolve the issue that I originally predicted, we'd need a way to avoid aspects of the screen shield while still allowing screens to be locked.

[1] https://extensions.gnome.org/extension/672/disable-screen-shield/
Comment 13 errata-xmlrpc 2019-11-05 22:14:04 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3553
Note You need to log in before you can comment on or make changes to this bug.