Bug 2166406

Summary:	[RHEL9/systemd/Bug] new systemd session idle timer killing midnight commander (mc) even if human input is provided
Product:	Red Hat Enterprise Linux 9	Reporter:	Michal Sekletar <msekleta>
Component:	systemd	Assignee:	Michal Sekletar <msekleta>
Status:	CLOSED MIGRATED	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	9.1	CC:	systemd-maint-list
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-21 12:20:09 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:
Bug Depends On:
Bug Blocks:	2125240

Description Michal Sekletar 2023-02-01 18:08:43 UTC

This bug was initially created as a copy of Bug #2158355

I am copying this bug because: 



Description of problem:

The new systemd idle session timer is always being triggered when 'mc' or 'mcedit' is being used. The session is killed after the set timeout ignoring active input by the human 'mc'.
With using 'vi' or 'nano' editor the session idle timer works and the session is not killed, only after being idle for the set timer (e.g. the 10 seconds in the reproducer below) the session is killed.

Steps to Reproduce:

1. Modify /etc/systemd/logind.conf, add 'StopIdleSessionSec=10'
2. sudo systemctl restart systemd-logind
3. Run 'mc''
4. Keep being active for 20 seconds (e.g. presses down-key and then up-key)


Actual results:Unable to keep active for 20 seconds, the session is killed after 10 seconds


Expected results:Session is only killed after 10 seconds no human input is provided

Comment 1 RHEL Program Management 2023-09-21 12:16:52 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 2 RHEL Program Management 2023-09-21 12:20:09 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.