Bug 1446395

All Rawhide installer images have failed to boot since tmux 2.4 landed in Rawhide.

These errors can be seen in the journal:

Apr 27 19:41:02 localhost systemd[1]: Starting Anaconda...
Apr 27 19:41:02 localhost tmux[1498]: invalid option: set-remain-on-exit
Apr 27 19:41:02 localhost tmux[1498]: open terminal failed: not a terminal
Apr 27 19:41:02 localhost tmux[1498]: no current session
Apr 27 19:41:02 localhost tmux[1498]: no current session
Apr 27 19:41:02 localhost systemd[1]: anaconda.service: Control process exited, code=exited status=1
Apr 27 19:41:02 localhost systemd[1]: Failed to start Anaconda.

I did try removing the 'set-remain-on-exit' option from the config file and restarting the service; that makes the 'invalid option' line go away, but anaconda still fails to start, so I don't *think* that's the problem.

I built a custom image with tmux reverted to 2.3 (by doing a scratch build of 2.3 with an epoch bump), and that boots fine. So tmux 2.4 is definitely the problem here.

anaconda's tmux config file looks like this:

========

# tmux.conf for the anaconda environment

bind -n M-tab next
bind -n F1 list-keys

set-option -s exit-unattached off
set-option -g base-index 1
set-option -g set-remain-on-exit on
set-option -g history-limit 10000

new-session -s anaconda -n main "anaconda"

set-option status-right '#[fg=blue]#(echo -n "Switch tab: Alt+Tab | Help: F1 ")'

new-window -d -n shell          "bash --login"
new-window -d -n log            "tail -F /tmp/anaconda.log"
new-window -d -n storage-log    "tail -F /tmp/storage.log"
new-window -d -n program-log    "tail -F /tmp/program.log"

# The idea here is to detach the client started here via anaconda.service, and
# then re-attach to it in the tmux service run on the console tty. However,
# the detach-client directive is now giving us "no current client" for some
# reason.
# detach-client -s anaconda

========

And anaconda.service does this:

Environment=HOME=/root MALLOC_CHECK_=2 MALLOC_PERTURB_=204 PATH=/usr/bin:/bin:/sbin:/usr/sbin:/mnt/sysimage/bin:/mnt/sysimage/usr/bin:/mnt/sysimage/usr/sbin:/mnt/sysimage/sbin LANG=en_US.UTF-8 GDK_BACKEND=x11 XDG_RUNTIME_DIR=/tmp GIO_USE_VFS=local
WorkingDirectory=/root
ExecStart=/usr/bin/tmux -u -f /usr/share/anaconda/tmux.conf start

If I recreate this manually, though - by running:

HOME=/root MALLOC_CHECK_=2 MALLOC_PERTURB_=204 PATH=/usr/bin:/bin:/sbin:/usr/sbin:/mnt/sysimage/bin:/mnt/sysimage/usr/bin:/mnt/sysimage/usr/sbin:/mnt/sysimage/sbin LANG=en_US.UTF-8 GDK_BACKEND=x11 XDG_RUNTIME_DIR=/tmp GIO_USE_VFS=local /usr/bin/tmux -u -f /usr/share/anaconda/tmux.conf start

from /root, tmux starts fine. Not sure what that implies; some complication based on how systemd runs it?

This is an automatic F27 Alpha blocker per "Complete failure of any release-blocking TC/RC image to boot at all under any circumstance - "DOA" image (conditional failure is not an automatic blocker)"