do-partial-upgrade crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubuntu-release-upgrader (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Crashed on last update.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubuntu-
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.8-0ubuntu2
Architecture: amd64
CrashDB: ubuntu
Date: Wed Nov 22 18:00:48 2017
DistributionCha
# This is a distribution channel descriptor
# For more information see http://
canonical-
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2017-06-22 (153 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
InterpreterPath: /usr/bin/python3.6
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/lib/
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
SegvAnalysis:
Segfault happened at: 0x7fb52f14f969: mov (%rbx),%rdi
PC (0x7fb52f14f969) ok
source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ubuntu-
StacktraceTop:
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
() at /usr/lib/
Title: do-partial-upgrade crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
| George Shuklin (george-shuklin) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
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 #1544395, 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.