Red Hat Bugzilla – Bug 1464556
[abrt] PackageKit: pk_backend_refresh_cache_thread(): packagekitd killed by signal 11
Last modified: 2017-08-21 13:09:10 EDT
Description of problem:
I had just booted this system and started KDE. I had not begun any other activities.
Version-Release number of selected component:
runlevel: N 3
Thread no. 1 (3 frames)
#0 pk_backend_refresh_cache_thread at pk-backend-dnf.c:1654
#1 pk_backend_job_thread_setup at pk-backend-job.c:813
#2 g_thread_proxy at gthread.c:784
This is a private, duplicate bug report of bug 1114207. The report has been created because Bugzilla cannot grant access to a comment for a specific group.
Created attachment 1291230 [details]
Created attachment 1291231 [details]
Created attachment 1291232 [details]
Created attachment 1291233 [details]
Created attachment 1291234 [details]
Created attachment 1291235 [details]
Created attachment 1291236 [details]
Created attachment 1291237 [details]
Created attachment 1291238 [details]
Created attachment 1291239 [details]
Created attachment 1291240 [details]
Created attachment 1291241 [details]
*** This bug has been marked as a duplicate of bug 1114207 ***
I highly doubt this is actually a dupe of a 3 year old bug which hasn't shown up in any of the interim releases, but is now reliably happening to every Rawhide KDE system, AFAICT.
I don't think there's actually anything private in any of the bug data, here, and it's an important bug which should be publicly viewable.
Proposing as a Beta blocker per criterion "The installed system must be able to download and install updates with the default graphical package manager in all release-blocking desktops." This seems violated for KDE: checking for updates on a system where updates are definitely available results in a PackageKit crash and KDE claiming the system is up to date.
Thanks for your support to this problem... It's appreciated.
Do I have to mark this as publicly viewable or can you do that?
I did it already.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.
Should be a dupe of https://bugzilla.redhat.com/show_bug.cgi?id=1460825 and already fixed in PackageKit-1.1.6-2.fc26
Indeed, looking at the most recent time this test ran in openQA, it did fail, but only due to what looks like a screenshot mismatch; the logs show no trace of the crash happening.
*** This bug has been marked as a duplicate of bug 1460825 ***