ssh host 'tmux new-session -d -s session' does not work anymore

[Alessio Bolognino]

Binary package hint: tmux

I upgraded to natty just yesterday and it broke one of my scripts: after debugging I found out that the culprit is (probably) tmux:

ssh host 'tmux new-session -d -s session' used to work on maverick, but it doesn't anymore. For the record I compiled tmux 1.4 (source from the project homepage) and it does work, so this is a bug in natty's tmux.

When executing ssh host 'tmux new-session -d -s session' tmux creates the new session, but hangs and never exits.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: tmux 1.3-2+squeeze1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
Architecture: i386
Date: Wed Apr 27 04:01:14 2011
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
SourcePackage: tmux
UpgradeStatus: Upgraded to natty on 2011-04-25 (1 days ago)

[Alessio Bolognino (themolok)]

I installed maverick's tmux (1.3-1) on natty (with maverick's .deb) and it doesn't work.
I recompiled maverick's tmux on natty and it doesn't work either. That's strange.

[Karl Ferdinand Ebert (kfebert)]

Hello Alessio,

as Ubuntu has no own package of tmux, only version numbers from Debian count. For your problem: Did you read /usr/share/doc/tmux/NEWS.gz during or after updating tmux from 1.3-2 or 1.4-5?
Could you describe what is not working and provide your script? It works for me but could be related to the changing of the socket directory.

Best regards,

Ferdinand

[Alessio Bolognino (themolok)]

> Did you read /usr/share/doc/tmux/NEWS.gz during or after updating tmux from 1.3-2 or 1.4-5?

No, I haven't installed tmux 1.4 from a debian package, but I compiled it from the source provided mainstream.

> Could you describe what is not working and provide your script? It works for me but could be related to the changing of the socket directory.

Well, I can't distribute the script, the command that fails is

ssh host 'tmux new-session -d -s session'

and I obviously tried it outside of the script. Sadly I haven't another Natty machine, so I can't test if it's a problem with my configuration (I find it unlikely, since I haven't really changed much and I also tried to run it from another user).

Again, it works with 1.4 and it used to work on Maverick (I tested it on another machine and it still works).
Let me know what can I do to help you.

[Alessio Bolognino (themolok)]

Why is this marked as "Incomplete"? I asked a friend of mine and he too can reproduce this bug on his Natty machine.

[Karl Ferdinand Ebert (kfebert)]

Please run then tmux -vvv and provide the created logs (as mentioned in /usr/share/doc/FAQ.gz).

>> Did you read /usr/share/doc/tmux/NEWS.gz during or after updating tmux from 1.3-2 or 1.4-5?
>No, I haven't installed tmux 1.4 from a debian package, but I compiled it from the source provided mainstream.
I assume you did not understand, what I was talking about.

[Alessio Bolognino (themolok)]

This is the only log that
ssh localhost '/usr/bin/tmux -vvv new-session -d -s session'
creates. I noticed that tmux 1.4 creates two logs, one named tmux-server-$PID, one named tmux-client-$PID.

I'm using gnome-terminal, the $TERM is xterm and when run over ssh $TERM is "dumb"

This is the diff between the log created by tmux 1.4 and Ubuntu's tmux (1.3*), I thought it could be useful since one mentions a socket and the other does not.

diff ok/tmux-server-10960.log ~/tmux-server-11265.log
1,2c1
< server started, pid 10960
< socket path /tmp/tmux-1000/default
---
> server started, pid 11265
146c145
< input_parse: '1' ground
---
> input_parse: '2' ground
148,149c147,148
< input_parse: '3' ground
< input_parse: '9' ground
---
> input_parse: '2' ground
> input_parse: '8' ground
204,205c203,204
< input_parse: '4' ground
< input_parse: '7' ground
---
> input_parse: '5' ground
> input_parse: '5' ground

[Karl Ferdinand Ebert (kfebert)]

Hello Alessio,

there is a new version in Debian, therefore in Ubuntu. Would you be so kind to reproduce your bug against this version?

Best regards,

Ferdinand

[Daniel Hahler (blueyed)]

As far as I understand this looks like a regression with 1.3-1, which is fixed in 1.4, given that the Ubuntu/Debian package for 1.4 and later works.

It works for me in Precise (development release), using tmux 1.5-3.

Please let us know, if you can verify that it works in a later release.
You could try installing the latest tmux package manually in e.g. Natty. See the "Binary packages" at https://launchpad.net/ubuntu/precise/+source/tmux.

[Alessio Bolognino (themolok)]

I'm using Ubuntu 11.10 and tmux-1.5-1 (standard package) and this bug seems gone.
You can probably close the bug report (I would do it myself but I'm not sure which status I should set).