Bug 672472 - [abrt] compiz-0.9.2.2-0.11.git619abc05b1.fc15: Process /usr/bin/compiz was killed by signal 11 (SIGSEGV)
Summary: [abrt] compiz-0.9.2.2-0.11.git619abc05b1.fc15: Process /usr/bin/compiz was ki...
Keywords:
Status: CLOSED DUPLICATE of bug 687922
Alias: None
Product: Fedora
Classification: Fedora
Component: compiz
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: leigh scott
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:eb1847633b407f8e73ae9585c68...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-25 08:32 UTC by Raphos
Modified: 2012-03-21 17:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 17:36:54 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (8.55 KB, text/plain)
2011-01-25 08:32 UTC, Raphos
no flags Details

Description Raphos 2011-01-25 08:32:55 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: compiz ccp --replace
component: compiz
executable: /usr/bin/compiz
kernel: 2.6.38-0.rc2.git0.1.fc15.x86_64
package: compiz-0.9.2.2-0.11.git619abc05b1.fc15
reason: Process /usr/bin/compiz was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1295944081
uid: 500

How to reproduce
-----
1.Update compiz today
2.Switch in the panel desktop-effects from gnome-shell to compiz
3.

Comment 1 Raphos 2011-01-25 08:32:58 UTC
Created attachment 475124 [details]
File: backtrace

Comment 2 Fedora Admin XMLRPC Client 2011-06-01 20:25:30 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 abrt-bot 2012-03-21 17:36:54 UTC
Backtrace analysis found this bug to be similar to bug #687922, closing as duplicate.

Bugs which were found to be similar to this bug: bug #670965, bug #687922

This comment is automatically generated.

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


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