Public bug reported:

mosh-server in Xenial crashes immediately on startup.  This is 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

** Affects: glibc
     Importance: Unknown
         Status: Unknown

** Affects: glibc (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: mosh (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: mosh (Debian)
     Importance: Unknown
         Status: Unknown


** Tags: amd64 apport-crash need-amd64-retrace xenial

** Bug watch added: Debian Bug tracker #817929
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817929

** Also affects: mosh (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817929
   Importance: Unknown
       Status: Unknown

** Bug watch added: Sourceware.org Bugzilla #19861
   http://sourceware.org/bugzilla/show_bug.cgi?id=19861

** Also affects: glibc via
   http://sourceware.org/bugzilla/show_bug.cgi?id=19861
   Importance: Unknown
       Status: Unknown

** Also affects: glibc (Ubuntu)
   Importance: Undecided
       Status: New

** Description changed:

- This appears to be a glibc bug, but a Mosh workaround was committed
- upstream. See
+ mosh-server in Xenial crashes immediately on startup.  This is 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)!
+  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
+  ?? ()
+  ?? () 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

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561621

Title:
  mosh-server crashed with SIGSEGV in utempter_add_record()

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1561621/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to