Version: unspecified (using KDE 4.4.4) OS: Linux After two years of Gnome, I switched to KDE (OpenSuSE) and just minutes ago I was experimenting with various features of the DE, Including desktop effects. I enabled Wabbly windows, enabled advanced mode, and set the stiffness to max. As a result everything started flying around on my desktop and was left helpless. I was forced to log out and am now using 'root' to write this report. The problem is that when the stiffness is at max, once the wobbling starts, it NEVER stops. I waited for about five minutes and there was no improvement. THE WABBLING MUST STOP AFTER SOME SOME INSTEAD. THIS IS A CRITICAL ISSUE BECAUSE I AM NOW UNABLE TO USE ANYTHING IN THE ACCOUNT I WAS LOGGED IN, DO TO CRAZY WOBBLING. How can I do one of the following: Disable desktop effects in the particular account, Disable Wobbly windows, or Decrese the stiffness ?????????????????????????????????? Reproducible: Always
I was able to change the unwanted behavior myself. No help needed anymore on that part. Hope this gets fixed soon.
To suspend or resume compositing by kbd shortcut use SHIFT+ALT+F12 To disable "Wobbly windows" call "kcmshell4 kwincompositing", select "all effects" and uncheck the effect, then click apply. In general the free wobbly windows settings are for "experts" ie. you need to know about fluid mech, my personal suggestion would be 40/50/4 - but i don't like the effect at all ;-) *** This bug has been marked as a duplicate of bug 205866 ***
"In general the free wobbly windows settings are for "experts" ie. you need to know about fluid mech" I still don't buy that explanation... I for one managed to find usable settings by simple black-box experimentation with different slider values, without reading up on theoretical fluid mechanics first... (It just took quite a bit of time, the bug described definitely was an obstacle...) Also it's kind of funny to tell user's they shouldn't play with the expert settings, when this is the *only* way to get a wobbly windows effect that is not totally exaggerated an unusable (at least in my opinion) (see bug 209522).