Bug 495285 - 'Enable Desktop Effects' checkbox in KDE4 / Rawhide seems to have no effect
'Enable Desktop Effects' checkbox in KDE4 / Rawhide seems to have no effect
Product: Fedora
Classification: Fedora
Component: kdebase-workspace (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Ngo Than
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-04-11 02:54 EDT by Brian Vuyk
Modified: 2009-05-26 14:55 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-05-26 14:55:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brian Vuyk 2009-04-11 02:54:01 EDT
Description of problem:

Checking the 'Enable Desktop Effects' checkbox in KDE4 / Rawhide seems to have no effect. 

Steps to Reproduce:
1. Go to the System Settings dialog and click on 'Desktop'.
2. Check the 'Enable Desktop Effects' box
3. Click Apply.

Actual results:

Desktop effects aren't enabled. 'Enable Desktop Effects' box remains checked even after closing and reopening System Settings and after reboot. However, no desktop effects are enabled on desktop.

Expected results:

Desktop effects should be enabled at this point.

Additional info:

I am using today's Rawhide, with the proprietary nvidia drivers. I would be happy to provide any debugging information needed. I apologize of this bug is filed wrong - I wasn't sure what to file it against.
Comment 1 Steven M. Parrish 2009-05-26 14:45:14 EDT
I am unable to reproduce this using rawhide with nvidia drivers.  Is this still an issue?  If so I hate to say its probably an issue with the proprietary driver as no one else is reporting this issue.  If that is the case I'm sorry to say nothing that we can do.
Comment 2 Brian Vuyk 2009-05-26 14:55:14 EDT
Just tested today, and it works properly.

I am closing.

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