Bug 283859

Summary:	Upon disabling compositing, kicker shadow as well as desktop widget popup shadows are replaced with black borders
Product:	[Unmaintained] plasma4	Reporter:	Donatas Glodenis <dg>
Component:	desktop	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	adaptee, aldo-public, b7.10110111, benjarobin+kde, mgraesslin, notmart, post, thelwyn
Priority:	NOR
Version:	4.8.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Black shadow around kicker

Description Donatas Glodenis 2011-10-12 13:37:58 UTC

Created attachment 64461 [details]
Black shadow around kicker

Version:           unspecified (using KDE 4.7.1) 
OS:                Linux

If I disable compositing at run-time, I get black borders around kicker menu, as well as around all panel/desktop widget popups. 

On the other hand, if I disable compositing at startup and restart KDE session, the borders are no longer painted black.

Reproducible: Always

Steps to Reproduce:
Log in with a brand new KDE session (at least, with composite enabled). Then
hit Alt+Shift+F12 to disable compositing, and open the K-Menu, or hover on any item in the taskbar that has a popup.

Actual Results:  
It looks like in attached screenshots, black borders.

Expected Results:  
The border should be redrawn appropriately.

It does not depend on window manager – I switched to metacity and the effect was the same. Switching plasma theme does not seem to affect the problem – it is still there.

This happens on two computers with the same KDE version (4.7.1) but different os versions and different hardware: Laptop, Kubuntu 11.04/Intel 945GM and desktop, Kubuntu 11.10 beta/Radeon9200 video card, R200 driver.

Could it be related to bug 283414 ?

Comment 1 Kolia 2011-12-07 21:24:45 UTC

Still valid in kde 4.7.3

Comment 2 Aaron J. Seigo 2011-12-08 11:47:11 UTC

this is because KWindowSystem::compositingActive() is never getting updated; nor is its signal being emitted. this is a recent happening ...

Comment 3 Aaron J. Seigo 2011-12-08 11:47:15 UTC

*** Bug 283414 has been marked as a duplicate of this bug. ***

Comment 4 Aaron J. Seigo 2011-12-08 11:50:10 UTC

putting some debug output in KWindowSystem::x11Event, it doesn't seem damage events are being sent when compositing changes. perhaps the compositor atom isn't being set at all?

also tested without the EffectsWatcher in Plasma::Theme, just in case, and it had no effect.

Comment 5 Benjamin Robin 2012-01-02 22:17:09 UTC

Still valid in kde 4.7.4

Comment 6 Aldoo 2012-03-04 08:32:50 UTC

This is still in KDE 4.8.0.

Comment 7 Ruslan Kabatsayev 2012-04-21 13:42:37 UTC

Hmm, I didn't even know that this has ever worked. This bug is still present in 4.8.2.

Comment 8 Marco Martin 2012-06-25 14:52:25 UTC

even tough is the "opposite" is the same issue as this other bug: sometimes it doesn't nitice composite being enabled or disabled

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