Bug 1765718
Summary: | DNF segmentation fault | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | SP <scp.stjohn> |
Component: | dnf | Assignee: | Lukáš Hrázký <lhrazky> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 30 | CC: | dmach, jmracek, jrohel, lhrazky, mblaha, mhatina, packaging-team-maint, pkratoch, rpm-software-management, vmukhame |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-10-31 07:42:24 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: |
Description
SP
2019-10-25 19:53:51 UTC
Hello, any insight on why the core is not dumped? On Fedora 30 by default core dumps should be handled by systemd-coredump. What dnf commands are you running? Are you updating the system? From what you're saying I'm getting the impression you have multiple systems and are updating them? What is the version of libdnf? If you are updating, what are the versions before and after? It may be caused by this problem: https://bugzilla.redhat.com/show_bug.cgi?id=1758737 Which was fixed in libdnf-0.35.5-4. The segfault no longer occurs. It occurred in two previous dnf updates on four different machines each running the same OS and Desktop Fedora 30 with KDE Plasma. Current Kernel version is now 5.3.7-200.fc30.x86_64 with KDE Plasma Version 5.15.5 Current libdbf version is 0.35.5-4.fc30 I should have checked the OS status when the segfault occurred. I guess the last update must have fixed it. Dnf update is run every day to check for updates. Dnf is run with sudo dnf update -vvv -y Thanks. There's little to go by, but since it seems libdnf-0.35.5-4.fc30 fixed your issue, I think it is most likely the log handler issue and I'm marking this as a duplicate of that. *** This bug has been marked as a duplicate of bug 1758737 *** |