packagekitd crashed with SIGSEGV in utilBuildPackageId()

Bug #1754265 reported by Julian Andres Klode
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
packagekit (Ubuntu)
Fix Released
High
Julian Andres Klode

Bug Description

PackageKit seems to be crashing randomly on bionic, not sure why, did not investigate further yet.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: packagekit 1.1.7-1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Thu Mar 8 08:35:34 2018
ExecutablePath: /usr/lib/packagekit/packagekitd
InstallationDate: Installed on 2017-12-08 (89 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/lib/packagekit/packagekitd
SegvAnalysis:
 Segfault happened at: 0x7fca622a9ecc <_Z18utilBuildPackageIdRKN8pkgCache11VerIteratorE+124>: cmpb $0x6,0x22(%rax)
 PC (0x7fca622a9ecc) ok
 source "$0x6" ok
 destination "0x22(%rax)" (0x0015f6da) 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:
 utilBuildPackageId(pkgCache::VerIterator const&) () at /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
 AptIntf::emitPackage(pkgCache::VerIterator const&, PkInfoEnum) () at /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
 AcqPackageKitStatus::updateStatus(pkgAcquire::ItemDesc&, int) () at /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
 pkgAcquire::Worker::RunMessages() () at /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
 pkgAcquire::Worker::InFdReady() () at /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0
Title: packagekitd crashed with SIGSEGV in utilBuildPackageId()
UpgradeStatus: Upgraded to bionic on 2017-12-08 (89 days ago)
UserGroups:

Revision history for this message
Julian Andres Klode (juliank) wrote :
Changed in packagekit (Ubuntu):
importance: Undecided → High
status: New → Triaged
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 utilBuildPackageId (ver=...) at apt-utils.cpp:396
 AptIntf::emitPackage (this=0x55ef029ce0e0, ver=..., state=state@entry=PK_INFO_ENUM_DOWNLOADING) at apt-intf.cpp:431
 AcqPackageKitStatus::updateStatus (this=0x7fca6181a4d0, Itm=..., status=0) at acqpkitstatus.cpp:211
 pkgAcquire::Worker::RunMessages (this=this@entry=0x7fca54045cf0) at ./apt-pkg/acquire-worker.cc:375
 pkgAcquire::Worker::InFdReady (this=this@entry=0x7fca54045cf0) at ./apt-pkg/acquire-worker.cc:870

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
tags: removed: need-amd64-retrace
Revision history for this message
Julian Andres Klode (juliank) wrote :

So, the problem is that PackageKit casts the item owner to pkgAcqArchiveSane, but I'm using the mirror method and this now fetches the mirror list every run, and that's probably not a pkgAcqArchive.

information type: Private → Public
Revision history for this message
Julian Andres Klode (juliank) wrote :
Changed in packagekit (Ubuntu):
status: Triaged → In Progress
assignee: nobody → Julian Andres Klode (juliank)
Revision history for this message
Julian Andres Klode (juliank) wrote :

Uploaded so we don't forget about it. Probably want to do a 1.1.9-2 in Debian though and sync it again :)

Changed in packagekit (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package packagekit - 1.1.9-1ubuntu1

---------------
packagekit (1.1.9-1ubuntu1) bionic; urgency=medium

  * Add might-fetch-non-archive.diff to prevent PackageKit from crashing
    when using the mirror method (LP: #1754265)

 -- Julian Andres Klode <email address hidden> Wed, 21 Mar 2018 12:32:34 +0100

Changed in packagekit (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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