Solved Tmux [excited]

martinrame · Jan 30, 2022

Hi, in a recently installed FreeBSD 13 machine I was using tmux, but since a couple of minutes ago I wasn't able start it again, getting "[excited] 65;6402;1c" on my terminal.

To try to fix it I deleted .tmux.conf and the .tmux directory, but the problem still persists. I also deleted the tmux package and
reinstalled again (tmux 3.2a from pkg), but I'm getting the same error.

Any hint?

Jose · Jan 30, 2022

martinrame said:
Hi, in a recently installed FreeBSD 13 machine I was using tmux, but since a couple of minutes ago I wasn't able start it again, getting "[excited] 65;6402;1c" on my terminal.

To try to fix it I deleted .tmux.conf and the .tmux directory, but the problem still persists. I also deleted the tmux package and
reinstalled again (tmux 3.2a from pkg), but I'm getting the same error.

Any hint?

The "excited" in brackets is the name of your session. Typing ctrl-b and then "d" should detached from whatever the "excited" session it.

martinrame · Jan 30, 2022

Hi Jose, I cannot do that, since tmux is not running.

eternal_noob · Jan 30, 2022

Maybe https://askubuntu.com/questions/442766/tmux-exited-on-startup helps?

Jose · Jan 30, 2022

martinrame said:
Hi Jose, I cannot do that, since tmux is not running.

~~Yes, it is.~~
eternal_noob is probably right.

martinrame · Jan 30, 2022

Jose said:
Yes, it is.

 

[leonardo@x270 ~] $ ps ax|grep tmux

38347  0  S+      0:00.00 grep tmux

[leonardo@x270 ~] $

I don't see it running.

martinrame · Jan 30, 2022

eternal_noob said:
Maybe https://askubuntu.com/questions/442766/tmux-exited-on-startup helps?

Hi eternal_noob, most of the issues posted in that link are related to some errors in .tmux.conf, but I deleted mine, so not exactly the issue I'm having here. Also I deleted the file /tmp/tmux-1000 (and tmux-1001) but the error is still present.

martinrame · Jan 30, 2022

I found a way to let tmux start. My shell is zsh, so I first started an instance of /bin/sh, then ran tmux and it worked.

Now I think the problem is related to my ~/.zshrc (copied from my main FreeBSD server).

martinrame · Jan 30, 2022

I found it!, in my ~/.zshrc I had this alias:

alias tmux='tmux new-session "tmux source-file ~/.tmux/session1"

(in the main server tmux is automatically started with a couple of panels one containing a shell and the other with the ranger file manager).

I'll mark this as solved.

Erichans · Jan 30, 2022

martinrame said:
Hi, in a recently installed FreeBSD 13 machine I was using tmux, but since a couple of minutes ago I wasn't able start it again, getting "[excited] 65;6402;1c" on my terminal.

martinrame said:
I found it!, in my ~/.zshrc I had this alias:

alias tmux='tmux new-session "tmux source-file ~/.tmux/session1"

I'm not familiar with the zsh but, taking your alias definition line as is:

Code:

alias tmux='tmux new-session "tmux source-file ~/.tmux/session1"
12345678901234567890123456789012345678901234567890123456789012345   <--

your 65;6402;1c shows a remarkable "65" resemblance with the point at which in your alias definition I would expect a closing single quote. (At least that is were the closing quote must be in a tcsh alias definition.)

In general I have found it very helpfull to be able to track down what command at the command line is actually being executed; such as a shell builtin command; an alias; or an external command. In both the zsh and the tcsh which tmux will help.