Bug 412541

Summary: Compiz desktop effects refuse to start
Product: [Fedora] Fedora Reporter: Raffaele Candeliere <r.candeliere>
Component: compiz-fusionAssignee: Adel Gadllah <adel.gadllah>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: low    
Version: 8CC: krh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-12-07 19:13:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Raffaele Candeliere 2007-12-05 18:17:14 UTC
Description of problem:
Compiz desktop effects refuse to start on an intel core duo aluminium 20" iMac


Version-Release number of selected component (if applicable):


How reproducible:
Install Fedora 8 on an aluminium intel core-duo based 20" iMac.
Then install the proprietary driver (yum-install from livna repository the
following package/updates: kmod-fglrx xorg-x11-drv-fglrx) for the ATI Radeon
HD2600 PRO video card (the open source driver doesn't support this video adapter).


Steps to Reproduce:
1.Launch (from gnome or kde) the "desktop-effests" window 
2.Click on "Enable desktop-effects"
3.Wait for the hint.
  
Actual results:
The hint says: "Desktop effects couldn't be activated"

Expected results:
Desktop effects enabled

Additional info:
I tried also installing compiz-fusion packages for F8 from other repos, but
always with the same result. No desktop effects.
I always removed the previous version of compiz before installing the next one
but nothing. With some packages i obtained "Segmentation fault". With others i
obtained messages complaining about missing Xgl or so ...

Comment 1 Adel Gadllah 2007-12-07 19:13:40 UTC
This looks like a problem with the fglrx driver (or its configuration) you have
to contact AMD/ATI for help. This is proprietary driver and therefore we cannot
fix it.