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 1980661 - "Screen Lock disabled" notification appears on first login after disabling gdm and notification pop-up.
Summary: "Screen Lock disabled" notification appears on first login after disabling gd...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-shell
Version: 8.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: beta
: ---
Assignee: Florian Müllner
QA Contact: Michal Odehnal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-09 07:36 UTC by Vishal Pakolu
Modified: 2021-11-10 07:30 UTC (History)
5 users (show)

Fixed In Version: gnome-shell-3.32.2-37.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-09 19:34:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Notification. (29.73 KB, image/png)
2021-07-09 07:36 UTC, Vishal Pakolu 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:4381 0 None None None 2021-11-09 19:34:51 UTC

Description Vishal Pakolu 2021-07-09 07:36:31 UTC 
Created attachment 1799887 [details]
Notification.

Description of problem:

"Screen Lock disabled" notification appears on first login after disabling gdm.

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

gnome-shell-3.32.2-20.el8
gdm-3.28.3-34.el8
RHEL 8.3

Also reproducible on :

gnome-shell-3.32.1-14.el8
gdm-3.28.3-29.el8
RHEL 8.2

How reproducible:

Always.

Steps to Reproduce:


1) Configure vnc with either methods based on RHEL release :
--> https://access.redhat.com/solutions/5544351
Or
--> https://access.redhat.com/solutions/966063

2) disable notification popups in GNOME3. (This step is optional)
--> https://access.redhat.com/solutions/4841201

3) Disable gdm :

~~~
# systemctl disable gdm 
~~~

4) Reboot. 

5) Try to connect over configured vnc. 

Following Notification is seen on first login :

"Screen lock is disabled Screen locking requires the GNOME display manager."

Actual results:

Following Notification is seen on first login :

"Screen lock is disabled Screen locking requires the GNOME display manager."

Expected results:

Notification should not be visible after 

Additional info:

Screen-shot attached for notification that is seen >> "Screen lock is disabled Screen locking requires the GNOME display manager."
Comment 1 Florian Müllner 2021-07-09 15:47:21 UTC 
> Notification should not be visible after 

After disabling notifications?

I'm a bit confused, because the summary says that the step to disable notifications is optional.
Comment 2 Florian Müllner 2021-07-12 21:11:01 UTC 
FWIW, I think that this is the issue that was fixed in https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1511 upstream.

However I'll wait for confirmation before adding devel+.
Comment 3 Vishal Pakolu 2021-07-13 11:42:34 UTC 
@Florian :

Sorry for the confusion. The issue is reproducible both with notification pop-up disabled and enabled. 

Also, the issue is reported here upstream > https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2432
Comment 4 Florian Müllner 2021-07-13 11:59:14 UTC 
(In reply to Vishal Pakolu from comment #3)
> @Florian :
> 
> Sorry for the confusion. The issue is reproducible both with notification
> pop-up disabled and enabled. 
> 
> Also, the issue is reported here upstream >
> https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2432

Mmh, I'm still confused. I can backport the fix from that bug, but:

> Following Notification is seen on first login :
>
> "Screen lock is disabled Screen locking requires the GNOME display manager."

That is the expected behavior, with or without that patch. What the upstream fix changes is that the notification is only shown once after disabling GDM, instead of at each login.

Again, I cannot fix anything if I don't know what I'm supposed to fix in the first place.
Comment 5 amit yadav 2021-07-19 04:17:47 UTC 
(In reply to Florian Müllner from comment #4)
> (In reply to Vishal Pakolu from comment #3)
> > @Florian :
> > 
> > Sorry for the confusion. The issue is reproducible both with notification
> > pop-up disabled and enabled. 
> > 
> > Also, the issue is reported here upstream >
> > https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2432
> 
> Mmh, I'm still confused. I can backport the fix from that bug, but:
> 
> > Following Notification is seen on first login :
> >
> > "Screen lock is disabled Screen locking requires the GNOME display manager."
> 
> That is the expected behavior, with or without that patch. What the upstream
> fix changes is that the notification is only shown once after disabling GDM,
> instead of at each login.

It seems this fix is already there is RHEL8.4. I am seeing the notification only once after the 
vnc service restart. If I relogin into the vnc session, I am not seeing the notification for the 
subsequent logins. It seems the customer is using RHEL8.2. I have not checked it on RHEL8.2.

@Florian So, As per my understanding it is not possible to completely disable this notification.
But we can reduced it's frequency. Is it correct?

> 
> Again, I cannot fix anything if I don't know what I'm supposed to fix in the
> first place.
Comment 7 Florian Müllner 2021-07-19 13:18:45 UTC 
(In reply to amit yadav from comment #5)

> It seems this fix is already there is RHEL8.4.

No, it's not. Note that in the context of the notification, "login" refers to the GNOME session. If that session keeps running when vnc disconnects, and further vnc logins reconnect to the existing GNOME session, then it is expected that the notification isn't shown.

What the upstream fix for https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2432 does is that gnome-shell remembers that the notification was shown, and will not show it again the next time the (GNOME) session is started without gdm.

So is this something you want backported?

> @Florian So, As per my understanding it is not possible to completely
> disable this notification.
> But we can reduced it's frequency. Is it correct?

That is what #2432 does. https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1511 also makes sure the `show-banners` setting in `org.gnome.desktop.notifications` is respected. We can backport that as well if desired.
Comment 8 amit yadav 2021-07-20 07:17:55 UTC 
(In reply to Florian Müllner from comment #7)
> (In reply to amit yadav from comment #5)
> 
> > It seems this fix is already there is RHEL8.4.
> 
> No, it's not. Note that in the context of the notification, "login" refers
> to the GNOME session. If that session keeps running when vnc disconnects,
> and further vnc logins reconnect to the existing GNOME session, then it is
> expected that the notification isn't shown.
> 
> What the upstream fix for
> https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2432 does is that
> gnome-shell remembers that the notification was shown, and will not show it
> again the next time the (GNOME) session is started without gdm.
> 
> So is this something you want backported?
> 
> > @Florian So, As per my understanding it is not possible to completely
> > disable this notification.
> > But we can reduced it's frequency. Is it correct?
> 
> That is what #2432 does.
> https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1511 also makes
> sure the `show-banners` setting in `org.gnome.desktop.notifications` is
> respected. We can backport that as well if desired.

Yes, it would be nice to backport them both to RHEL8.
Comment 9 Michal Odehnal 2021-08-05 16:45:05 UTC 
Automation suite was run with good result - no unexpected fails and I was unable to reproduce the issue with the new version. Switching to Verified:Tested.
Comment 14 errata-xmlrpc 2021-11-09 19:34:38 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 (Moderate: GNOME security, bug fix, and enhancement update), 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-2021:4381
Note You need to log in before you can comment on or make changes to this bug.