Created attachment 1364947 [details]
File: backtrace

Created attachment 1364948 [details]
File: cgroup

Created attachment 1364949 [details]
File: core_backtrace

Created attachment 1364950 [details]
File: cpuinfo

Created attachment 1364951 [details]
File: dso_list

Created attachment 1364952 [details]
File: environ

Created attachment 1364953 [details]
File: limits

Created attachment 1364954 [details]
File: maps

Created attachment 1364955 [details]
File: mountinfo

Created attachment 1364956 [details]
File: open_fds

Created attachment 1364957 [details]
File: proc_pid_status

Created attachment 1364958 [details]
File: var_log_messages

*** Bug 1530234 has been marked as a duplicate of this bug. ***

*** Bug 1541405 has been marked as a duplicate of this bug. ***

*** Bug 1541725 has been marked as a duplicate of this bug. ***

*** Bug 1544874 has been marked as a duplicate of this bug. ***

*** Bug 1560810 has been marked as a duplicate of this bug. ***

*** Bug 1564521 has been marked as a duplicate of this bug. ***

*** Bug 1572847 has been marked as a duplicate of this bug. ***

*** Bug 1572864 has been marked as a duplicate of this bug. ***

Similar problem has been detected:

I had a number of PackageKit crashes. They were suspiciouslly correlated with me running dnf and getting
messages like this (dnf was able to proceed though):


  Verifying        : ed-1.14.1-4.fc27.x86_64                                                                                                    11/11 
warning: rpmdb: BDB2053 Freeing read locks for locker 0xb1b: 25548/139704017169792
warning: rpmdb: BDB2053 Freeing read locks for locker 0xb1d: 25548/139704017169792

Removed:
  google-chrome-stable.x86_64 66.0.3359.139-1    redhat-lsb-core.x86_64 4.1-36.fc27                 ed.x86_64 1.14.1-4.fc27                         

reporter:       libreport-2.9.3
backtrace_rating: 4
cmdline:        /usr/libexec/packagekitd
crash_function: solv_realloc
executable:     /usr/libexec/packagekitd
journald_cursor: s=ddb71857e8644e29aeb10a243da65d6a;i=58bbf1;b=93c6e00a23ac44e1a0172d6eb500c68a;m=13715538ba;t=56b35f76d904c;x=947ade6d635c5ed4
kernel:         4.16.4-200.fc27.x86_64
package:        PackageKit-1.1.10-1.fc27
reason:         packagekitd killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

*** Bug 1576355 has been marked as a duplicate of this bug. ***

*** Bug 1595348 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.