Bug 1167281

Summary: [abrt] xfce4-panel: xfce_tasklist_button_enter_notify_event_disconnected(): xfce4-panel killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Roel van de Kraats <rhbug>
Component: xfce4-panelAssignee: Kevin Fenzi <kevin>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: christoph.wickert, joshua.kordani, kevin, nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/79b8800cc33fdfb154eab45a6eb97d52fc00ea54
Whiteboard: abrt_hash:4c30c660e88decad02f7620d537ee7015645721b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 01:13:42 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: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Roel van de Kraats 2014-11-24 11:23:50 UTC 
Version-Release number of selected component:
xfce4-panel-4.10.1-3.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        xfce4-panel --display :0.0 --sm-client-id 2616e45d6-b642-45f4-9f1d-a1e5f36297f8
crash_function: xfce_tasklist_button_enter_notify_event_disconnected
executable:     /usr/bin/xfce4-panel
kernel:         3.17.2-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            578

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 xfce_tasklist_button_enter_notify_event_disconnected at tasklist-widget.c:2690
 #1 closure_invoke_notifiers at gclosure.c:249
 #2 g_closure_unref at gclosure.c:599
 #3 handler_unref_R at gsignal.c:653
 #4 g_signal_handlers_destroy at gsignal.c:2661
 #9 gtk_object_dispose at gtkobject.c:421
 #11 gtk_menu_shell_forall at gtkmenushell.c:1113
 #12 gtk_container_destroy at gtkcontainer.c:1073
 #17 gtk_object_dispose at gtkobject.c:421
 #19 xfce_tasklist_group_button_menu_destroy at tasklist-widget.c:3260

Potential duplicate: bug 719802
Comment 1 Roel van de Kraats 2014-11-24 11:23:53 UTC 
Created attachment 960663 [details]
File: backtrace
Comment 2 Roel van de Kraats 2014-11-24 11:23:54 UTC 
Created attachment 960664 [details]
File: cgroup
Comment 3 Roel van de Kraats 2014-11-24 11:23:56 UTC 
Created attachment 960665 [details]
File: core_backtrace
Comment 4 Roel van de Kraats 2014-11-24 11:23:57 UTC 
Created attachment 960666 [details]
File: dso_list
Comment 5 Roel van de Kraats 2014-11-24 11:23:58 UTC 
Created attachment 960667 [details]
File: environ
Comment 6 Roel van de Kraats 2014-11-24 11:23:59 UTC 
Created attachment 960668 [details]
File: exploitable
Comment 7 Roel van de Kraats 2014-11-24 11:24:00 UTC 
Created attachment 960669 [details]
File: limits
Comment 8 Roel van de Kraats 2014-11-24 11:24:02 UTC 
Created attachment 960670 [details]
File: maps
Comment 9 Roel van de Kraats 2014-11-24 11:24:03 UTC 
Created attachment 960671 [details]
File: open_fds
Comment 10 Roel van de Kraats 2014-11-24 11:24:04 UTC 
Created attachment 960672 [details]
File: proc_pid_status
Comment 11 Roel van de Kraats 2014-11-24 11:24:05 UTC 
Created attachment 960673 [details]
File: var_log_messages
Comment 12 Kevin Fenzi 2014-11-24 15:12:10 UTC 
What were you doing when this happened?

Can you duplicate it?
Comment 13 Roel van de Kraats 2014-11-24 15:21:23 UTC 
I'm not quite sure what happened. I had a lot of Firefox windows open and closed one of them. Firefox was very busy (using 100% CPU time) and while I was waiting for the window to close, the xfce4-panel restarted.
Comment 14 Kevin Fenzi 2014-11-24 19:29:02 UTC 
ok. I will see if I can make anything of the backtrace. ;) 

thanks.
Comment 15 Joshua Kordani 2015-03-12 02:32:16 UTC 
Another user experienced a similar problem:

i don't fucking know.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        xfce4-panel
crash_function: xfce_tasklist_button_enter_notify_event_disconnected
executable:     /usr/bin/xfce4-panel
kernel:         3.18.8-100.fc20.i686
package:        xfce4-panel-4.10.1-3.fc20
reason:         xfce4-panel killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 16 Fedora End Of Life 2015-05-29 13:22:53 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 17 Fedora End Of Life 2015-06-30 01:13:42 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.