Bug 1576086

Created attachment 1433390 [details]
File: backtrace

Created attachment 1433391 [details]
File: cgroup

Created attachment 1433392 [details]
File: core_backtrace

Created attachment 1433393 [details]
File: cpuinfo

Created attachment 1433394 [details]
File: dso_list

Created attachment 1433395 [details]
File: environ

Created attachment 1433396 [details]
File: limits

Created attachment 1433397 [details]
File: maps

Created attachment 1433398 [details]
File: mountinfo

Created attachment 1433399 [details]
File: open_fds

Created attachment 1433400 [details]
File: proc_pid_status

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

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

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

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

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

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

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

Similar problem has been detected:

Just opened the window from the taskbar button

reporter:       libreport-2.9.5
backtrace_rating: 4
cmdline:        /usr/bin/python3 /usr/bin/dnfdragora-updater
crash_function: Py_FatalError
executable:     /usr/bin/python3.6
journald_cursor: s=0ba28a64a14d4ff78a8ad5daa561135f;i=93124;b=64a5a72925554e41a41e0190eea46003;m=46ec88f;t=57950eb79881a;x=3caf22e5ba853c47
kernel:         4.18.16-200.fc28.x86_64
package:        dnfdragora-updater-1.0.1-10.git20180108.b0e8a66.fc28
reason:         python3.6 killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            5078

Created attachment 1498380 [details]
File: backtrace

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

Similar problem has been detected:

Running dnfdragora to perform updates.
I almost always pick packages to update separately so that bugs or failures may have less scope for corrupting rpmdb or the installed packages themselves.
Dnfdragora may sometimes crash after picking and upgrading several cycles.
Also dnfdaemon has a very bad memory leak with the process growing 100s of kilobytes each package upgrade cycle.

reporter:       libreport-2.9.5
backtrace_rating: 3
cmdline:        /usr/bin/python3 /usr/bin/dnfdragora
crash_function: Py_FatalError
executable:     /usr/bin/python3.6
journald_cursor: s=259d8b6dc0d34129b558891afd5f6478;i=a773;b=5fc3cf5298164a8998772f8f8a9715ad;m=6bc25792;t=57c3e15821840;x=d5a60b5f1f2f8ca2
kernel:         4.19.3-200.fc28.x86_64
package:        dnfdragora-1.0.1-10.git20180108.b0e8a66.fc28
reason:         python3.6 killed by SIGABRT
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

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

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

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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

This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.