Bug 989083

Summary: [abrt] mate-window-manager-1.6.2-3.fc19: g_list_foreach: Process /usr/bin/marco was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Dario Di Nucci <linkin88mail>
Component: mate-window-managerAssignee: Dan Mashal <dan.mashal>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: dan.mashal, raveit65.sun, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b8b1d4630f3509f06581b352a0c32b69e573424e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-04 13:15:09 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: xsession_errors none

Description Dario Di Nucci 2013-07-27 12:45:27 UTC 
Description of problem:
When activating compiz windows manager.

Version-Release number of selected component:
mate-window-manager-1.6.2-3.fc19

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        marco
crash_function: g_list_foreach
executable:     /usr/bin/marco
kernel:         3.10.3-300.fc19.x86_64
runlevel:       N 5
uid:            1000
var_log_messages: Jul 27 14:29:49 localhost abrt[3428]: Saved core dump of pid 904 (/usr/bin/marco) to /var/tmp/abrt/ccpp-2013-07-27-14:29:48-904 (32870400 bytes)

Truncated backtrace:
Thread no. 1 (5 frames)
 #6 g_list_foreach at glist.c:949
 #7 meta_screen_composite_all_windows at core/screen.c:825
 #8 enable_compositor at core/display.c:289
 #9 emit_changed at core/prefs.c:798
 #10 changed_idle_handler at core/prefs.c:824
Comment 1 Dario Di Nucci 2013-07-27 12:45:31 UTC 
Created attachment 779061 [details]
File: backtrace
Comment 2 Dario Di Nucci 2013-07-27 12:45:34 UTC 
Created attachment 779062 [details]
File: cgroup
Comment 3 Dario Di Nucci 2013-07-27 12:45:37 UTC 
Created attachment 779063 [details]
File: core_backtrace
Comment 4 Dario Di Nucci 2013-07-27 12:45:42 UTC 
Created attachment 779064 [details]
File: dso_list
Comment 5 Dario Di Nucci 2013-07-27 12:45:46 UTC 
Created attachment 779065 [details]
File: environ
Comment 6 Dario Di Nucci 2013-07-27 12:45:49 UTC 
Created attachment 779066 [details]
File: limits
Comment 7 Dario Di Nucci 2013-07-27 12:45:53 UTC 
Created attachment 779067 [details]
File: maps
Comment 8 Dario Di Nucci 2013-07-27 12:45:57 UTC 
Created attachment 779068 [details]
File: open_fds
Comment 9 Dario Di Nucci 2013-07-27 12:46:00 UTC 
Created attachment 779069 [details]
File: proc_pid_status
Comment 10 Dario Di Nucci 2013-07-27 12:46:03 UTC 
Created attachment 779070 [details]
File: xsession_errors
Comment 11 Wolfgang Ulbrich 2013-08-03 23:56:02 UTC 
Can you describe a little more detailed what happend?
How did you start compiz?
Did this issue occurs frequently ?
Comment 12 Dario Di Nucci 2013-08-04 13:15:09 UTC 
It happend when trying to activate compiz from Control Center -> Windows.
In the end it activated it but there was this warning.
With the last updates it doesn't happend anylong. =)