Good point. I did indeed have protobuf and protoc libraries lying around in /usr/local.
I thought I checked all the stuff, but I guess I should have done that strace I considered doing. Thanks, sorry for the spurious bug report. On Sun, Jul 30, 2017, 23:24 Keith Winstein <kei...@mit.edu> wrote: > Thank you for this report. Is it possible you have a different version of > libprotobuf in your LD_LIBRARY_PATH, or a different version of mosh-server > in your PATH? > > (Do you have anything related to libprotobuf in /usr/local ?) > > On Sun, Jul 30, 2017 at 2:40 PM, Ivan Vucica <i...@vucica.net> wrote: > >> Package: mosh >> Version: 1.2.6-1+b2 >> Severity: important >> >> Dear Maintainer, >> >> Yesterday I updated almost all of my system to stretch / stable. >> (Stragglers >> include things like php which might break some of my projects.) >> >> Today I am no longer able to connect to my server with mosh. Running >> mosh-server manually results in: >> >> mosh-server: symbol lookup error: mosh-server: undefined symbol: >> _ZNK6google8protobuf11MessageLite25InitializationErrorStringB5cxx11Ev >> >> Perhaps there is some incompatibility with libprotobuf? >> >> Could we please patch stretch / stable? >> >> -- System Information: >> Debian Release: 9.1 >> APT prefers stable >> APT policy: (500, 'stable') >> Architecture: amd64 (x86_64) >> >> Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) >> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=en_US:en >> (charmap=ANSI_X3.4-1968) >> Shell: /bin/sh linked to /bin/dash >> Init: systemd (via /run/systemd/system) >> >> Versions of packages mosh depends on: >> ii dpkg 1.18.24 >> ii libc6 2.24-11+deb9u1 >> ii libgcc1 1:6.3.0-18 >> ii libprotobuf10 3.0.0-9 >> ii libssl1.1 1.1.0f-3 >> ii libstdc++6 6.3.0-18 >> ii libtinfo5 6.0+20161126-1 >> ii libutempter0 1.1.6-3 >> ii openssh-client 1:7.4p1-10+deb9u1 >> ii zlib1g 1:1.2.8.dfsg-5 >> >> Versions of packages mosh recommends: >> ii perl-base [libio-socket-ip-perl] 5.24.1-3+deb9u1 >> >> mosh suggests no packages. >> >> -- no debconf information >> > >
