Bug 616886 - [abrt] crash in compiz-0.8.6-1.fc13: Process /usr/bin/compiz was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in compiz-0.8.6-1.fc13: Process /usr/bin/compiz was killed by si...
Keywords:
Status: CLOSED DUPLICATE of bug 576883
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:7a73b5abbf87e3b53838ba31143...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-21 16:11 UTC by Mitrandir
Modified: 2023-09-14 01:21 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-09-13 19:24:41 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (41.61 KB, text/plain)
2010-07-21 16:11 UTC, Mitrandir 		no flags Details
View All

Description Mitrandir 2010-07-21 16:11:36 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: compiz --ignore-desktop-hints ccp
component: compiz
executable: /usr/bin/compiz
global_uuid: 7a73b5abbf87e3b53838ba31143ae3741b315678
kernel: 2.6.33.6-147.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 Mitrandir 2010-07-21 16:11:39 UTC 
Created attachment 433456 [details]
File: backtrace
Comment 2 Hamidou Dia 2010-09-13 19:24:41 UTC 
Hi,


Thanks for reporting the issue.
This a duplicate of BZ#576883.
I am closing this ticket, so please feel free to make any comment regarding this issue in BZ#576883.
We would be interested to know if whether or not you still face the same issues, with the lastest intel drivers.

Regards.




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

*** This bug has been marked as a duplicate of bug 576883 ***
Comment 3 Red Hat Bugzilla 2023-09-14 01:21:41 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.