Bug 1706292

Summary: [abrt] xfce4-panel: magazine_chain_pop_head(): xfce4-panel killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Villy Kruse <ppywlkiqletw>
Component: xfce4-panelAssignee: Kevin Fenzi <kevin>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: abhisek.mukherjee, dirk, doniysa, feiticeir0, jcomputer, joaomfloriano, joe.klemmer, ju.oa, kevin, ludek.bartek, mcm, nonamedotc, prd-fedora, raphoszap, rpuxa.m, stealthcipher, stepan.anikin, william.d.southard, youandox
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0730598af6e416c725a7dbac4c1def471b6c828a
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-05-04 11:19:27 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 Villy Kruse 2019-05-04 05:15:20 UTC 
Description of problem:
This happens often when running "dnf upgrade".


Version-Release number of selected component:
xfce4-panel-4.13.4-2.fc30

Additional info:
reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        xfce4-panel
crash_function: magazine_chain_pop_head
executable:     /usr/bin/xfce4-panel
journald_cursor: s=386ec708b06a4d0fa8aecf956f91c2a2;i=13b8b5;b=2a0a8bfd7fb14beeb1349ae16426e7ad;m=5a900874;t=58808c2214896;x=9c8438e8ecebfec2
kernel:         5.0.10-300.fc30.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 magazine_chain_pop_head at ../glib/gslice.c:538
 #1 thread_memory_magazine1_alloc at ../glib/gslice.c:841
 #2 g_slice_alloc at ../glib/gslice.c:1015
 #3 g_list_prepend at ../glib/glist.c:314
 #4 gtk_container_children_callback at gtkcontainer.c:3310
 #5 gtk_menu_shell_forall at gtkmenushell.c:1154
 #6 gtk_container_get_children at gtkcontainer.c:2542
 #7 garcon_gtk_menu_reload_idle at garcon-gtk-menu.c:614
 #13 gtk_main at gtkmain.c:1323

Potential duplicate: bug 1672108
Comment 1 Villy Kruse 2019-05-04 05:15:24 UTC 
Created attachment 1562939 [details]
File: backtrace
Comment 2 Villy Kruse 2019-05-04 05:15:25 UTC 
Created attachment 1562940 [details]
File: cgroup
Comment 3 Villy Kruse 2019-05-04 05:15:26 UTC 
Created attachment 1562941 [details]
File: core_backtrace
Comment 4 Villy Kruse 2019-05-04 05:15:27 UTC 
Created attachment 1562942 [details]
File: cpuinfo
Comment 5 Villy Kruse 2019-05-04 05:15:29 UTC 
Created attachment 1562943 [details]
File: dso_list
Comment 6 Villy Kruse 2019-05-04 05:15:30 UTC 
Created attachment 1562944 [details]
File: environ
Comment 7 Villy Kruse 2019-05-04 05:15:31 UTC 
Created attachment 1562945 [details]
File: exploitable
Comment 8 Villy Kruse 2019-05-04 05:15:32 UTC 
Created attachment 1562946 [details]
File: limits
Comment 9 Villy Kruse 2019-05-04 05:15:34 UTC 
Created attachment 1562947 [details]
File: maps
Comment 10 Villy Kruse 2019-05-04 05:15:35 UTC 
Created attachment 1562948 [details]
File: mountinfo
Comment 11 Villy Kruse 2019-05-04 05:15:36 UTC 
Created attachment 1562949 [details]
File: open_fds
Comment 12 Villy Kruse 2019-05-04 05:15:37 UTC 
Created attachment 1562950 [details]
File: proc_pid_status
Comment 13 Mukundan Ragavan 2019-05-04 11:19:27 UTC 

*** This bug has been marked as a duplicate of bug 1671518 ***
Comment 14 Abhisek Mukherjee 2019-05-05 09:28:57 UTC 
*** Bug 1706535 has been marked as a duplicate of this bug. ***
Comment 15 Will 2019-05-06 11:31:12 UTC 
*** Bug 1706836 has been marked as a duplicate of this bug. ***
Comment 16 Abhisek Mukherjee 2019-05-11 16:25:10 UTC 
*** Bug 1708914 has been marked as a duplicate of this bug. ***
Comment 17 Paul DeStefano 2019-05-20 03:25:44 UTC 
*** Bug 1711742 has been marked as a duplicate of this bug. ***
Comment 18 Abhisek Mukherjee 2019-05-27 05:08:18 UTC 
*** Bug 1714086 has been marked as a duplicate of this bug. ***
Comment 19 Dirk Deimeke 2019-05-28 04:18:01 UTC 
*** Bug 1714416 has been marked as a duplicate of this bug. ***
Comment 20 Joe Klemmer 2019-05-29 17:46:52 UTC 
*** Bug 1715162 has been marked as a duplicate of this bug. ***
Comment 21 Wiley Young 2019-05-30 22:07:57 UTC 
*** Bug 1715651 has been marked as a duplicate of this bug. ***
Comment 22 Wiley Young 2019-05-30 22:40:47 UTC 
*** Bug 1715657 has been marked as a duplicate of this bug. ***
Comment 23 Sergii Donii 2019-06-04 13:07:44 UTC 
*** Bug 1716968 has been marked as a duplicate of this bug. ***
Comment 24 Raphos 2019-06-19 14:06:48 UTC 
*** Bug 1722124 has been marked as a duplicate of this bug. ***
Comment 25 Grigory 2019-06-28 03:58:19 UTC 
*** Bug 1724899 has been marked as a duplicate of this bug. ***
Comment 26 Ryan 2019-07-15 12:27:56 UTC 
*** Bug 1729961 has been marked as a duplicate of this bug. ***
Comment 27 Joao Marcos Floriano 2019-07-24 01:09:39 UTC 
*** Bug 1732646 has been marked as a duplicate of this bug. ***
Comment 28 Ludek Bartek 2019-07-30 19:17:49 UTC 
*** Bug 1734528 has been marked as a duplicate of this bug. ***
Comment 29 Marcus 2019-07-31 02:12:26 UTC 
*** Bug 1734595 has been marked as a duplicate of this bug. ***
Comment 30 Bruno Santos 2019-07-31 09:15:36 UTC 
*** Bug 1734703 has been marked as a duplicate of this bug. ***
Comment 31 Stepan 2019-08-12 09:58:40 UTC 
*** Bug 1740104 has been marked as a duplicate of this bug. ***
Comment 32 Dong 2019-10-12 11:03:30 UTC 
*** Bug 1761087 has been marked as a duplicate of this bug. ***
Comment 33 John Veenstra 2019-10-17 01:58:42 UTC 
*** Bug 1762591 has been marked as a duplicate of this bug. ***