Bug 867108

Summary: [abrt] xfce4-panel-4.10.0-2.fc18: SmcCloseConnection: Process /usr/bin/xfce4-panel was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Andy Lawrence <dr.diesel>
Component: xfce4-panelAssignee: Kevin Fenzi <kevin>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: admiller, christoph.wickert, kevin
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:376270c6630fce05d65bd599966dce46386cff8b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:50:24 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: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description Andy Lawrence 2012-10-16 19:23:33 UTC
Description of problem:
Happened on boot, just after log-in.

Version-Release number of selected component:
xfce4-panel-4.10.0-2.fc18

Additional info:
libreport version: 2.0.16
abrt_version:   2.0.15
backtrace_rating: 4
cmdline:        xfce4-panel
crash_function: SmcCloseConnection
kernel:         3.6.1-1.fc18.x86_64

truncated backtrace:
:Thread no. 1 (3 frames)
: #0 SmcCloseConnection at sm_client.c:300
: #1 IA__xfce_sm_client_disconnect at xfce-sm-client.c:1720
: #2 xfce_sm_client_finalize at xfce-sm-client.c:591

Comment 1 Andy Lawrence 2012-10-16 19:23:36 UTC
Created attachment 628340 [details]
File: core_backtrace

Comment 2 Andy Lawrence 2012-10-16 19:23:37 UTC
Created attachment 628341 [details]
File: environ

Comment 3 Andy Lawrence 2012-10-16 19:23:39 UTC
Created attachment 628342 [details]
File: limits

Comment 4 Andy Lawrence 2012-10-16 19:23:41 UTC
Created attachment 628343 [details]
File: backtrace

Comment 5 Andy Lawrence 2012-10-16 19:23:42 UTC
Created attachment 628344 [details]
File: cgroup

Comment 6 Andy Lawrence 2012-10-16 19:23:44 UTC
Created attachment 628345 [details]
File: maps

Comment 7 Andy Lawrence 2012-10-16 19:23:46 UTC
Created attachment 628346 [details]
File: dso_list

Comment 8 Andy Lawrence 2012-10-16 19:23:47 UTC
Created attachment 628347 [details]
File: proc_pid_status

Comment 9 Andy Lawrence 2012-10-16 19:23:49 UTC
Created attachment 628348 [details]
File: var_log_messages

Comment 10 Andy Lawrence 2012-10-16 19:23:50 UTC
Created attachment 628349 [details]
File: open_fds

Comment 11 Kevin Fenzi 2012-10-17 20:42:08 UTC
Does it happen on every boot?

Did you reboot from a Xfce session?

Comment 12 Andy Lawrence 2012-10-18 22:42:48 UTC
This happened twice on boot.

I then realized that the Intel DN2800 motherboard that has a horrible Power something or other GPU only had 32bit drivers.  So I blasted my F18_64bit install and went for F18_32, which failed to boot in every possible manor.

I ended up on F17_32, which didn't have the error above.

Comment 13 Fedora End Of Life 2013-12-21 15:09:07 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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 14 Fedora End Of Life 2014-02-05 22:50:24 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.