packagekitd crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
packagekit (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This error came up when I was copying files from an SD card to my SSD.
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: packagekit 1.1.13-2
ProcVersionSign
Uname: Linux 5.4.0-9-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
Date: Sat Jan 25 08:26:36 2020
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2020-01-25 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
ProcCmdline: /usr/lib/
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/sh
SegvAnalysis:
Segfault happened at: 0x7fca189be5e3: mov %eax,(%rdx)
PC (0x7fca189be5e3) ok
source "%eax" ok
destination "(%rdx)" (0x7fca09b57040) 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_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
?? () from /lib/x86_
Title: packagekitd crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
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 #1860855, 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.