Bug 1460825

Summary: [abrt] PackageKit: pk_backend_refresh_cache_thread(): packagekitd killed by signal 11
Product: [Fedora] Fedora Reporter: Daniel <code>
Component: PackageKitAssignee: Richard Hughes <rhughes>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: code, eugenemah, grgoffe, jonathan, klember, michal.halenka, mustafa1024m, orti1980, rdieter, rhughes, robatino, smparrish, vindicators
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ab4d0ad2220fb12c2a2b40e0c685c581cbb2c4f9
Whiteboard: abrt_hash:90da674552b0497a9f49eb88fb772311c8ef5785;VARIANT_ID=workstation;
Fixed In Version: PackageKit-1.1.6-2.fc26 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-17 19:43:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1396702    
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Daniel 2017-06-12 22:11:41 UTC
Description of problem:
Crash every time I run `pkcon refresh`.

Version-Release number of selected component:
PackageKit-1.1.6-1.fc26

Additional info:
reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/packagekitd
crash_function: pk_backend_refresh_cache_thread
executable:     /usr/libexec/packagekitd
journald_cursor: s=0fa1f239b1794f89889dfeb23027acbc;i=1f48b;b=3d1f6cbaeedc401f8162bdd9c7ff304e;m=e106870ee;t=551c87c4b8b39;x=7ced7cc4e49b472a
kernel:         4.11.4-300.fc26.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
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

Potential duplicate: bug 1114207

Comment 1 Daniel 2017-06-12 22:11:48 UTC
Created attachment 1287104 [details]
File: backtrace

Comment 2 Daniel 2017-06-12 22:11:49 UTC
Created attachment 1287105 [details]
File: cgroup

Comment 3 Daniel 2017-06-12 22:11:51 UTC
Created attachment 1287106 [details]
File: core_backtrace

Comment 4 Daniel 2017-06-12 22:11:52 UTC
Created attachment 1287107 [details]
File: cpuinfo

Comment 5 Daniel 2017-06-12 22:11:54 UTC
Created attachment 1287108 [details]
File: dso_list

Comment 6 Daniel 2017-06-12 22:11:56 UTC
Created attachment 1287109 [details]
File: environ

Comment 7 Daniel 2017-06-12 22:11:58 UTC
Created attachment 1287110 [details]
File: exploitable

Comment 8 Daniel 2017-06-12 22:11:59 UTC
Created attachment 1287111 [details]
File: limits

Comment 9 Daniel 2017-06-12 22:12:02 UTC
Created attachment 1287112 [details]
File: maps

Comment 10 Daniel 2017-06-12 22:12:04 UTC
Created attachment 1287113 [details]
File: open_fds

Comment 11 Daniel 2017-06-12 22:12:06 UTC
Created attachment 1287114 [details]
File: proc_pid_status

Comment 12 Daniel 2017-06-12 22:12:07 UTC
Created attachment 1287115 [details]
File: var_log_messages

Comment 13 Eugene Mah 2017-06-14 09:45:24 UTC
Similar problem has been detected:

Logged into my computer. Notification was displayed that PackageKit quit unexpectedly.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/packagekitd
crash_function: pk_backend_refresh_cache_thread
executable:     /usr/libexec/packagekitd
journald_cursor: s=fc22d2cbec5e4b95af3cda0296001c74;i=177a6a;b=7f5a6e0a1ec84c1aa930e81bb9134963;m=3c68dfa8;t=551bfd6e9384f;x=27d24d6edab72c26
kernel:         4.11.3-302.fc26.x86_64
package:        PackageKit-1.1.6-1.fc26
reason:         packagekitd killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Comment 14 Michal Halenka 2017-06-14 09:58:33 UTC
*** Bug 1461362 has been marked as a duplicate of this bug. ***

Comment 15 Richard Hughes 2017-06-15 08:46:38 UTC
Are there any critical warnings in the journal? I can't see how dnf_state_done() can be returning FALSE and not setting the error. Thanks.

Comment 16 Eugene Mah 2017-06-15 09:44:40 UTC
Similar problem has been detected:

Logged in to my computer and a crash notification appeared.

reporter:       libreport-2.9.1
backtrace_rating: 4
cmdline:        /usr/libexec/packagekitd
crash_function: pk_backend_refresh_cache_thread
executable:     /usr/libexec/packagekitd
journald_cursor: s=fc22d2cbec5e4b95af3cda0296001c74;i=17c0a3;b=44852a3e95b84cdf8a663363dd5faa62;m=a5c7eb60;t=551e880e975fa;x=26fd60f3d0caba7c
kernel:         4.11.4-300.fc26.x86_64
package:        PackageKit-1.1.6-1.fc26
reason:         packagekitd killed by signal 11
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Comment 17 Fedora Update System 2017-06-15 13:12:15 UTC
PackageKit-1.1.6-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-7f91d69342

Comment 18 orti1980 2017-06-16 20:53:46 UTC
*** Bug 1462366 has been marked as a duplicate of this bug. ***

Comment 19 Fedora Update System 2017-06-16 22:24:00 UTC
PackageKit-1.1.6-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-7f91d69342

Comment 20 Fedora Update System 2017-06-17 19:43:24 UTC
PackageKit-1.1.6-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.

Comment 21 Adam Williamson 2017-08-21 17:09:10 UTC
*** Bug 1464556 has been marked as a duplicate of this bug. ***

Comment 22 Red Hat Bugzilla 2023-09-14 03:59:03 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days