packagekitd crashed with SIGSEGV

Bug #1860855 reported by Pete Graner
34
This bug affects 4 people
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
Fix Released
Undecided
Unassigned
packagekit (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Message popped up about there being a system error.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: packagekit 1.1.13-2
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
Date: Sat Jan 25 13:28:12 2020
ExecutablePath: /usr/lib/packagekit/packagekitd
InstallationDate: Installed on 2020-01-25 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
ProcCmdline: /usr/lib/packagekit/packagekitd
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/sh
SegvAnalysis:
 Segfault happened at: 0x7f8244d2f5e3: mov %eax,(%rdx)
 PC (0x7f8244d2f5e3) ok
 source "%eax" ok
 destination "(%rdx)" (0x7f8235e09040) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: packagekit
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
 ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
 ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
 ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
 ?? () from /lib/x86_64-linux-gnu/libapt-pkg.so.5.90
Title: packagekitd crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

separator:

Revision history for this message
Pete Graner (pgraner) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 pkgCacheGenerator::NewGroup (this=0x7f8230062700, Grp=..., Name=...) at ../apt-pkg/pkgcachegen.cc:564
 pkgCacheListParser::NewGroup (this=0x7f8230045ec0, Name=..., Grp=...) at include/apt-pkg/pkgcachegen.h:180
 debListParser::NewVersion (this=0x7f8230045ec0, Ver=...) at ../apt-pkg/deb/deblistparser.cc:215
 pkgCacheGenerator::MergeListVersion (this=0x7f8230062700, List=..., Pkg=..., Version=..., OutVer=@0x7f823660d4d8: 0x0) at ../apt-pkg/pkgcachegen.cc:445
 pkgCacheGenerator::MergeList (this=this@entry=0x7f8230062700, List=..., OutVer=<optimized out>, OutVer@entry=0x0) at ../apt-pkg/pkgcachegen.cc:287

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in packagekit (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in packagekit (Ubuntu):
status: New → Confirmed
Revision history for this message
Julian Andres Klode (juliank) wrote :

This is fixed in APT 1.9.8, which will be synced later today.

information type: Private → Public
Changed in packagekit (Ubuntu):
status: Confirmed → Invalid
Changed in apt (Ubuntu):
status: New → Fix Committed
Revision history for this message
Julian Andres Klode (juliank) wrote :

This bug was fixed in the package apt - 1.9.8

---------------
apt (1.9.8) experimental; urgency=medium

  * pkgcache.cc: Mix PACKAGE_VERSION into the cache hash
  * mmap: Do not look for empty pool unless we need to
  * apt-verbatim.ent: Update ubuntu-codename from disco to focal
  * NewGroup: Create GrpIterator after allocation (fix segfault)

 -- Julian Andres Klode <email address hidden> Mon, 27 Jan 2020 13:25:52 +0100

Changed in apt (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Julian Andres Klode (juliank) wrote :

(Sorry, the bug is not listed in the changelog, so closed it with syncpackage, so it does not get forgotten - will take some time to migrate from proposed to release pocket)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.