Thanks Philipp! 1) Can you fill me in -- what version of Mosh is running on the server in your setup?
2) There are packages for pre-1.2.6 versions of Mosh in wheezy, jessie, and jessie-backports (please see https://packages.debian. org/search?keywords=mosh). You could also build from source (it would need to be on both the client and server though to be sure). https://mosh.org/mosh-1.2.5.tar.gz 3) Can you please send all *three* logs from "script"? We need simultaneous captures of the output (1) entering tmux, (2) leaving tmux and entering mosh, and then (3) leaving mosh. So three invocations of script, each producing one logfile. (Use the command-line argument to give the logfile name.) Also can you please tell me your terminal size so I can properly replay the captures? Thanks much, Keith On Tue, Nov 8, 2016 at 1:06 AM, Philipp Marek <[email protected]> wrote: > Hi Keith, > > > What version of Mosh is running on the server? > > What architecture is the server (is it also a Debian amd64 machine)? > Debian amd64, yes. > > > Could you please also test running Mosh 1.2.5 on the client *and* server, > > and seeing if you can replicate the bug? That will help us determine if > > this is a regression. > Do you know when such a package was available in Debian, so that I can find > it in the archives? > > > > Depending on the results, the next request will be for you to use > "script" > > to capture the output (1) entering tmux, (2) leaving tmux and entering > > mosh, and then (3) leaving mosh. > Here you are. > > > > Thanks very much for finding this, > Hah! You're welcome, but I'd be happier if I didn't ;) > > >
