Bug 625253 - [abrt] compiz-0.8.6-1.fc13: dri_get_buffers: Process /usr/bin/compiz was killed by signal 11 (SIGSEGV)
[abrt] compiz-0.8.6-1.fc13: dri_get_buffers: Process /usr/bin/compiz was kill...
Status: CLOSED DUPLICATE of bug 595236
Product: Fedora
Classification: Fedora
Component: compiz (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Adel Gadllah
Fedora Extras Quality Assurance
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2010-08-18 20:27 EDT by Paul Lange
Modified: 2010-09-13 11:52 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-09-13 11:52:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (40.48 KB, text/plain)
2010-08-18 20:27 EDT, Paul Lange
no flags Details
Backtrace (41.78 KB, application/octet-stream)
2010-09-03 17:47 EDT, Andrea Oliveti
no flags Details

  None (edit)
Description Paul Lange 2010-08-18 20:27:35 EDT
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: compiz --ignore-desktop-hints glib gconf gnomecompat
component: compiz
crash_function: dri_get_buffers
executable: /usr/bin/compiz
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: 1282177297
uid: 500
Comment 1 Paul Lange 2010-08-18 20:27:39 EDT
Created an attachment (id=439555)
File: backtrace
Comment 2 Andrea Oliveti 2010-09-03 17:42:05 EDT
Package: compiz-0.8.6-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)

How to reproduce
Comment 3 Andrea Oliveti 2010-09-03 17:47:19 EDT
Created attachment 442990 [details]
Comment 4 Hamidou Dia 2010-09-13 11:52:35 EDT
Hi Paul.

Thanks for reporting this issue.


Fedora Bugzappers volunteer triage team

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

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