Bug 1661482

Summary: [abrt] xfce4-panel: magazine_chain_pop_head(): wrapper-2.0 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Pavel Alexeev <pahan>
Component: garconAssignee: Kevin Fenzi <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: kevin, mhroncok, nonamedotc, orion, projects.rg
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/97f4a62eef2eaf72057f8f0894c849f468ae268a
Whiteboard: abrt_hash:7b66e695f8dd121f6c17d1b9fd1fe6d9e804c1db;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-27 21:12:39 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: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Pavel Alexeev 2018-12-21 10:42:50 UTC
Version-Release number of selected component:
xfce4-panel-4.13.3-20.fc29

Additional info:
reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libwhiskermenu.so 16 14680071 whiskermenu Whisker Menu Show a menu to easily access installed applications
crash_function: magazine_chain_pop_head
executable:     /usr/lib64/xfce4/panel/wrapper-2.0
journald_cursor: s=2fdb562f15df4e619ce2ff5859a07ac5;i=268d5;b=ad2dde79637743cfa003a443e9a564c9;m=3648152492;t=57d85d72e4521;x=1a8ca9c5025f93d5
kernel:         4.19.9-300.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 magazine_chain_pop_head at gslice.c:538
 #1 thread_memory_magazine1_alloc at gslice.c:841
 #2 g_slice_alloc at gslice.c:1015
 #3 g_list_copy_deep at glist.c:693
 #4 g_list_copy at glist.c:636
 #5 garcon_menu_item_reload_from_file at garcon-menu-item.c:1113
 #6 garcon_menu_item_reload at garcon-menu-item.c:961
 #7 garcon_menu_process_file_changes at garcon-menu.c:2274
 #13 gtk_main at gtkmain.c:1323

Comment 1 Pavel Alexeev 2018-12-21 10:42:53 UTC
Created attachment 1516081 [details]
File: backtrace

Comment 2 Pavel Alexeev 2018-12-21 10:42:54 UTC
Created attachment 1516082 [details]
File: cgroup

Comment 3 Pavel Alexeev 2018-12-21 10:42:55 UTC
Created attachment 1516083 [details]
File: core_backtrace

Comment 4 Pavel Alexeev 2018-12-21 10:42:56 UTC
Created attachment 1516084 [details]
File: cpuinfo

Comment 5 Pavel Alexeev 2018-12-21 10:42:57 UTC
Created attachment 1516085 [details]
File: dso_list

Comment 6 Pavel Alexeev 2018-12-21 10:42:59 UTC
Created attachment 1516086 [details]
File: environ

Comment 7 Pavel Alexeev 2018-12-21 10:43:00 UTC
Created attachment 1516087 [details]
File: exploitable

Comment 8 Pavel Alexeev 2018-12-21 10:43:01 UTC
Created attachment 1516088 [details]
File: limits

Comment 9 Pavel Alexeev 2018-12-21 10:43:02 UTC
Created attachment 1516089 [details]
File: maps

Comment 10 Pavel Alexeev 2018-12-21 10:43:04 UTC
Created attachment 1516090 [details]
File: mountinfo

Comment 11 Pavel Alexeev 2018-12-21 10:43:05 UTC
Created attachment 1516091 [details]
File: open_fds

Comment 12 Pavel Alexeev 2018-12-21 10:43:06 UTC
Created attachment 1516092 [details]
File: proc_pid_status

Comment 13 Mukundan Ragavan 2018-12-21 12:40:53 UTC
What were you doing when this happened?

Comment 14 Raphael Groner 2018-12-22 11:05:42 UTC
The provided backtrace indicates garcon failed try to reload an image or icon for whiskermenu.
Maybe it's better to blame something in between the components garcon or whiskermenu. Reassigning.

Comment 15 Raphael Groner 2019-01-30 19:21:53 UTC
Obviously another duplication of bug #1670582.

Comment 16 Raphael Groner 2019-01-30 19:23:16 UTC
Duplication of bug #1667495, following.

Comment 17 Miro HronĨok 2019-02-26 19:54:07 UTC
This happens during dnf upgrade. A joined report of xfce4-panel, xfce4-appfinder and xfdesktop. I've observed a short restart of the components.

No xfce component got updated, so I guess it might have been the apps menu during one of the .desktop files update.

Comment 18 Ben Cotton 2019-10-31 19:54:41 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 19 Ben Cotton 2019-11-27 21:12:39 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.