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 1329803 - gnome-shell to set LockedHint property from logind
Summary: gnome-shell to set LockedHint property from logind
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1335499
Blocks: 1323623
TreeView+ depends on / blocked
 
Reported: 2016-04-23 11:06 UTC by Victor Toso
Modified: 2016-11-04 01:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 01:44:21 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2258 0 normal SHIPPED_LIVE gnome-shell, gnome-shell-extensions, and gtk3 bug fix and enhancement update 2016-11-03 13:32:13 UTC

Description Victor Toso 2016-04-23 11:06:33 UTC 
Description of problem:
Logind is not used to the lock the session but it is always used to unlock it by gdm. This makes it hard to reliably track if session is locked or not.


Steps to Reproduce:
You can verify it by monitoring the Session from login1 and Locking you session.

gdbus monitor --system --dest org.freedesktop.login1 --object-path /org/freedesktop/login1/session/_31

Actual results:
You can see that the Unlock signal was emitted but Lock was not. It is also possible to see that IdleHint property changed correctly but that isn't reliable enough IMHO (It is broken in my F23, for instance)

Expected results:
Lock signal should be emitted.


Additional info:
Bug was filled upstream as well [0] and this is interesting for spice-vdagent in order to disable features like drag-and-drop when system is locked [1]

[0] https://bugzilla.gnome.org/show_bug.cgi?id=764773
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1323623
Comment 2 Ray Strode [halfline] 2016-05-09 15:28:26 UTC 
So we can fix gnome-shell to lock itself via logind but:

1) doing it introduces a race where logind will emit Locked before it's actually Locked (unless gnome-shell calls logind's Lock method after it's already locked and then ignores the ensuring locked signal itself)

2) I don't think any other desktop environment does locking that way at the moment.  The cross desktop api for screen locking is the org.freedesktop.ScreenSaver interface (which is a bit of a misnomer) so I'd recommend vdagent use that.
Comment 3 Ray Strode [halfline] 2016-05-09 18:27:04 UTC 
So actually the cross desktop api for screen locking won't work.  Our implementation is currently this:

        } else if (g_strcmp0 (method_name, "GetActive") == 0) {•
                goto unimplemented;•
        }

So you'd need to use org.gnome.ScreenSaver.GetActive instead for RHEL.
Comment 4 Victor Toso 2016-05-12 10:38:42 UTC 
Another way to have this is by using logind's new property LockedHint.
gnome-shell can set this property and applications can query it to track if session is Locked or not.

Proposal patch on upstream bugzilla.
Comment 5 Victor Toso 2016-05-16 08:53:59 UTC 
Changing the summary based on comment #4

Patch for this is upstream:
https://git.gnome.org/browse/gnome-shell/commit/?id=ddea54a5398c123a4711243e55811c8ba26f8b85
Comment 7 Victor Toso 2016-08-11 13:45:57 UTC 
Just for future reference, build with this patch is:
3.14.4-45
Comment 10 errata-xmlrpc 2016-11-04 01:44:21 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://rhn.redhat.com/errata/RHBA-2016-2258.html
Note You need to log in before you can comment on or make changes to this bug.