Bug 596504

Summary: [abrt] crash in metacity-2.30.0-2.fc13: pa_atomic_load: Process /usr/bin/metacity was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Gerard Pradas <pradasgsj>
Component: metacityAssignee: Owen Taylor <otaylor>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: it_rom, otaylor, sjohnson, tobyknudsen, wlh2008
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:7b2f82489da1114214d39253baee0abedf1e6d8a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-08 18:27:56 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

Description Gerard Pradas 2010-05-26 20:23:46 UTC 
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: metacity
component: metacity
crash_function: pa_atomic_load
executable: /usr/bin/metacity
global_uuid: 7b2f82489da1114214d39253baee0abedf1e6d8a
kernel: 2.6.33.3-85.fc13.x86_64
package: metacity-2.30.0-2.fc13
rating: 4
reason: Process /usr/bin/metacity was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Gerard Pradas 2010-05-26 20:23:49 UTC 
Created attachment 417021 [details]
File: backtrace
Comment 2 tobyknudsen@gmail.com 2010-05-27 18:23:08 UTC 
Package: metacity-2.30.0-2.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. had started cinepaint...
2.
3.
Comment 3 William Hill 2010-06-25 23:07:39 UTC 
Package: metacity-2.30.0-2.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


Comment
-----
I was openning a .png on my harddisk when this occurred.
Comment 4 Owen Taylor 2010-07-08 18:27:56 UTC 

*** This bug has been marked as a duplicate of bug 544520 ***