Bug 243889

Summary:	When KWin effects are on with Direct Rendering disabled, switching widget theme causes screen to freeze
Product:	[Plasma] kwin	Reporter:	Marcus Harrison <marcus>
Component:	compositing	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	0.2
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Marcus Harrison 2010-07-07 21:55:28 UTC

Version:           0.2 (using Devel) 
OS:                Linux

When desktop effects are on with Direct Rendering disabled, switching the widget theme makes the entire screen besides the mouse unresponsive. Applications (and KWin) still respond to mouse and keyboard input, but nothing on-screen changes, making it unusable until KWin or X is restarted.

Reproducible: Always




OS: Linux (i686) release 2.6.32-24-generic
Compiler: cc

Comment 1 Christoph Feck 2010-07-08 01:41:37 UTC

If this can be reproduced only with compositing effects, it is a KWin bug.

Comment 2 Thomas Lübking 2010-07-08 16:28:45 UTC

- GPU/driver?

- KDE version (4.4 or 4.5 beta / trunk)

- does SHIFT+ALT+F12 (suspend compositing) /after/ the freeze "fix" it?

- by "widget theme" do you mean 
a) the plasma theme (desktop "widgets") or 
b) the Qt style (buttons, scrollbars, etc. - QWidgets)

- which kwin decoration do you use? (oxygen, aurorae, ...)

Comment 3 Marcus Harrison 2010-07-30 23:13:19 UTC

GPU: Intel Atom (945GME) Integrated Graphics with Mesa driver
KDE 4.4.92 (RC2).
Yes, temporarily disabling using Shift+Alt+F12 unfreezes ("fixes") the screen.
Oxygen widget theme: theme for applications, not for the desktop (so "b", QWidgets).
Using the Oxygen windeco.

Sorry it took me so long to reply - I didn't catch the message in my inbox.

Comment 4 Thomas Lübking 2010-08-27 01:04:47 UTC

this is most likely related to bug #241402 and LIBGL_ALWAYS_INDIRECT, please try to add
export LIBGL_ALWAYS_INDIRECT=1
to ~/.xprofile, login and out and see whether the issue remains

(sorry for the delay myself...)

Comment 5 Martin Flöser 2010-08-28 14:54:03 UTC

I am very sure that this is the same bug. Please reopen if it's not the same one. Thanks

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