Bug 602617 - [abrt] crash in compiz-0.8.6-1.fc13: radeon_bo_get_tiling: Process /usr/bin/compiz was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in compiz-0.8.6-1.fc13: radeon_bo_get_tiling: Process /usr/bin/c...
Keywords:
Status: CLOSED DUPLICATE of bug 568593
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8335d6f23511e66c8132cbfc776...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-10 10:20 UTC by freeman
Modified: 2010-06-15 07:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-15 07:19:10 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (30.70 KB, text/plain)
2010-06-10 10:20 UTC, freeman 		no flags Details
View All

Description freeman 2010-06-10 10:20:07 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: compiz --ignore-desktop-hints ccp
component: compiz
crash_function: radeon_bo_get_tiling
executable: /usr/bin/compiz
global_uuid: 8335d6f23511e66c8132cbfc776d6fa97448ad4f
kernel: 2.6.33.5-112.fc13.i686.PAE
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)
Comment 1 freeman 2010-06-10 10:20:09 UTC 
Created attachment 422850 [details]
File: backtrace
Comment 2 Adel Gadllah 2010-06-12 07:45:21 UTC 
This is a driver bug.
Comment 3 freeman 2010-06-13 04:22:09 UTC 
Thanks. I will try to rearrange
Comment 4 Jeff Raber 2010-06-15 07:19:10 UTC 
Thank you for the bug report. This particular bug has already been reported
into our bug tracking system, but please feel free to report any further bugs
you find.



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

*** This bug has been marked as a duplicate of bug 568593 ***
Note You need to log in before you can comment on or make changes to this bug.