Bug 1707500

Created attachment 1565273 [details]
File: backtrace

Created attachment 1565274 [details]
File: cgroup

Created attachment 1565275 [details]
File: core_backtrace

Created attachment 1565276 [details]
File: cpuinfo

Created attachment 1565277 [details]
File: dso_list

Created attachment 1565278 [details]
File: environ

Created attachment 1565279 [details]
File: limits

Similar problem has been detected:

The first thing that happened after login. Had not started anything yet, got the crash report just as the desktop was shown.

reporter:       libreport-2.10.0
backtrace_rating: 3
cmdline:        /usr/bin/python3 /usr/bin/dnfdragora-updater
crash_function: g_log_structured_standard
executable:     /usr/bin/python3.7
journald_cursor: s=ff944e9c0cf045879833dd994fdff1b3;i=22db6e;b=5432bf0c411a46828a4000caa7f74445;m=3ca38e0;t=5884e62231f9e;x=51dee250d99438cd
kernel:         5.0.11-300.fc30.x86_64
package:        dnfdragora-updater-1.1.1-2.fc30
reason:         python3.7 killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

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

I faced this bug, too.

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

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

For me, a crashing dnfdragora-updater sometimes also causes a crash of xfce4-panel:
bug 1684753
bug 1683838

Similar problem has been detected:

This happened very shortly after the system started up.  There was no user interaction to that point.

reporter:       libreport-2.10.0
backtrace_rating: 3
cmdline:        /usr/bin/python3 /usr/bin/dnfdragora-updater
crash_function: g_log_structured_standard
executable:     /usr/bin/python3.7
journald_cursor: s=a9576ec9e38b4305bb466ba90a57db1c;i=aa27;b=2733671249994707897a71d7bedce3ac;m=21ff3b9;t=58d5afa97b11b;x=3b0db2f37cc851ad
kernel:         5.1.16-300.fc30.x86_64
package:        dnfdragora-updater-1.1.1-2.fc30
reason:         python3.7 killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

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

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

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

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

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

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

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

Similar problem has been detected:

I recieved the notification that there were updates and then I clicked on the notification icon and it crashed.

reporter:       libreport-2.10.1
backtrace_rating: 3
cmdline:        /usr/bin/python3 /usr/bin/dnfdragora-updater
crash_function: g_log_structured_standard
executable:     /usr/bin/python3.7
journald_cursor: s=846a68892c13473b8cfe667154794f69;i=32859;b=ddba8f24be06468cb13f0a102192541b;m=129d8905;t=5946fde8b4f9c;x=1d3272799f6b04ad
kernel:         5.2.17-200.fc30.x86_64
package:        dnfdragora-updater-1.1.1-2.fc30
reason:         python3.7 killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Similar problem has been detected:

I was trying to bring up the dnfdragora user interface.

reporter:       libreport-2.11.3
backtrace_rating: 3
cmdline:        /usr/bin/python3 /usr/bin/dnfdragora-updater
crash_function: g_log_structured_standard
executable:     /usr/bin/python3.7
journald_cursor: s=20a66e5cb99c4641b474ac797704cee5;i=491c21;b=8c6ed1f2221f4ccd85bc7b195685c430;m=3fd9892;t=59c924b7db1c0;x=b0a45ffe69bcee03
kernel:         5.4.10-100.fc30.x86_64
package:        dnfdragora-updater-1.1.1-2.fc30
reason:         python3.7 killed by SIGTRAP
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000
xsession_errors:

Please test 2.0.x version

This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-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 '30'.

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

No problem.

I've not been reporting these python errors for quite a while, seeing all the duplicates and generally lack of action.  I haven't even seen any suggestions on how to gather more information.  For me, dnfdragora fails in roughly one of every four start-ups.

I'll resume reporting this failure mode after I upgrade to Fedora 32.