Created attachment 68649 [details] button background glitch using QtCurve Version: unspecified (using KDE 4.8.0) OS: Linux The background behind the buttons of some window decorations appears to be "see-through" when compositing (desktop effects) are turned off. So far I have been able to reproduce this with both the QtCurve (1.8.7) and deKorator (0.5.1). This is most easily perceived with round buttons (see attached screenshot). I have reproduced this on two systems with NVIDIA and Intel graphics chipsets. Reproducible: Always Steps to Reproduce: 1. Install the QtCurve theme and set the window decoration to QtCurve. (In Kubuntu, I'm using QtCurve version 1.8.7.) 2. Turn off desktop effects. 3. Open a few windows and observe the titlebar buttons... the area behind the button will appear as whatever is behind the window when it is created. Actual Results: Graphics corruption. Expected Results: No graphics corruption. ** My System ** OS: Kubuntu 11.10 64-bit w/ KDE 4.8.0 Motherboard: ASRock X58 Extreme3 (Intel X58 chipset) CPU: Intel Core i7 (2.8 GHz quad-core) RAM: 12GB DDR3 Video: Dell NVIDIA GeForce 7800 GTX w/ 256 MB RAM (PCI Express) Linux Kernel: 3.1.0-1-generic NVIDIA video driver: 280.13 Screen Resolution: 1280 x 960
Reassigning to dekorator. For QtCurve you'll have to contact Craig (bugs.kde.org rejected his mail address) ------------------------------------------------ Repost of a kwin@kde.org message ------------------------------------------------ Hi decoration developers, we have a change in KWin master (aka 4.8) I wanted to inform you about. Since a2ca75f6573e04922bb2d2a4b964607c332e55be the internal PaintRedirector is only used in a composited setup. For non-composited setups the behavior is as it used to be before we added translucancy support to KWin decorations (4.2 and beore). It is possible that this change introduces rendering artefacts if the decoration requires double buffering (which was provided through the PaintRedirector incorrectly also for non-composited setups). Hugo fixed such issues in our default Oxygen decoration with the commits: * be56be249db8abc81f757879c452358865671414 * c83f46f928460500ac4dfd1415c40b1a56c494cc * 410a930691abe2d41903e5ecad6c863b92790ced Apart from this issue I wanted to inform you that I started to work on a new decoration API. I do not yet know when this becomes available, but I do not plan to remove the existing API before we stop releasing 4.x workspace releases. Some design ideas can be found in [1]. Feel free to add your input to the Wiki page. Given the low number of 3rd party decorations I am not (yet) planning to give an ABI promise on the new API when it gets released. Kind Regards Martin Gräßlin [1]: http://community.kde.org/KWin/Decoration
Here is the fix for bug: https://git.reviewboard.kde.org/r/104380/
Although this bug report is based on a rather out-dated version of KDE and QtCurve, as the new QtCurve developer, I would like to ask if this issue have been fixed since the review doesn't seem to be merged yet. Is there any workaround I need to add in QtCurve?
(In reply to comment #3) > Although this bug report is based on a rather out-dated version of KDE and > QtCurve, as the new QtCurve developer, I would like to ask if this issue > have been fixed since the review doesn't seem to be merged yet. Is there any > workaround I need to add in QtCurve? I cannot say for QtCurve, but Oxygen has specific rendering code for non-composited mode and we know from other decorations that they have problems in one or the other rendering mode. Anyway: I expect such issues to be solved in the Qt5 based KWin.
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years and I will be closing this bug.