Bug 1765909 - [abrt] dnfdragora-updater: g_log_structured_standard(): python3.7 killed by SIGTRAP
Summary: [abrt] dnfdragora-updater: g_log_structured_standard(): python3.7 killed by S...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: dnfdragora
Version: 30
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Neal Gompa
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:3eee4351b835388a5481fc3fe30...
: 1806569 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-27 09:47 UTC by Woi
Modified: 2020-05-26 18:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-26 18:21:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (92.89 KB, text/plain)
2019-10-27 09:47 UTC, Woi
no flags Details
File: cgroup (331 bytes, text/plain)
2019-10-27 09:47 UTC, Woi
no flags Details
File: core_backtrace (32.37 KB, text/plain)
2019-10-27 09:47 UTC, Woi
no flags Details
File: cpuinfo (1.33 KB, text/plain)
2019-10-27 09:47 UTC, Woi
no flags Details
File: dso_list (19.99 KB, text/plain)
2019-10-27 09:47 UTC, Woi
no flags Details
File: environ (1.14 KB, text/plain)
2019-10-27 09:47 UTC, Woi
no flags Details
File: limits (1.29 KB, text/plain)
2019-10-27 09:47 UTC, Woi
no flags Details
File: maps (115.25 KB, text/plain)
2019-10-27 09:47 UTC, Woi
no flags Details
File: mountinfo (3.32 KB, text/plain)
2019-10-27 09:47 UTC, Woi
no flags Details
File: open_fds (1.15 KB, text/plain)
2019-10-27 09:47 UTC, Woi
no flags Details
File: proc_pid_status (1.32 KB, text/plain)
2019-10-27 09:47 UTC, Woi
no flags Details

Description Woi 2019-10-27 09:47:22 UTC
Description of problem:
The "usual" dnfdragora-updater crash, but this time it crashed shortly after login to xfce. Before, crashes occured "only" after closing the application, thus giving the opportunity to update the system.
Should it stay this way, the default way to update some spins (all but Gnome and KDE?) became unusable. As far as I can see, this could be a violation of release criteria. Namely:
https://fedoraproject.org/wiki/Fedora_31_Final_Release_Criteria#Update_notification
https://fedoraproject.org/wiki/Fedora_31_Final_Release_Criteria#SELinux_and_crash_notifications (As reported before: I had a crash of dnfdragora-updater during my first login after a fresh install of FC30)


Version-Release number of selected component:
dnfdragora-updater-1.1.1-2.fc30

Additional info:
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=5461b4e428474a318d2ae73ed5b2ad37;i=8afc;b=de42645b8980401fa7e725cd71b856cd;m=176269c1;t=595e0ac5573a3;x=f7d9720efe922689
kernel:         5.3.7-200.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Potential duplicate: bug 1751196

Comment 1 Woi 2019-10-27 09:47:26 UTC
Created attachment 1629530 [details]
File: backtrace

Comment 2 Woi 2019-10-27 09:47:27 UTC
Created attachment 1629531 [details]
File: cgroup

Comment 3 Woi 2019-10-27 09:47:29 UTC
Created attachment 1629532 [details]
File: core_backtrace

Comment 4 Woi 2019-10-27 09:47:30 UTC
Created attachment 1629533 [details]
File: cpuinfo

Comment 5 Woi 2019-10-27 09:47:31 UTC
Created attachment 1629534 [details]
File: dso_list

Comment 6 Woi 2019-10-27 09:47:33 UTC
Created attachment 1629535 [details]
File: environ

Comment 7 Woi 2019-10-27 09:47:34 UTC
Created attachment 1629536 [details]
File: limits

Comment 8 Woi 2019-10-27 09:47:36 UTC
Created attachment 1629537 [details]
File: maps

Comment 9 Woi 2019-10-27 09:47:37 UTC
Created attachment 1629538 [details]
File: mountinfo

Comment 10 Woi 2019-10-27 09:47:38 UTC
Created attachment 1629539 [details]
File: open_fds

Comment 11 Woi 2019-10-27 09:47:39 UTC
Created attachment 1629540 [details]
File: proc_pid_status

Comment 12 Woi 2019-10-27 10:00:32 UTC
Potential duplicate of bug 1751196
Tracking bug should be most likely bug 1667903

Comment 13 louisclain 2020-02-24 14:41:39 UTC
*** Bug 1806569 has been marked as a duplicate of this bug. ***

Comment 14 Ben Cotton 2020-04-30 20:24:34 UTC
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.

Comment 15 Ben Cotton 2020-05-26 18:21:38 UTC
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.


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