Bug 306195

Summary:	When Desktop Effects enebled (kwin, compositing) results to broken applications dropdown menus.
Product:	[Plasma] kwin	Reporter:	firewalker <firew4lker>
Component:	compositing	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	4.9.0
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
URL:	https://bbs.archlinux.org/viewtopic.php?id=137713
Latest Commit:		Version Fixed In:

Description firewalker 2012-09-03 12:45:26 UTC

When KDE's desktop effects are enabled the drop down menus of non KDE application, that don't use the KDE's theme (e.g. gtk application with Clearlooks or other theme), are broken.

If the theme for non KDE applications changes to oxygen/oxygen-gtk the problem goes away. 

My graphic cards is an Intel 3000 for the laptop and Nvidia 8400 GS for the desktop.

The problem is there since 4.8.1

Reproducible: Always

Steps to Reproduce:
1. Enable Desktop effects.
2. Open a gtk application with Clearlooks theme (e.g. Firefox, CodeBlocks) or a Qt one (e.g. KVIRC.)
3. Try to navigate across the dropdown menus.
Actual Results:  
http://i.imgur.com/wKAOp.png (Firefox)
http://i.imgur.com/2t8Js.png (KVIRC)


https://bbs.archlinux.org/viewtopic.php?id=137713

https://bbs.archlinux.org/viewtopic.php?pid=1156049#p1156049

Comment 1 Thomas Lübking 2012-09-03 14:06:53 UTC

Only happens if there's no showing animation (fade, scale, generic animations, stuff like that) I assume?

> The problem is there since 4.8.1
Please, prettyprettyprettypleasewithsugarontop:

            DO NOT WAIT SIX MONTHS BEFORE REPORTING AN ISSUE!

Thanks ;-)

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

Comment 2 firewalker 2012-09-03 15:27:59 UTC

Yes, it only happens when there's no showing animation.

I was following a bug that seamed relative to this problem. It was to be included to 4.9. After I upgraded and it was still present I filed the report.

Thanks for the info.

Comment 3 Thomas Lübking 2012-09-03 15:41:43 UTC

(In reply to comment #2)

> I was following a bug that seamed relative to this problem.
Which one?