Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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
In the attached Case i already provided input that also the more important 'less' command is impacted. E.g. tailing/browsing interactive log file will also suddenly be abrupted after exactly 'StopIdleSecs' after 'less' is started irrespective that the human did some interactive (non-idle) browsing.
(In reply to Lukáš Nykrýn from comment #6)
> Just for the record, this BZ is blocked by Red
> Hathttps://bugzilla.redhat.com/show_bug.cgi?id=2174006 we need to sort out
> that first
Kernel changes were already merged and should appear in linux-6.5. Next, is to add small check in logind and omit idle check for graphical sessions.
Comment 10RHEL Program Management
2023-09-21 12:16:26 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 11RHEL Program Management
2023-09-21 12:20:02 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.
Comment 12Red Hat Bugzilla
2024-01-20 04:25:36 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days