packagekitd crashed with SIGSEGV in AptCacheFile::resolvePkgID()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
packagekit (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I was just doing updates.
ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: packagekit 1.2.5-2ubuntu1
ProcVersionSign
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu78
Architecture: amd64
CasperMD5CheckR
Date: Fri Mar 11 18:24:53 2022
ExecutablePath: /usr/libexec/
InstallationDate: Installed on 2022-02-05 (33 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220114)
ProcCmdline: /usr/libexec/
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/sh
SegvAnalysis:
Segfault happened at: 0x7f1d6ba1f082 <__strcmp_
PC (0x7f1d6ba1f082) ok
source "(%rdi,%rdx,1)" (0x7f1de7ca36dc) not located in a known VMA region (needed readable region)!
destination "%eax" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: packagekit
StacktraceTop:
AptCacheFile:
AptIntf:
() at /usr/lib/
()
g_tree_remove () at /lib/x86_
Title: packagekitd crashed with SIGSEGV in AptCacheFile:
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:
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 #1964559, 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.