Bug 1728995

Summary: Failed to detect screen is locked by dbus or loginctl utility when click Lock menu quickly after login
Product: Red Hat Enterprise Linux 7 Reporter: VMwareEng <rhel-eng>
Component: dbusAssignee: David King <dking>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.0   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-15 07:37:27 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:
Description Flags
test.sh and screen-status-monitor.desktop none

Description VMwareEng 2019-07-11 07:37:25 UTC
Created attachment 1589324 [details]
test.sh and screen-status-monitor.desktop

Description of problem: 
Click Lock menu very soon after login, the screen is locked as expected. But in this case, there is no org.gnome.ScreenSaver related dbus generated, and less way to report screen is locked.

Version-Release number of selected component (if applicable): All Redhat version, I tested at Redhat6.10, and Redhat7.6

How reproducible: Click Lock system menu very quickly after login.

Steps to Reproduce:
1. Put attached test.sh under /tmp/test.sh
2. Put attached screen-status-monitor.desktop to /etc/xdg/autostart/screen-status-monitor.desktop
3. Click Lock menu very quickly after login
4. Verify /tmp/monitor, there is no ScreenSaver related dbus in it
5. Verify /tmp/result, the first "true/false" is to query dbus org.gnome.screensaver.GetAcitve, the second is to query session lock status from loginctl utility, they both indicate "unlocked" status.

Actual results:
In most of time, the query result is "unlocked" status

Expected results:
the query result is "locked" status

Additional info:

Comment 4 RHEL Program Management 2021-03-15 07:37:27 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.