unison-2.40.102-gtk crashed with SIGSEGV

[Louis Bouchard]

segv

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unison-gtk 2.40.102-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Feb 8 15:15:56 2016
ExecutablePath: /usr/bin/unison-2.40.102-gtk
InstallationDate: Installed on 2014-09-05 (521 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcCmdline: unison-2.40.102-gtk
SegvAnalysis:
 Segfault happened at: 0x46ba96: mov (%rbx),%rdi
 PC (0x0046ba96) ok
 source "(%rbx)" (0x00000001) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unison
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: unison-2.40.102-gtk crashed with SIGSEGV
UpgradeStatus: Upgraded to xenial on 2015-11-03 (96 days ago)
UserGroups: adm cdrom dialout dip libvirtd lp lpadmin lxd plugdev sambashare sbuild sudo

[Louis Bouchard (louis)]

Seems to be a regression caused by the last rebuild against ncurses6. Going back to 2.40.102-2ubuntu1 fixes the SEGV

[Apport retracing service (apport)]

StacktraceTop:
 camlUicommon__initPrefs_1207 ()
 camlUicommon__uiInit_1248 ()
 camlUigtk2__start_2965 ()
 camlMain__Body_1088 ()
 camlLinkgtk2__entry ()

[Louis Bouchard (louis)]

This debian bug may explain the issue : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807019

Xenial now has 2.48 which is incompatible with 2.40 so I'm staying on 2.40 for the time being