packagekitd crashed with SIGSEGV in pkgSourceList::AddVolatileFile()

[IT-Support]

MDATP crashes while increasing the loglevel

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: packagekit 1.2.5-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Mar 14 17:29:14 2022
ExecutablePath: /usr/libexec/packagekitd
InstallationDate: Installed on 2022-02-11 (31 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220211)
ProcCmdline: /usr/libexec/packagekitd
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/sh
SegvAnalysis:
 Segfault happened at: 0x7f7611e26d05 <_ZN13pkgSourceList15AddVolatileFileEP12pkgIndexFile+21>: mov 0x18(%rdi),%rsi
 PC (0x7f7611e26d05) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: packagekit
StacktraceTop:
 pkgSourceList::AddVolatileFile(pkgIndexFile*) () from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
 pkgSourceList::AddVolatileFile(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >*) () from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
 AptIntf::init(char**) () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
 ?? () from /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
 ?? ()
Title: packagekitd crashed with SIGSEGV in pkgSourceList::AddVolatileFile()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:

[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 #1916035, 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.