Bug 594973 - [abrt] crash in compiz-0.8.6-1.fc13: dri_get_buffers: Process /usr/bin/compiz was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in compiz-0.8.6-1.fc13: dri_get_buffers: Process /usr/bin/compiz...
Keywords:
Status: CLOSED DUPLICATE of bug 584992
Alias: None
Product: Fedora
Classification: Fedora
Component: compiz
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adel Gadllah
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8d67ac21847d27d4bfbf69b5322...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-22 12:05 UTC by Eric Lake
Modified: 2010-05-25 08:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 08:44:08 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (41.65 KB, text/plain)
2010-05-22 12:05 UTC, Eric Lake 		no flags Details
View All

Description Eric Lake 2010-05-22 12:05:38 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: compiz --ignore-desktop-hints glib gconf gnomecompat --replace
component: compiz
crash_function: dri_get_buffers
executable: /usr/bin/compiz
global_uuid: 8d67ac21847d27d4bfbf69b5322911da4f732126
kernel: 2.6.33.4-95.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
-----
The apps that I had open when the crash happened were,

gnome-terminal, Firefox, Thunderbird and had just started messing with gNote.

How to reproduce
-----
1. Install mesa-dri-drivers-experimental.i686
2. Enable desktop effects (cube and wobbly windows)
3. Use the system
Comment 1 Eric Lake 2010-05-22 12:05:40 UTC 
Created attachment 415854 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 08:44:08 UTC 

*** This bug has been marked as a duplicate of bug 584992 ***
Comment 3 Karel Klíč 2010-05-25 08:44:08 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #584992.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.