Bug 285131

Summary:	KWin freezes when activating Desktop grid, present windows, or taskbar thumbnails
Product:	[Plasma] kwin	Reporter:	searchfgold67899
Component:	effects-window-management	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	Keywords:	triaged
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description searchfgold67899 2011-10-27 20:22:13 UTC

Version:           unspecified (using KDE 4.6.5) 
OS:                Linux

Exactly what it sys on the tin - I also notice that when I run "kwin --replace", it shows that I have the NV30 Graphics card, whereas I actually have the NV34 (nVidia)
The problem is not present in XRender.
Every time this problem is present, I can activate and deactivate the desktop cube to refresh the contents of the screen. In most cases, I can also get to a terminal and restart kwin, and it begins working perfectly again and all my work is saved.

Reproducible: Always

Steps to Reproduce:
Activate any of the effects I described.

Actual Results:  
KWin freezes.

Expected Results:  
Should have not froze.

Comment 1 Thomas Lübking 2011-10-27 20:38:53 UTC

try to set the scale method to "smooth" instead of "accurate" and please report the outcome.

> I have the NV30 Graphics card, whereas I actually have the NV34
try glxinfo, does it report an NV34?
If not: the NV30 (FX5800) is theoretically much faster than the NV34 (FX5200)

Comment 2 searchfgold67899 2011-11-02 20:17:01 UTC

> try to set the scale method to "smooth" instead of "accurate" and please report
> the outcome.
OK, it's fixed now! Thank you so much!!!
> > I have the NV30 Graphics card, whereas I actually have the NV34
> try glxinfo, does it report an NV34?
> If not: the NV30 (FX5800) is theoretically much faster than the NV34 (FX5200)
I don't get it :s ... glxinfo reports that I have the NV34.

Comment 3 Martin Flöser 2011-12-10 08:43:12 UTC

probably driver problem in combination with lanczos filter. If you use the nouveau driver, switch to the proprietary one.

Comment 4 searchfgold67899 2012-04-05 14:37:01 UTC

Switching the scaling method from "accurate" to "smooth" no longer fixes this problem.

Comment 5 Martin Flöser 2012-04-05 14:54:04 UTC

Could you please provide some more information about your system. Have you updated the KDE Plasma version in the meantime (4.6 is no longer supported), have you updated the drivers? Could you please provide the output of glxinfo?

In case you use nouveau please install the proprietary drivers.

Comment 6 searchfgold67899 2012-04-05 16:11:00 UTC

Never mind, it does. Have a nice day.

Comment 7 searchfgold67899 2012-04-05 16:11:48 UTC

Never mind, it does. Have a nice day.

Comment 8 Andrew Crouthamel 2018-09-23 02:41:24 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 9 Andrew Crouthamel 2018-10-27 02:43:35 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!