apport-gtk crashed with SIGSEGV

[Gene Soo]

Error occurred on first boot Daily Build Ubuntu Desktop 17.04.

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: apport-gtk 2.20.4-0ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
Uname: Linux 4.10.0-8-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CrashReports:
 640:1000:122:8395118:2017-02-26 00:31:24.667407274 -0600:2017-02-26 00:31:25.667407274 -0600:/var/crash/_usr_bin_compiz.1000.crash
 640:1000:122:6792304:2017-02-26 00:31:35.076570510 -0600:2017-02-26 00:31:36.076570510 -0600:/var/crash/_usr_share_apport_apport-gtk.1000.crash
CurrentDesktop: Unity:Unity7
Date: Sun Feb 26 00:31:30 2017
ExecutablePath: /usr/share/apport/apport-gtk
ExecutableTimestamp: 1486144051
InstallationDate: Installed on 2017-02-26 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170225)
InterpreterPath: /usr/bin/python3.5
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
ProcCwd: /home/gene
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fbe38a84889: mov (%rbx),%rdi
 PC (0x7fbe38a84889) 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/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: apport-gtk crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm 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 #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.