Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1679815 - [abrt] xfdesktop: garcon_menu_item_set_action(): xfdesktop killed by SIGSEGV
Summary: [abrt] xfdesktop: garcon_menu_item_set_action(): xfdesktop killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xfdesktop
Version: 29
Hardware: x86_64
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:19d99e4784c7a6263c928f84380...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-21 22:37 UTC by Jeremy Harris
Modified: 2019-11-27 18:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-27 18:15:38 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (26.04 KB, text/plain)
2019-02-21 22:37 UTC, Jeremy Harris 		no flags Details
File: cgroup (349 bytes, text/plain)
2019-02-21 22:37 UTC, Jeremy Harris 		no flags Details
File: core_backtrace (8.49 KB, text/plain)
2019-02-21 22:37 UTC, Jeremy Harris 		no flags Details
File: cpuinfo (1.42 KB, text/plain)
2019-02-21 22:37 UTC, Jeremy Harris 		no flags Details
File: dso_list (10.61 KB, text/plain)
2019-02-21 22:37 UTC, Jeremy Harris 		no flags Details
File: environ (1.38 KB, text/plain)
2019-02-21 22:37 UTC, Jeremy Harris 		no flags Details
File: exploitable (82 bytes, text/plain)
2019-02-21 22:37 UTC, Jeremy Harris 		no flags Details
File: limits (1.29 KB, text/plain)
2019-02-21 22:37 UTC, Jeremy Harris 		no flags Details
File: maps (70.49 KB, text/plain)
2019-02-21 22:37 UTC, Jeremy Harris 		no flags Details
File: mountinfo (4.13 KB, text/plain)
2019-02-21 22:37 UTC, Jeremy Harris 		no flags Details
File: open_fds (3.42 KB, text/plain)
2019-02-21 22:37 UTC, Jeremy Harris 		no flags Details
File: proc_pid_status (1.31 KB, text/plain)
2019-02-21 22:37 UTC, Jeremy Harris 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1672521 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 1674221 0 unspecified CLOSED [abrt] xfce4-panel: g_type_check_instance_cast(): wrapper-2.0 killed by SIGSEGV 2022-05-16 11:32:56 UTC

Internal Links: 1674221

Description Jeremy Harris 2019-02-21 22:37:38 UTC 
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
Comment 1 Jeremy Harris 2019-02-21 22:37:41 UTC 
Created attachment 1537237 [details]
File: backtrace
Comment 2 Jeremy Harris 2019-02-21 22:37:42 UTC 
Created attachment 1537238 [details]
File: cgroup
Comment 3 Jeremy Harris 2019-02-21 22:37:43 UTC 
Created attachment 1537239 [details]
File: core_backtrace
Comment 4 Jeremy Harris 2019-02-21 22:37:44 UTC 
Created attachment 1537240 [details]
File: cpuinfo
Comment 5 Jeremy Harris 2019-02-21 22:37:45 UTC 
Created attachment 1537241 [details]
File: dso_list
Comment 6 Jeremy Harris 2019-02-21 22:37:46 UTC 
Created attachment 1537242 [details]
File: environ
Comment 7 Jeremy Harris 2019-02-21 22:37:47 UTC 
Created attachment 1537243 [details]
File: exploitable
Comment 8 Jeremy Harris 2019-02-21 22:37:48 UTC 
Created attachment 1537244 [details]
File: limits
Comment 9 Jeremy Harris 2019-02-21 22:37:50 UTC 
Created attachment 1537245 [details]
File: maps
Comment 10 Jeremy Harris 2019-02-21 22:37:51 UTC 
Created attachment 1537246 [details]
File: mountinfo
Comment 11 Jeremy Harris 2019-02-21 22:37:52 UTC 
Created attachment 1537247 [details]
File: open_fds
Comment 12 Jeremy Harris 2019-02-21 22:37:53 UTC 
Created attachment 1537248 [details]
File: proc_pid_status
Comment 13 Miro Hrončok 2019-03-09 23:08:00 UTC 
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
Comment 14 Lonni J Friedman 2019-06-21 23:15:54 UTC 
I'm also seeing this problem whenever 'dnf update' is running.
Comment 15 Ben Cotton 2019-10-31 19:06:26 UTC 
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.
Comment 16 Lonni J Friedman 2019-11-01 00:11:44 UTC 
Super great.  Open over 8 months, no attention from Fedora, and now they want to close it out.
Comment 17 Miro Hrončok 2019-11-01 06:11:10 UTC 
For what it's worth, I haven't seen this for a long time Fedora 30.
Comment 18 Lonni J Friedman 2019-11-01 23:42:41 UTC 
I see it every time that I run 'dnf update'.
Comment 19 Ben Cotton 2019-11-27 18:15:38 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.