Version: (using Devel) Compiler: g++ 4.1.3 OS: Linux Installed from: Compiled sources with empty dot and home directory systemsettings->appearence->windows->window decoration The default 'ozone' window decoration has an option "show stripes next to the title" enabled by default, but if you actually see the preview below there are no stripes shown.
Confirming here using: Qt: 4.4.3 + qt-copy-patches-889120 KDE: 4.2.60 (KDE 4.2.60 (KDE 4.3 >= 20090106)) kdelibs svn rev. 908156 / kdebase svn rev. 908156 on ArchLinux x86_64 - Kernel 2.6.27.10 Bug 169323 also reported this bug (Also, the "Active Window" title isn't show)
Actually, none of the changes made while clicking a checkbox get applied in the preview. Or am i wrong? E.g. In the plastik style, when you select to have the text centered, it doesn't show in the preview
Indeed, to update the preview (at least using Plastik) you have to: - Setup the style/options - Apply - Now, change to another decoration without applying - Select Plastik again. Now the Plastik decoration shows the selected configuration... I don't know if this report should be enhanced to "The Preview doesn't honor the selected options" or report another bug and leave this for the Ozone stripes..
This bug is still present in KDE-4.2rc1.
@Thomas (comment 2): can you file a new bug report describing the new problem we just discovered (using comment 2 and comment 3 information)? Thanks a lot :)
Unfortunately, this bug is still present in KDE-4.2 final.
This bug is still present in KDE-4.2.2.
post #0 may be more related to bug #196069 - these are however not necessarily real duplicates -> preview concept needs a more fundamental fix?!
There are two bugs described here 1/ that the ozone default setting is not reflected in its preview appearance This is "fixed" in kde4.4 and trunk: no more Ozone, and no more stripes next to the title. 2/ changes made to the decoration configuration are not visible in the preview. This is an upstream bug that affects all decorations settings (except the window border).
Could you please provide a pointer to the upstrem bug report?
*** This bug has been marked as a duplicate of bug 163825 ***