Bug 883119

Summary: [abrt] xfce4-panel-4.8.6-4.fc17: sn_xcb_display_new: Process /usr/bin/xfce4-panel was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: M J <login>
Component: xfce4-panelAssignee: Kevin Fenzi <kevin>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: admiller, christoph.wickert, kevin
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b405ba86c997b40cfff85eac7adfb7896a3b48d6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 17:37:30 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: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: maps
none
File: open_fds none

Description M J 2012-12-03 20:08:54 UTC 
Version-Release number of selected component:
xfce4-panel-4.8.6-4.fc17

Additional info:
libreport version: 2.0.14
abrt_version:   2.0.13
backtrace_rating: 4
cmdline:        xfce4-panel
crash_function: sn_xcb_display_new
kernel:         3.6.1-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 sn_xcb_display_new at sn-common.c:149
: #1 sn_display_new at sn-common.c:77
: #2 wnck_screen_construct at screen.c:594
: #3 wnck_screen_get at screen.c:650
: #4 xfce_tasklist_connect_screen at tasklist-widget.c:1366
: #5 _g_closure_invoke_va at gclosure.c:840
: #8 gtk_widget_realize at gtkwidget.c:3543
: #9 gtk_widget_map at gtkwidget.c:3417
: #10 gtk_box_forall at gtkbox.c:1251
: #11 gtk_container_map at gtkcontainer.c:2684
Comment 1 M J 2012-12-03 20:09:13 UTC 
Created attachment 656992 [details]
File: environ
Comment 2 M J 2012-12-03 20:09:15 UTC 
Created attachment 656993 [details]
File: limits
Comment 3 M J 2012-12-03 20:09:17 UTC 
Created attachment 656994 [details]
File: backtrace
Comment 4 M J 2012-12-03 20:09:19 UTC 
Created attachment 656995 [details]
File: cgroup
Comment 5 M J 2012-12-03 20:09:21 UTC 
Created attachment 656996 [details]
File: maps
Comment 6 M J 2012-12-03 20:09:22 UTC 
Created attachment 656997 [details]
File: open_fds
Comment 7 Kevin Fenzi 2012-12-03 23:58:50 UTC 
What were you doing when this happened?

Can you duplicate it?
Comment 8 Fedora End Of Life 2013-07-04 06:09:27 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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 9 Fedora End Of Life 2013-08-01 17:37:34 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.