Bug 170371 - Set an option and cancel it leads to inconsistency
Summary: Set an option and cancel it leads to inconsistency
Status: RESOLVED DUPLICATE of bug 238119
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-04 11:21 UTC by Charles
Modified: 2012-08-26 10:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Charles 2008-09-04 11:21:45 UTC 
Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Ubuntu Packages

Open the Configue Window Behaviour menu.
Tick the option enable desktop effect and go to the  tab desktop effects enabled.
Then leave the menu with the cancel button.
If you open it back, you will see that the option is still ticked whereas the effect is not enabled..

The problem doesn't occur if instead of going to the all effects tab you switch to another menu on the left column and leave.

The same control has to be done for the previous run I described..

Cheers everyone
Comment 1 Martin Flöser 2011-03-19 10:11:47 UTC 
is this still an issue in a later release of KDE?
Comment 2 FiNeX 2011-03-19 10:43:45 UTC 
@Martin: yes, the bug is still valid, just reproduced using KDE 4.6.1
Comment 3 Martin Flöser 2011-03-19 10:59:36 UTC 
more interesting would be in fact to know if it is still reproducable in master as the dialog changed.
Comment 4 Thomas Lübking 2011-03-19 16:02:40 UTC 
The particular issue is gone, since the option doesn't work this way anymore.
The general bug behind this is that the config is synced and reloaded on tab changes w/o emitting an "apply" / changed() signal.

In other words:
switching tabs implicitly saves the config (to disk) - to gain sync between the switcher setting and the "all effects" tab (and also the restrictions of the XRender backend)
This is somehow a design bug :-(
Comment 5 Thomas Lübking 2012-08-26 10:40:51 UTC 

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