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.
This has already been reported as a Debian bug, <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529082>. If another user creates a path /tmp/tmux-$UID, user $UID cannot start tmux.
An easy fix would use XDG_RUNTIME_DIR by default, but that depends on fixing bug 753882.
Tired of dragging this one forward and never getting it approved. Approving for 7.3. Will implement what Debian did for this problem so there is at least some consistency across vendors (plus, Debian's fix has been present in their packages since 2009).
(In reply to Florian Weimer from comment #0)
> An easy fix would use XDG_RUNTIME_DIR by default
And that is not the fix we're trying to apply. Instead, there are attempts to move socket file to /run and make tmux sgid to be able to write there.
I do not believe upstream tests or supports running tmux as sgid. I see that both Debian and Fedora used to have sgid tmux at some point, but abandoned the idea.
Fedora:
http://pkgs.fedoraproject.org/cgit/rpms/tmux.git/commit/?id=d659dacd7ed7df042c3c844a93f92961e978981f
Debian has this in NEWS.Debian:
tmux (1.4-7) unstable; urgency=low
Starting with version 1.4-7, tmux is no longer installed setgid utmp and
server sockets are no longer placed under /var/run/tmux, reverting to
the default upstream behavior (sockets in a user directory under /tmp).
We recommend that you close any open tmux sessions before proceeding
with the upgrade. If necessary, old servers can be accessed after the
upgrade with e.g. "tmux -S /var/run/tmux/tmux-`id -u`/default attach".
-- Romain Francoise <rfrancoise> Sat, 16 Apr 2011 19:16:23 +0200
SUSE also rejected setgid approach, afaics:
https://bugzilla.novell.com/show_bug.cgi?id=567398#c3
Do we have a reason to believe that the approach that turned out to be wrong for both Fedora and Debian is the right thing to do for RHEL?
Florian, any thoughts from you as the reporter of this issue?