apport-gtk crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Possibly something to do with trying to report a crash of easystroke, which has started happening since updates for 16.10 a few days ago
Easystroke build fails, possibly connected to this: from https:/
(I know it's for redhat but might give some clues)
Before gcc-6.0.0 arrived in rawhide it failed to build because it depends on libsigc++ which now requires C++11, but gcc-6 defaults to C++14 so that is resolved, and it fails with this error instead:
actions.cc: In constructor 'TreeViewMulti:
actions.cc:57:39: error: 'group' is not a member of 'sigc'
get_selection
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: apport-gtk 2.20.3-0ubuntu6
ProcVersionSign
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.3-0ubuntu6
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Aug 13 13:08:19 2016
ExecutablePath: /usr/share/
InstallationDate: Installed on 2014-08-13 (730 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810)
InterpreterPath: /usr/bin/python3.5
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/share/
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f417343aae9: mov (%rbx),%rdi
PC (0x7f417343aae9) ok
source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apport
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: apport-gtk crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1552577, 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.