Bug 1751196

Summary: [abrt] dnfdragora-updater: g_log_structured_standard(): python3.7 killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Mike FABIAN <mfabian>
Component: dnfdragoraAssignee: Neal Gompa <ngompa13>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: awilliam, besser82, galaktoid1995, half666, ngompa13, woiling
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/adf0232fb0f311ed55bfef2557b96a0b409e37b2
Whiteboard: abrt_hash:3eee4351b835388a5481fc3fe303f70c75654b14;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-24 18:07:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Mike FABIAN 2019-09-11 11:35:58 UTC 
Version-Release number of selected component:
dnfdragora-updater-1.1.1-3.fc31

Additional info:
reporter:       libreport-2.10.1
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/session-5.scope
cmdline:        /usr/bin/python3 /usr/bin/dnfdragora-updater
crash_function: g_log_structured_standard
executable:     /usr/bin/python3.7
journald_cursor: s=ec62f368ed7742acb693d2f1599e4c73;i=bc15;b=05dbe149ac7445a1b88ee4c43300beb0;m=77e818a;t=592451f61c4be;x=2f5c78d03e494d56
kernel:         5.3.0-0.rc6.git0.1.fc31.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 g_log_structured_standard at ../glib/gmessages.c:1982
 #13 XFlush at Flush.c:39
 #14 gtk_tray_icon_update_manager_window at deprecated/gtktrayicon-x11.c:849
 #15 gtk_tray_icon_constructed at deprecated/gtktrayicon-x11.c:265
 #16 g_object_new_internal at ../gobject/gobject.c:1867
 #17 g_object_new_valist at ../gobject/gobject.c:2152
 #19 _gtk_tray_icon_new at deprecated/gtktrayicon-x11.c:1084
 #20 gtk_status_icon_init at deprecated/gtkstatusicon.c:883
 #21 g_type_create_instance at ../gobject/gtype.c:1867
 #22 g_object_new_internal at ../gobject/gobject.c:1827
Comment 1 Mike FABIAN 2019-09-11 11:36:02 UTC 
Created attachment 1614068 [details]
File: backtrace
Comment 2 Mike FABIAN 2019-09-11 11:36:05 UTC 
Created attachment 1614069 [details]
File: core_backtrace
Comment 3 Mike FABIAN 2019-09-11 11:36:06 UTC 
Created attachment 1614070 [details]
File: cpuinfo
Comment 4 Mike FABIAN 2019-09-11 11:36:08 UTC 
Created attachment 1614071 [details]
File: dso_list
Comment 5 Mike FABIAN 2019-09-11 11:36:09 UTC 
Created attachment 1614072 [details]
File: environ
Comment 6 Mike FABIAN 2019-09-11 11:36:10 UTC 
Created attachment 1614073 [details]
File: limits
Comment 7 Mike FABIAN 2019-09-11 11:36:14 UTC 
Created attachment 1614074 [details]
File: maps
Comment 8 Mike FABIAN 2019-09-11 11:36:15 UTC 
Created attachment 1614075 [details]
File: mountinfo
Comment 9 Mike FABIAN 2019-09-11 11:36:16 UTC 
Created attachment 1614076 [details]
File: open_fds
Comment 10 Mike FABIAN 2019-09-11 11:36:17 UTC 
Created attachment 1614077 [details]
File: proc_pid_status
Comment 11 Woi 2019-10-27 10:01:00 UTC 
I think my bug is a duplicate: bug 1765909

Looks like 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 in bug 1667903#c57: I had a crash of dnfdragora-updater during my first login after a fresh install of FC30)

Se also bug 1667903
Comment 12 Woi 2019-10-27 10:08:50 UTC 
There already has been some related discussion about blocker: bug 1750575
Comment 13 Fedora Blocker Bugs Application 2019-10-27 11:10:02 UTC 
Proposed as a Blocker for 31-final by Fedora user woi using the blocker tracking app because:

 Dnfdragora-updater is the default updater for some desktop spins (XFCE for sure, but likely for all desktops but Gnome and KDE).
It started to crash a while ago  (#1667903), but it's getting worth in frequency and now even in impact.
So it currently might violate two release criteria:
* Release-blocking desktops must notify the user of available updates. (Reason: Crash before showing update notification)
* There must be no [...] crash notifications [...] at first login after a default install of a release-blocking desktop

I looks  like it's getting more and more difficult to apply updates using dnfdragora-updater. See for example 1751196#c11 1667903#c57  or 1707500#c22 If this development continues, there is a risk of desktops ending up unable to update using the default tool during the life time of Fedora 31.

There has been already some discussion about release blocking or not in 1750575, but assumptions where that it's possible to still apply updates and that there is a bug fix.
There first seems to chance, while I'm not sure if the fix solves this issue.
Comment 14 Adam Williamson 2019-10-28 00:23:05 UTC 
We already signed off the F31 release. There can't be any new blockers now.
Comment 15 half666 2019-11-05 12:12:35 UTC 
*** Bug 1768856 has been marked as a duplicate of this bug. ***
Comment 16 Ben Cotton 2020-11-03 15:34:02 UTC 
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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 17 Woi 2020-11-03 17:02:19 UTC 
Haven't seen this in quite a while. I assume it has been fixed upstream.
Comment 18 Ben Cotton 2020-11-24 18:07:55 UTC 
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.