Version-Release number of selected component:
cmdline: /usr/bin/python3 /usr/bin/dnfdragora-updater
runlevel: N 5
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
Created attachment 1614068 [details]
Created attachment 1614069 [details]
Created attachment 1614070 [details]
Created attachment 1614071 [details]
Created attachment 1614072 [details]
Created attachment 1614073 [details]
Created attachment 1614074 [details]
Created attachment 1614075 [details]
Created attachment 1614076 [details]
Created attachment 1614077 [details]
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#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
There already has been some related discussion about blocker: bug 1750575
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.
We already signed off the F31 release. There can't be any new blockers now.
*** Bug 1768856 has been marked as a duplicate of this bug. ***