Comment 0 for bug 1561621

This appears to be a glibc bug, but a Mosh workaround was committed upstream. See

https://github.com/mobile-shell/mosh/issues/727
https://bugs.debian.org/817929
https://sourceware.org/ml/libc-help/2016-03/msg00004.html
https://sourceware.org/bugzilla/show_bug.cgi?id=19861

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: mosh 1.2.5-1.1build1
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Mar 24 12:22:08 2016
Disassembly: => 0x0: Cannot access memory at address 0x0
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/mosh-server
InstallationDate: Installed on 2016-02-19 (34 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218)
ProcCmdline: mosh-server
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: mosh
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libutempter.so.0
 utempter_add_record () from /usr/lib/x86_64-linux-gnu/libutempter.so.0
 ?? ()
 __libc_start_main (main=0x564683ff2000, argc=1, argv=0x7fff22b44308, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff22b442f8) at ../csu/libc-start.c:291
Title: mosh-server crashed with SIGSEGV in utempter_add_record()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo wireshark