Bug 626567

Summary: [abrt] compiz-0.8.6-1.fc13: radeon_bo_get_tiling: Process /usr/bin/compiz was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: pmvr
Component: compizAssignee: Adel Gadllah <adel.gadllah>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: adel.gadllah, bbgun06, hidoufr, jpv50
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:1c34e067de190c44e1d56e3b7ce56972a38ded96
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-09 22:47:05 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 pmvr 2010-08-23 20:36:24 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: compiz --ignore-desktop-hints ccp
component: compiz
crash_function: radeon_bo_get_tiling
executable: /usr/bin/compiz
kernel: 2.6.33.6-147.2.4.fc13.i686
package: compiz-0.8.6-1.fc13
rating: 4
reason: Process /usr/bin/compiz was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1282595837
uid: 500

Comment 1 pmvr 2010-08-23 20:36:32 UTC
Created an attachment (id=440493)
File: backtrace

Comment 2 John Vincent 2010-09-06 20:44:59 UTC
Package: compiz-0.8.6-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. open an application
2. open a sub-window (like the "about" dialogue box)
3. re-size the sub-window


Comment
-----
Only seems to happen when resizing a sub-window, not a main window.
Seems to happen with many applications.

Comment 3 Hamidou Dia 2010-09-09 22:47:05 UTC
Hi Pedro, John.

Thanks for reporting this issue.

Regards.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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