Bug 1667495

Summary: [abrt] xfce4-panel: magazine_chain_pop_head(): xfce4-panel killed by SIGSEGV
Product: [Fedora] Fedora Reporter: mastaiza <mastaizawfm>
Component: gtk3Assignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 29CC: chiguy1256, cosimo.cecchi, david, eloranta, fukidid, gabriel.gass, geoffleach.gl, gnome-sig, hockmanj, kevin, maxime.tierre, mclasen, mhroncok, nonamedotc, projects.rg, stefan998, yetoohappy
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/d29ae633f08156bf2003a32233d6425e0aa9f502
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 22:43:49 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:
Bug Depends On:    
Bug Blocks: 1668484, 1671584    
Attachments:
Description Flags
File: backtrace
none
File: cgroup
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
File: exploitable none

Description mastaiza 2019-01-18 16:01:14 UTC
Version-Release number of selected component:
xfce4-panel-4.13.4-1.fc29

Additional info:
reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        xfce4-panel --display :0.0 --sm-client-id 2e8aeb63d-3bd5-4383-b423-57b7cc32390d
crash_function: magazine_chain_pop_head
executable:     /usr/bin/xfce4-panel
journald_cursor: s=ad3c26441fe342dd917e2e6c329dc81e;i=1aa1;b=50a008b9d32842b0965bfa5c8f5f2169;m=2e72cffb;t=57f5124e1a6dd;x=f413ab6306802a41
kernel:         4.19.13-300.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 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_prepend at glist.c:314
 #4 gtk_widget_add_tick_callback at gtkwidget.c:5321
 #5 gtk_css_widget_node_queue_validate at gtkcsswidgetnode.c:95
 #6 gtk_css_node_invalidate_style at gtkcssnode.c:727
 #7 gtk_css_node_invalidate at gtkcssnode.c:1372
 #8 gtk_css_node_invalidate_style_provider at gtkcssnode.c:1314
 #13 _gtk_style_provider_private_changed at gtkstyleproviderprivate.c:113

Comment 1 mastaiza 2019-01-18 16:01:18 UTC
Created attachment 1521580 [details]
File: backtrace

Comment 2 mastaiza 2019-01-18 16:01:19 UTC
Created attachment 1521581 [details]
File: cgroup

Comment 3 mastaiza 2019-01-18 16:01:21 UTC
Created attachment 1521582 [details]
File: core_backtrace

Comment 4 mastaiza 2019-01-18 16:01:22 UTC
Created attachment 1521583 [details]
File: cpuinfo

Comment 5 mastaiza 2019-01-18 16:01:24 UTC
Created attachment 1521584 [details]
File: dso_list

Comment 6 mastaiza 2019-01-18 16:01:25 UTC
Created attachment 1521585 [details]
File: environ

Comment 7 mastaiza 2019-01-18 16:01:26 UTC
Created attachment 1521586 [details]
File: limits

Comment 8 mastaiza 2019-01-18 16:01:28 UTC
Created attachment 1521587 [details]
File: maps

Comment 9 mastaiza 2019-01-18 16:01:29 UTC
Created attachment 1521588 [details]
File: mountinfo

Comment 10 mastaiza 2019-01-18 16:01:31 UTC
Created attachment 1521589 [details]
File: open_fds

Comment 11 mastaiza 2019-01-18 16:01:32 UTC
Created attachment 1521590 [details]
File: proc_pid_status

Comment 12 mastaiza 2019-01-18 16:01:33 UTC
Created attachment 1521591 [details]
File: exploitable

Comment 13 Jussi Eloranta 2019-01-18 21:52:16 UTC
Similar problem has been detected:

No special activity - hopefully the core dump will provide more info.

reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        xfce4-panel --display :0.0 --sm-client-id 26a3f870a-3997-466c-97f3-55fb617edfbd
crash_function: magazine_chain_pop_head
executable:     /usr/bin/xfce4-panel
journald_cursor: s=71dfc8742d9448b7a5ff6da12adcee30;i=a59d;b=4eabbc13185449ff83972ac9431b764d;m=16d692299f8;t=57fc1b2a8bb85;x=3fc68cff829f608e
kernel:         4.19.10-300.fc29.x86_64
package:        xfce4-panel-4.13.4-1.fc29
reason:         xfce4-panel killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1022

Comment 14 Miro Hrončok 2019-01-20 20:31:14 UTC
Similar problem has been detected:

it was during dnf update, I haven't interacted with panel in any way

reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        xfce4-panel --display :0.0 --sm-client-id 2184a6d98-2c73-4bdd-8a78-d2debf45237b
crash_function: magazine_chain_pop_head
executable:     /usr/bin/xfce4-panel
journald_cursor: s=887eaaad8a374c5e9394ed1828070e0f;i=2f7a;b=bf051b6cb599436f9e60a06fc1d34594;m=1fa75516;t=57fe981eab63c;x=95461eedf8f9c64b
kernel:         4.19.13-300.fc29.x86_64
package:        xfce4-panel-4.13.3-20.fc29
reason:         xfce4-panel killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 Scott Cohen 2019-01-21 09:05:26 UTC
Similar problem has been detected:

I think there was a lot of swapping going on at this time, I'm not sure.

reporter:       libreport-2.9.7
backtrace_rating: 4
cmdline:        /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libwhiskermenu.so 8 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=5cee89a16fe74a1d9b20ea325ac2e5fe;i=7f1d;b=b4f4353e48e64e4b9e257b28b2c635fd;m=8b6b82ad52;t=57ff1a591cc04;x=175ba88f20b6a041
kernel:         4.19.13-300.fc29.x86_64
package:        xfce4-panel-4.13.4-1.fc29
reason:         wrapper-2.0 killed by SIGSEGV
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 16 Raphael Groner 2019-01-25 20:34:45 UTC
Maybe someone should consider to report this to upstream. As it seems reproducible, what are steps?

Comment 17 Raphael Groner 2019-01-25 20:36:24 UTC
Maybe maintainers of Gtk can help. Reassigning.

Provided backtrace:
>  #13 _gtk_style_provider_private_changed at gtkstyleproviderprivate.c:113

Comment 18 Raphael Groner 2019-01-26 09:43:41 UTC
What theme do you use? My question because there are notes about CSS in the provided backtrace.

Any other special configuration? Does this crash happen with a fresh user profile?

Comment 19 Miro Hrončok 2019-01-26 10:57:40 UTC
I cannot reproduce.

I use Greybird GTK theme.

Comment 20 Scott Cohen 2019-01-26 16:41:02 UTC
The crash I reported was made while I was using the Greybird GTK theme, MATE icon set theme, and the Meenee window manager theme.

Comment 21 Raphael Groner 2019-01-30 19:18:45 UTC
*** Bug 1670582 has been marked as a duplicate of this bug. ***

Comment 22 Raphael Groner 2019-01-30 19:20:26 UTC
This is definitely an issue in Gtk core. Currently, there are 11 open bugs reported against several components with very similiar backtraces.
https://bugzilla.redhat.com/buglist.cgi?quicksearch=magazine_chain_pop_head

Could someone look into this, please?

Comment 23 Raphael Groner 2019-02-01 07:10:49 UTC
*** Bug 1671601 has been marked as a duplicate of this bug. ***

Comment 24 Raphael Groner 2019-02-02 10:23:22 UTC
*** Bug 1671940 has been marked as a duplicate of this bug. ***

Comment 25 Raphael Groner 2019-02-03 10:50:37 UTC
*** Bug 1672046 has been marked as a duplicate of this bug. ***

Comment 26 Mukundan Ragavan 2019-05-21 22:03:01 UTC
*** Bug 1711670 has been marked as a duplicate of this bug. ***

Comment 27 Mukundan Ragavan 2019-06-04 21:59:41 UTC
*** Bug 1716989 has been marked as a duplicate of this bug. ***

Comment 28 Ben Cotton 2019-10-31 19:11:30 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 29 Ben Cotton 2019-11-27 22:43:49 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.