Bug 1628797 - PK-Backend: segfault at 48 ip 00007f6dc6707908 sp 00007f6dc4b08958 error 4 in libdnf.so.2
Summary: PK-Backend: segfault at 48 ip 00007f6dc6707908 sp 00007f6dc4b08958 error 4 in...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-14 02:46 UTC by Chris Murphy
Modified: 2019-11-27 19:27 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-11-27 19:27:25 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journal snippet (35.47 KB, text/plain)
2018-09-14 02:48 UTC, Chris Murphy
no flags Details
coredumpctl gdb, thread apply all bt full (23.06 KB, text/plain)
2018-09-14 02:48 UTC, Chris Murphy
no flags Details

Description Chris Murphy 2018-09-14 02:46:27 UTC
Description of problem:

Soon after a dnf update and dnf remove to clean out older kernels, I'm getting a crash in PK-Backend reported in abrt and in the journal.


Version-Release number of selected component (if applicable):

PackageKit-1.1.10-4.fc29.x86_64
dnf-3.3.0-2.fc29.noarch
libdnf-0.17.2-1.fc29.x86_64



How reproducible:
1 for 1


Steps to Reproduce:
1. sudo dnf update
2. sudo dnf remove <list of kernel packages>
3.

Actual results:

Crash ~minutes of last dnf completing


Expected results:

No crash

Additional info:

Comment 1 Chris Murphy 2018-09-14 02:48:23 UTC
Created attachment 1483193 [details]
journal snippet

journalctl -o short-monotonic, for the time frame starting from dnf update through the crash.

Comment 2 Chris Murphy 2018-09-14 02:48:59 UTC
Created attachment 1483194 [details]
coredumpctl gdb, thread apply all bt full

Comment 3 Ben Cotton 2019-10-31 20:42:24 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 '29'.

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 29 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.

Comment 4 Ben Cotton 2019-11-27 19:27:25 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.


Note You need to log in before you can comment on or make changes to this bug.