Bug 248562

Summary: Blur effect renders the system unusable and unstable (Core 2 Duo 2.4GHz, 4GB RAM, Intel Graphics 4 Series)
Product: [Plasma] kwin Reporter: Aitor <mail>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Glxinfo file

Description Aitor 2010-08-21 01:08:29 UTC
Created attachment 50805 [details]
Glxinfo file

Version:           unspecified (using KDE 4.5.0) 
OS:                Linux

Once I installed kde 4.5 blur was activated by default and my system became really slow. Some dialogs blinked.
Sometimes, after some usage, the X server crash.
Looking at the CPU usage, it was above normal (30%-50% on either cores) but windows didn't move smoothly.
I'm sorry, but I'm back in kde4.4 now (other issues regarding to dual screen configuration made me downgrade to 4.4)

Reproducible: Always

Steps to Reproduce:
Enable blur effect


Actual Results:  
Huge drop in performance
Sometimes X crashes after some usage.
Comment 1 Martin Flöser 2010-08-21 07:38:39 UTC
It is totally fine to disable the blur effect if it is causing problems for you. That's why it is optional, but enabled by default, because only drivers supporting this effect can use it. Unfortunately some drivers say that they support it, but in truth they don't. That is not our bug, but theirs. We even introduce a blacklist to disable blur for broken drivers. Feel free to attach your driver information to the duplicate bug, so that this driver can be blacklisted in the next version.

Please note, that no application is able to crash the X server - this would be a serious security problem if it were possible. As you mention that X is crashing, it indicates that your used driver is very buggy. I'm sorry to say but there is nothing we can do about it, such issues have to be fixed by the driver developers.

*** This bug has been marked as a duplicate of bug 242985 ***