Bug 252095

Summary: When desktop effects are enabled, knotify popups are transparent
Product: [Plasma] kwin Reporter: tbohaning
Component: compositingAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: asraniel, plasma-bugs
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description tbohaning 2010-09-23 06:12:06 UTC 
Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

When ever Desktop effects are enabled the notification popups are transparent. With a dark background, the notifications are very difficult to read.

Need a way to turn off transparency for notifications.

Reproducible: Didn't try

Steps to Reproduce:
Install a dark background. I use "There is Rain on the Table". Enable thru right click on background. Choose Desktop Settings. Install background.

Disable Desktop Effects in System Settings/Desktop Effects. 
Run kdialog --passivepopup "This is a test" 5
Note that the popup is solid.

Go back and enable Desktop Effects.
Run kdialog --passivepopup "This is a test" 5
Note that the popup is transparent. 
There is no place that I've been able to identify to turn off or adjust the level of transparency.

Actual Results:  
Popup is transparent

Expected Results:  
Popup should be solid color. A transparent popup is no readable with black text on a dark back ground.
Comment 1 Beat Wolf 2010-09-24 10:08:55 UTC 
this is probably the fault of a not working blur plugin in kwin.
Can you deactivate blur and test if it works better? plasma might need to be restarted.
Comment 2 tbohaning 2010-09-24 15:43:00 UTC 
That was it. My initial tests did include turning off each effect but didn't include the plasma restart.

Thanks for your help!
Comment 3 Thomas Lübking 2010-09-24 16:22:51 UTC 
please see the dupe, read here http://blog.martin-graesslin.com/blog/2010/07/blacklisting-drivers-for-some-kwin-effects/ and attach your gpu driver renderer/version string to the report

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