Bug 603318 - [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...
Status: CLOSED DUPLICATE of bug 538679
Alias: None
Product: Fedora
Classification: Fedora
Component: compiz   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adel Gadllah
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fafb1138099a58578c63b3561d5...
Keywords: Triaged
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-12 11:51 UTC by Juta Sirakas
Modified: 2010-09-20 20:49 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-09-20 20:49:34 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (3.65 KB, text/plain)
2010-06-12 11:51 UTC, Juta Sirakas
no flags Details

Description Juta Sirakas 2010-06-12 11:51:23 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
component: compiz
executable: /usr/bin/compiz
global_uuid: fafb1138099a58578c63b3561d5032f51146dffb
kernel: 2.6.33.5-112.fc13.x86_64
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 Juta Sirakas 2010-06-12 11:51:26 UTC
Created attachment 423483 [details]
File: backtrace

Comment 2 edo 2010-06-26 11:56:10 UTC
Package: compiz-0.8.6-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Start Gnome
2.Restart
3.

Comment 3 Hamidou Dia 2010-09-20 20:49:34 UTC
Hi Juta,

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 538679 ***


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