Version: unspecified (using KDE 4.6.1) OS: Linux When closing a window that has client side alpha channel shadows (e.g. Oxygen) you have a thick black border around the window. I don‘t know if this actually is the shadow (since I have black shadows which would match and I don‘t know if this border will be turkey/blue when using the default glow) but therer is a black border around the window that is being thrown against you. Reproducible: Always
no, there seems to be something fishy. I noticed during port to GLES. Explosion is very high on my "to be removed" list, btw.
I just reported it, not that I will ever going to be using this Epilepsy-causing effect :D
Created attachment 73518 [details] Screenshot under 4.9.0 The effect as well as its bug is still present in 4.9.0. ;-) Personally I do not care for the effect. If you do not care to fix the bug, see my comment as friendly reminder to delete this effect fro 4.10 (or even 4.9.1/4.9.2 if rules allow it). :-) PS, the usual for KWin reports: Options ======= focusPolicy: 0 nextFocusPrefersMouse: false clickRaise: true autoRaise: false autoRaiseInterval: 0 delayFocusInterval: 0 shadeHover: false shadeHoverInterval: 250 tiling: false tilingLayout: 0 tilingRaisePolicy: 0 separateScreenFocus: false activeMouseScreen: false placement: 4 focusPolicyIsReasonable: true borderSnapZone: 10 windowSnapZone: 10 centerSnapZone: 0 snapOnlyWhenOverlapping: false showDesktopIsMinimizeAll: false rollOverDesktops: true focusStealingPreventionLevel: 1 legacyFullscreenSupport: false operationTitlebarDblClick: commandActiveTitlebar1: 0 commandActiveTitlebar2: 30 commandActiveTitlebar3: 2 commandInactiveTitlebar1: 4 commandInactiveTitlebar2: 30 commandInactiveTitlebar3: 2 commandWindow1: 7 commandWindow2: 8 commandWindow3: 8 commandWindowWheel: 31 commandAll1: 10 commandAll2: 3 commandAll3: 14 keyCmdAllModKey: 16777251 showGeometryTip: false electricBorders: false electricBorderDelay: 150 electricBorderCooldown: 350 electricBorderPushbackPixels: 1 electricBorderMaximize: false electricBorderTiling: false borderlessMaximizedWindows: false killPingTimeout: 5000 hideUtilityWindowsForInactive: true inactiveTabsSkipTaskbar: false autogroupSimilarWindows: false autogroupInForeground: true compositingMode: 1 useCompositing: true compositingInitialized: true hiddenPreviews: 1 unredirectFullscreen: false glSmoothScale: 2 glVSync: true xrenderSmoothScale: false maxFpsInterval: 17 refreshRate: 0 vBlankTime: 6144 glDirect: true glStrictBinding: false glStrictBindingFollowsDriver: true Compositing =========== Qt Graphics System: raster Compositing is active Compositing Type: OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce 9200M GS/PCIe/SSE2 OpenGL version string: 3.3.0 NVIDIA 295.49 Driver: NVIDIA Driver version: 295.49 GPU class: G80/G90 OpenGL version: 3.3 X server version: 1.10.4 Linux kernel version: 3.1.10 Direct rendering: yes Requires strict binding: no GLSL shaders: yes Texture NPOT support: yes OpenGL 2 Shaders are used Loaded Effects: --------------- kwin4_effect_login kwin4_effect_coverswitch kwin4_effect_translucency kwin4_effect_screenshot kwin4_effect_desktopgrid kwin4_effect_diminactive kwin4_effect_magiclamp kwin4_effect_fade kwin4_effect_explosion kwin4_effect_dialogparent kwin4_effect_highlightwindow kwin4_effect_taskbarthumbnail kwin4_effect_presentwindows kwin4_effect_blur kwin4_effect_logout kwin4_effect_dashboard kwin4_effect_outline Currently Active Effects: ------------------------- kwin4_effect_translucency kwin4_effect_diminactive kwin4_effect_fade kwin4_effect_explosion kwin4_effect_blur
this bug is still present in KDE 4.10 RC1. (Intel SB, Kubuntu Raring) at the same time, also this bug https://bugs.kde.org/show_bug.cgi?id=306376 is present. I strongly suggest to remove this fancy effect before final release as it is plain broken and makes the desktop unusable.
*** This bug has been marked as a duplicate of bug 312176 ***
The older bug is not a dupe of the newer. It's the other way around. ;-)
*** Bug 312176 has been marked as a duplicate of this bug. ***
This is a report of a disfunction, the other is a collection of such in a task, explicitly created for that reason. Please don't mess up my git history for stupid "i'm first" ego junk, thanks. *** This bug has been marked as a duplicate of bug 312176 ***
Sorry for the not so kind tone - you certainly had best intentions by ordering the bugs. I'm just not very kind around christmas (turns me into grumpy smurf every year, i wake up being totally pissed ;-) The reason for the inverse dupe order is that the "dupe" is actually none, but i just linked explosion effect related bugs to that collector so that by closing it with a dropping commit, they all get closed automatically. In case the explosion effect would actually not get dropped, i'd of course have to dispatch (undupe / reopen) them again.