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.

Hi,
The version of tmux in RHEL8 and Centos Stream 8, 2.7, has a now-fixed bug. The bug can result in activity to the tmux socket hanging, while spinning a CPU core on the host. Although intermittent, it can be frustrating for folks that "live" in tmux when it occurs for day-to-day work, as losing all of their live shells/sessions at once is not far off of an experience from an unexpected host crash.

I believe I had experience this same bug on EL7, on 2.7 multiple times, with a homemade RPM build, and eventually moved on to 2.8 and did not have the issue anymore. I was hoping that this would be resolved in EL8, at least due to the change in circumstances, if not a different tmux version, but unfortunately, it seems to be present as I encountered the issue on an EL8 host.

There is a bug report for this in https://github.com/tmux/tmux/issues/1352 , plus a short linked git commit that fixes the issue. Is it possible to update the tmux version in EL8 to an unaffected version, or backport the fix into the distribution RPM for 2.7? It would be preferable to use a distribution-provided RPM rather than a homemade or third-party RPM, but we otherwise have no need for a newer version besides the fix. Thank you very much for your consideration.

Thanks,
Ross

Sorry about that, I know how frustrating that can be.  I just looked in to this and it looks like a low risk fix, so I'm going to see what I can do to get it in to the next update.

I'm also going to see if I can get it in to CentOS Stream 8 first, but I'm not sure if I can.

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 (tmux 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/RHBA-2023:7094