Bug#817929: mosh fails to connect, giving a UDP error

2016-03-25 Thread Matthew Gabeler-Lee
On 03/24/2016 12:31 AM, john hood wrote: > I haven't been able to chase these glibc details down. Do you have > pointers to specifics for this? My assessment was based just on reading the referenced glibc-help thread, and the commit it referenced --

Bug#817929: mosh fails to connect, giving a UDP error

2016-03-23 Thread john hood
On 3/22/16 9:48 PM, Matthew Gabeler-Lee wrote: > On Tue, 22 Mar 2016 23:21:31 +0100 Goffredo Baroncelli > wrote: >> Please give a look to >> >> https://sourceware.org/ml/libc-help/2016-03/msg00010.html >> >> to me it seems that the real problem is in glibc. > > From reading

Bug#817929: mosh fails to connect, giving a UDP error

2016-03-23 Thread kreij...@inwind.it
On Tue, 22 Mar 2016 21:48:43 -0400 Matthew Gabeler-Lee wrote: [...] > But what we have here is an uncommon case driven by mosh's linker > options, which means that the glibc workaround for protobuf's incorrect > linker options doesn't (can't?) work. Why are you stating that

Bug#817929: mosh fails to connect, giving a UDP error

2016-03-23 Thread kreij...@inwind.it
On Tue, 22 Mar 2016 21:48:43 -0400 Matthew Gabeler-Lee wrote: [...] > But what we have here is an uncommon case driven by mosh's linker > options, which means that the glibc workaround for protobuf's incorrect > linker options doesn't (can't?) work. Why are you stating that

Bug#817929: mosh fails to connect, giving a UDP error

2016-03-22 Thread Matthew Gabeler-Lee
On Tue, 22 Mar 2016 23:21:31 +0100 Goffredo Baroncelli wrote: > Please give a look to > > https://sourceware.org/ml/libc-help/2016-03/msg00010.html > > to me it seems that the real problem is in glibc. >From reading that thread and looking at the referenced git commit, I'm

Bug#817929: mosh fails to connect, giving a UDP error

2016-03-22 Thread Goffredo Baroncelli
On Mon, 21 Mar 2016 19:23:54 -0400 Matthew Gabeler-Lee wrote: > Package: mosh > Version: 1.2.5-1.1 > Followup-For: Bug #817929 > > Looks like upstream has a patch for this: > > https://github.com/mobile-shell/mosh/pull/732/commits/a47917b97606a03f6bbf0cafd1fcd495b0229790 >

Bug#817929: mosh fails to connect, giving a UDP error

2016-03-21 Thread Matthew Gabeler-Lee
Package: mosh Version: 1.2.5-1.1 Followup-For: Bug #817929 Looks like upstream has a patch for this: https://github.com/mobile-shell/mosh/pull/732/commits/a47917b97606a03f6bbf0cafd1fcd495b0229790 Though it looks like that's a hack and they really want this fixed in protobuf:

Bug#817929: mosh fails to connect, giving a UDP error

2016-03-11 Thread Goffredo Baroncelli
Package: mosh Version: 1.2.5-1.1 Followup-For: Bug #817929 I can confirm that. After a recent update (but I was sure which one) mosh stops to work. The problem seems to be in mosh-server which ends with a SIGSEGV after it forks: $ strace -f mosh-server execve("/usr/bin/mosh-server",

Bug#817929: mosh fails to connect, giving a UDP error

2016-03-11 Thread demure
Package: mosh Version: 1.2.5-1.1 Severity: grave Justification: renders package unusable Dear Maintainer, Mosh is unable to connect to debian sid's mosh-server currently. I have two instances of debian sid, a laptop and a VPS. Neither can connect to each other with mosh, or even them selfs