Version: SVN (using Devel) OS: Linux Hi, I'm running KDE 4.5 Beta 2 on openSUSE 11.2. When using the zoom effect from Kwin, there is a bug with Blur (in the Calendar plasmoïd for example). I also noticed that the windows' preview in the Task Manager are also buggy with the zoom activated. Reproducible: Always Steps to Reproduce: Enable Zoom and Blur in KDE System Settings. Zoom the deskop ("Meta + +" by default) Show the calendar by clicking on the clock Actual Results: The background of the calendar is not blurred but black. When you move the mouse, the blur effect may apply to part of the calendar. Expected Results: The Blur effect should apply the same way whether or not the zoom effect is activated. I use the Air desktop theme from KDE 4.5 Beta 2.
I'm not sure if this is the same issue, but I'm also seeing some problems with Blur + Zoom, namely that the area being blurred 'moves' with (counter to) the zoom area and leaves remnant image traces behind (see attached image). KDE 4.5.1 on PCLinuxOS (using latest svn bespin style with ARGB and blur enabled) To reproduce: 1. Activate Blur and Zoom KWin effects 2. Open a window that shows the Blur effect 3. Zoom in 4. Pan around the desktop Actual results: The blurred area moves in the opposite direction as the mouse relative to the window, leaving an image trail behind. Expected Results: The blurred area remains fixed to the window (i.e. moves with the window as the mouse and zoom area moves)
Created attachment 51254 [details] Screenshot showing the offset blur area and left-lover image trail
*** Bug 265024 has been marked as a duplicate of this bug. ***
Another way to reproduce (kde 4.7): activate blur plugin make sure area unther the bottom panel is blurred zoom in note that the lower part of the screen is blurred, even if the panel is not visible anymore. ** so: zoom plugin does not update the blur aera **
(In reply to comment #4) > ** so: zoom plugin does not update the blur aera ** FTR: "And should not." The blur area is set by the clients, manipulating it from an effect would partially not work (broken by interim client updates) and in doubt leave a wrong state. The blur effect needs to recalculate the area with the zoom transformations so in doubt must be ensured to be invoked after zooming has manipulated the data and/or the zoom effect must export the transformation globally.
Something new about this little bug? Or it will catch KDE 5.0?
(In reply to comment #6) > Something new about this little bug? Or it will catch KDE 5.0? Comments like these do not really raise the motivation of the developer to work on the bug. We have enough open bug reports we can choose from for working on them. At the time of this writing there are ~300 open bug reports for KWin. For a user it is very impossible to judge whether a bug is "little" or "heavy", for a user it is impossible to know how long it will take to fix this bug.
(In reply to comment #7) > (In reply to comment #6) > > Something new about this little bug? Or it will catch KDE 5.0? > Comments like these do not really raise the motivation of the developer to > work on the bug. We have enough open bug reports we can choose from for > working on them. At the time of this writing there are ~300 open bug reports > for KWin. > > For a user it is very impossible to judge whether a bug is "little" or > "heavy", for a user it is impossible to know how long it will take to fix > this bug. Sorry for that, I was just curious about the state of this bug. I found it last days and, trying to submit a bug about it, I found this bug report and the last activity beign on september last year. I understand that nobody is paid to fix bugs here, I'm also working on some open-source project without beign paid, but I just wanted to bring this bug into attention.
*** Bug 279566 has been marked as a duplicate of this bug. ***
This bug is still valid for KWin 4.96. On the Neon 5 iso, there is a plama panel on the bottom. If you zoom in, a white rectangle stays at the bottom of the screen even when the panel is not in the zoomed area.
*** Bug 337398 has been marked as a duplicate of this bug. ***
*** Bug 341475 has been marked as a duplicate of this bug. ***
*** Bug 361561 has been marked as a duplicate of this bug. ***
*** Bug 364199 has been marked as a duplicate of this bug. ***
*** Bug 347849 has been marked as a duplicate of this bug. ***
*** Bug 372264 has been marked as a duplicate of this bug. ***
Any particular reason this bug is still marked as UNCONFIRMED (!?)
(In reply to Antonio Orefice from comment #17) > Any particular reason this bug is still marked as UNCONFIRMED (!?) This is a common confusion among users. The state has no influence on the bug at all. For us fixing bugs it's not a question of whether the bug is in unconfirmed or confirmed state.
Yes, yes, i did not mean that. I really mean just what i asked :)
It's unconfirmed because we don't care about the state. We don't go into the bugs and mark them as confirmed. It's as simple as that: it does not have any meaning.
This bug is still present, and annoying, in 5.9.3.
*** Bug 383138 has been marked as a duplicate of this bug. ***
Created attachment 115809 [details] Screenshot of the zooming effect creating artifacts for the blur effect
I can confirm that this causes issues still in 5.14 to an extent, I'd like to keep my desktop pretty while also keeping my eyesight. The problem with the blur effect is that so long as there's some sort of transparency, there seems to be some visual artifacts that I'm not sure how they come to be.
(In reply to Brandin Starliper from comment #24) > I can confirm that this causes issues still in 5.14 to an extent, I'd like > to keep my desktop pretty while also keeping my eyesight. The problem with > the blur effect is that so long as there's some sort of transparency, there > seems to be some visual artifacts that I'm not sure how they come to be. I can also confirm. Doesn't seem to matter if it is widget, terminal etc. Also I can see my background image even after I switched it, but is like a combo of the old image and the newer one, quite weird.
*** This bug has been marked as a duplicate of bug 447670 ***