Bug 868727

Summary: [abrt] kde-workspace-4.9.2-3.fc17: call_gmon_start: Process /usr/bin/kwin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: john.white77
Component: kde-workspaceAssignee: Than Ngo <than>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: jgrulich, jreznik, kevin, ltinkl, mbriza, rdieter, rnovacek, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:31a2b9949f8c0a5ddb7deb553e343f734c439f8c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 12:08:40 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: event_log
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: maps
none
File: dso_list
none
File: open_fds
none
File: var_log_messages none

Description john.white77 2012-10-22 01:08:53 UTC
Version-Release number of selected component:
kde-workspace-4.9.2-3.fc17

Additional info:
libreport version: 2.0.14
abrt_version:   2.0.13
backtrace_rating: 4
cmdline:        /usr/bin/kwin --crashes 1
crash_function: call_gmon_start
kernel:         3.6.1-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (1 frames)
: #0 call_gmon_start at /lib64/libkwineffects.so.1

Comment 1 john.white77 2012-10-22 01:08:56 UTC
Created attachment 631175 [details]
File: core_backtrace

Comment 2 john.white77 2012-10-22 01:08:58 UTC
Created attachment 631176 [details]
File: environ

Comment 3 john.white77 2012-10-22 01:08:59 UTC
Created attachment 631177 [details]
File: event_log

Comment 4 john.white77 2012-10-22 01:09:01 UTC
Created attachment 631178 [details]
File: limits

Comment 5 john.white77 2012-10-22 01:09:03 UTC
Created attachment 631179 [details]
File: backtrace

Comment 6 john.white77 2012-10-22 01:09:04 UTC
Created attachment 631180 [details]
File: cgroup

Comment 7 john.white77 2012-10-22 01:09:06 UTC
Created attachment 631181 [details]
File: maps

Comment 8 john.white77 2012-10-22 01:09:08 UTC
Created attachment 631182 [details]
File: dso_list

Comment 9 john.white77 2012-10-22 01:09:09 UTC
Created attachment 631183 [details]
File: open_fds

Comment 10 john.white77 2012-10-22 01:09:11 UTC
Created attachment 631184 [details]
File: var_log_messages

Comment 11 Kevin Kofler 2012-10-22 21:33:42 UTC
This sounds a lot like a graphics driver bug. What graphics driver are you using?

Comment 12 Fedora End Of Life 2013-07-04 03:53:51 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 13 Fedora End Of Life 2013-08-01 12:08:50 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.