synaptic crashed with SIGSEGV in _XReply()

[Alejandro Davila]

Since I updated to 17.10, Synaptic hasn't worked. I still can't access to it

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: synaptic 0.84.2
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 9 22:53:50 2017
ExecutablePath: /usr/sbin/synaptic
InstallationDate: Installed on 2016-07-31 (467 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: synaptic
SegvAnalysis:
 Segfault happened at: 0x7f977f2a3982 <_XReply+50>: cmpq $0x0,0x28(%rcx)
 PC (0x7f977f2a3982) ok
 source "$0x0" ok
 destination "0x28(%rcx)" (0x00000028) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: synaptic
StacktraceTop:
 _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6
 ()
 ()
 ()
Title: synaptic crashed with SIGSEGV in _XReply()
UpgradeStatus: Upgraded to artful on 2017-10-31 (9 days ago)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1701845, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.