Bug 952374

Summary: [abrt] xfwm4-4.10.0-5.fc18: find_cwindow_in_screen: Process /usr/bin/xfwm4 was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: jamie <mail>
Component: xfwm4Assignee: Kevin Fenzi <kevin>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: admiller, kevin, mail
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8d50532afb08ec7b845c56fd2edea2b511795cf1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-21 21:02:00 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: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description jamie 2013-04-15 19:44:44 UTC 
Version-Release number of selected component:
xfwm4-4.10.0-5.fc18

Additional info:
backtrace_rating: 4
cmdline:        xfwm4 --display :0.0 --sm-client-id 2f662d6e7-4c8b-4338-8c57-e9b4be0cb7c8
crash_function: find_cwindow_in_screen
executable:     /usr/bin/xfwm4
kernel:         3.8.6-203.fc18.x86_64
uid:            1000
ureports_counter: 2

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 find_cwindow_in_screen at compositor.c:144
 #1 find_cwindow_in_display at compositor.c:164
 #2 compositorSetClient at compositor.c:2618
 #3 clientUnframe at client.c:1936
 #4 clientUnframeAll at client.c:2076
 #5 myScreenClose at screen.c:359
 #6 cleanUp at main.c:155
Comment 1 jamie 2013-04-15 19:44:47 UTC 
Created attachment 736030 [details]
File: backtrace
Comment 2 jamie 2013-04-15 19:44:49 UTC 
Created attachment 736031 [details]
File: cgroup
Comment 3 jamie 2013-04-15 19:44:51 UTC 
Created attachment 736032 [details]
File: core_backtrace
Comment 4 jamie 2013-04-15 19:44:52 UTC 
Created attachment 736033 [details]
File: environ
Comment 5 jamie 2013-04-15 19:44:55 UTC 
Created attachment 736034 [details]
File: limits
Comment 6 jamie 2013-04-15 19:44:57 UTC 
Created attachment 736035 [details]
File: maps
Comment 7 jamie 2013-04-15 19:44:59 UTC 
Created attachment 736036 [details]
File: open_fds
Comment 8 jamie 2013-04-15 19:45:01 UTC 
Created attachment 736037 [details]
File: proc_pid_status
Comment 9 Kevin Fenzi 2013-04-15 21:01:54 UTC 
What were you doing when this happened? 

Can you duplicate it?
Comment 10 jamie 2013-04-15 21:08:54 UTC 
I get this error after booting up and loging into my machine, I may have got it once before. My shutdown was clean.
Comment 11 jamie 2013-04-21 20:29:18 UTC 
* sorry got, I don't get seem to get it anymore.
Comment 12 Kevin Fenzi 2013-04-21 21:02:00 UTC 
Great.
Comment 13 jamie 2013-04-21 21:06:23 UTC 
But I did get Bug #954197 which also involves a "killed by signal 11 (SIGSEGV)" but it may not be related.