Bug 570723 - [abrt] crash in compiz-0.8.2-24.fc12: Process /usr/bin/compiz was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in compiz-0.8.2-24.fc12: Process /usr/bin/compiz was killed by s...
Keywords:
Status: CLOSED DUPLICATE of bug 542804
Alias: None
Product: Fedora
Classification: Fedora
Component: compiz
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Adel Gadllah
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:51aa266aac56909b7331abf4b98...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-05 07:42 UTC by Tom Beam
Modified: 2010-03-28 15:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-28 15:52:11 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (25.09 KB, text/plain)
2010-03-05 07:42 UTC, Tom Beam
no flags Details

Description Tom Beam 2010-03-05 07:42:21 UTC
abrt 1.0.7 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: compiz --replace --sm-disable --ignore-desktop-hints ccp
component: compiz
executable: /usr/bin/compiz
kernel: 2.6.31.12-174.2.22.fc12.i686
package: compiz-0.8.2-24.fc12
rating: 4
reason: Process /usr/bin/compiz was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
How to reproduce: 1. run a cube test with videos on all 4 sides...i think that did it

Comment 1 Tom Beam 2010-03-05 07:42:23 UTC
Created attachment 397989 [details]
File: backtrace

Comment 2 Luigi Pardey 2010-03-27 16:26:41 UTC

How to reproduce
-----
1.Enable Compiz Fusion
2.Get an app to lock the acces to yum
3.Let gpk-update-icon try to get the lock to the application


Comment
-----
When the mouse pointer goes over the button in the taskbar for gpk-update-icon, with the message that the application can't get the lock to the application, Compiz Fusion crashes, and it must be restarted.

Comment 3 Adel Gadllah 2010-03-28 15:52:11 UTC

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


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