synaptic crashed with SIGSEGV in _XReply() in XWayland

Bug #1726887 reported by Ade Malsasa Akbar on 2017-10-24
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
synaptic (Ubuntu)
Undecided
Unassigned

Bug Description

Synaptic crashes in Xwayland mode in Artful.

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: Tue Oct 24 21:16:56 2017
ExecutablePath: /usr/sbin/synaptic
InstallationDate: Installed on 2017-10-24 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: synaptic
SegvAnalysis:
 Segfault happened at: 0x7f4569c70982 <_XReply+50>: cmpq $0x0,0x28(%rcx)
 PC (0x7f4569c70982) 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 () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? ()
 ?? ()
 ?? ()
Title: synaptic crashed with SIGSEGV in _XReply()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Ade Malsasa Akbar (malsasa) wrote :
information type: Private → Public

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.

tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers