Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
abrt version: 1.1.13
architecture: x86_64
cmdline: /usr/sbin/packagekitd
component: PackageKit
crash_function: pthread_mutex_lock
executable: /usr/sbin/packagekitd
reason: Process /usr/sbin/packagekitd was killed by signal 11 (SIGSEGV)
Version-Release number of selected component (if applicable):
kernel: 2.6.32-71.14.1.el6.x86_64
package: PackageKit-0.5.8-13.el6
Red Hat Enterprise Linux Server release 6.0 (Santiago)
How reproducible:
Random crash
Steps to Reproduce:
1.
2.
3.
Actual results:
Application packagekit was killed.
Expected results:
Application packagekit should not killed.
Additional info:
This bug was not resolved before development freeze. We are now making preparations for the launch of 6.1 and are only accepting critical and high impact bugs. We're reflagging this bug for 6.2 to continue the review and work needed to resolve this bug.