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.

Bug 1684270

Summary: [hawkey] occasional segfault when interrupting (SIGINT) dnf process (may be caused by particular plugins in use, e.g. "leaves" ones in the past)
Product: Red Hat Enterprise Linux 8 Reporter: Jan Pokorný [poki] <jpokorny>
Component: libdnfAssignee: amatej
Status: CLOSED ERRATA QA Contact: Karel Srot <ksrot>
Severity: unspecified Docs Contact:
Priority: high    
Version: 8.0CC: amatej, dmach, extras-qa, jmracek, mluscon, rpm-software-management
Target Milestone: rcKeywords: Triaged
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libdnf-0.33.0-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1610456 Environment:
Last Closed: 2019-11-05 22:21:13 UTC Type: Bug
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: 1610456    
Bug Blocks:    

Description Jan Pokorný [poki] 2019-02-28 20:41:06 UTC
Have hit the same:

+++ This bug was initially created as a clone of Bug #1610456 +++

with pre GA 8.0 as well, sadly it was in systemd-nspawn container so
I have very little info to provide:

- it was, IIRC, during "dnf update *.rpm"
  (was located in a directory I wanted to update packages from)
  and again, I realized that I want to cancel that transaction for now

- default configuration (all installed plugin presumably enabled):

# find /usr/lib*/python3.6/site-packages/dnf-plugins/* -print0 \
  | xargs -0 rpm -qf | sort -u
> python3-dnf-4.0.9.2-5.el8.noarch
> python3-dnf-plugins-core-4.0.2.2-3.el8.noarch

- on the host in the journal/dmesg:

> kernel: dnf[12953]: segfault at 8 ip 00007f954d937d51 sp 00007fffa628feb0 error 4 in libpython3.6m.so.1.0[7f954d833000+2bf000]
> kernel: Code: a0 03 00 00 41 c7 84 24 94 03 00 00 02 00 00 00 e9 c9 fb ff ff e8 2f 99 f5 ff e9 98 b9 f6 ff 48 83 c3 01 e9 74 fb ff ff 90 53 <48> 8b 47 08 48 89 fb 48 8b 80 d8 00 00 00 48 85 c0 74 28 ff d0 48

- packages in the container:

# rpm -q dnf rpm libdnf librepo libsolv
> dnf-4.0.9.2-5.el8.noarch
> rpm-4.14.2-9.el8.x86_64
> libdnf-0.22.5-4.el8.x86_64
> librepo-1.9.2-1.el8.x86_64
> libsolv-0.6.35-6.el8.x86_64

# rpm -qf /usr/lib64/libpython3.6m.so.1.0
> python3-libs-3.6.8-1.el8.x86_64

Comment 1 amatej 2019-03-29 14:25:54 UTC
created PR: https://github.com/rpm-software-management/libdnf/pull/694

Comment 6 errata-xmlrpc 2019-11-05 22:21:13 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3583