Description of problem: During a "dnf update". Version-Release number of selected component: xfdesktop-4.13.2-20.fc29 Additional info: reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: xfdesktop --display :0.0 --sm-client-id 23831a172-1ffa-4e00-9c38-d3e192dc447a crash_function: garcon_menu_item_set_action executable: /usr/bin/xfdesktop journald_cursor: s=5d5a3576fcbc4932b17a440dcc10a85e;i=7346;b=7c465d3c1d56461e9e7949a11972eb90;m=aebb002ef;t=5826f0dfd5295;x=353f2986329ba2e1 kernel: 4.20.8-200.fc29.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 garcon_menu_item_set_action at garcon-menu-item.c:1775 #1 garcon_menu_item_reload_from_file at garcon-menu-item.c:1183 #2 garcon_menu_item_reload at garcon-menu-item.c:961 #3 garcon_menu_process_file_changes at garcon-menu.c:2274 #9 gtk_main at gtkmain.c:1323 #10 xfdesktop_application_start at xfdesktop-application.c:764 #11 cb_wait_for_window_manager_destroyed at xfdesktop-application.c:587 #12 g_source_callback_unref at gmain.c:1551 #14 g_source_destroy_internal at gmain.c:1236 #18 g_main_context_iteration at gmain.c:3981
Created attachment 1537237 [details] File: backtrace
Created attachment 1537238 [details] File: cgroup
Created attachment 1537239 [details] File: core_backtrace
Created attachment 1537240 [details] File: cpuinfo
Created attachment 1537241 [details] File: dso_list
Created attachment 1537242 [details] File: environ
Created attachment 1537243 [details] File: exploitable
Created attachment 1537244 [details] File: limits
Created attachment 1537245 [details] File: maps
Created attachment 1537246 [details] File: mountinfo
Created attachment 1537247 [details] File: open_fds
Created attachment 1537248 [details] File: proc_pid_status
Similar problem has been detected: dnf update of unrelated packages with desktop files. xfce4-panel, xfce4-appfinder and xfesktop all killed and restarted together. reporter: libreport-2.10.0 backtrace_rating: 4 cmdline: xfdesktop --display :0.0 --sm-client-id 21acccd48-5898-4408-b404-67f390f0795b crash_function: garcon_menu_item_set_action executable: /usr/bin/xfdesktop journald_cursor: s=887eaaad8a374c5e9394ed1828070e0f;i=5e73c;b=8655ac0b108b4e24a388f54a7830afa0;m=2071d3ebb3;t=583b14d39a53b;x=3555a809adc3ef97 kernel: 4.20.12-200.fc29.x86_64 package: xfdesktop-4.13.2-20.fc29 reason: xfdesktop killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
I'm also seeing this problem whenever 'dnf update' is running.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'. 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 29 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.
Super great. Open over 8 months, no attention from Fedora, and now they want to close it out.
For what it's worth, I haven't seen this for a long time Fedora 30.
I see it every time that I run 'dnf update'.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.