Bug 252654 - KWin doesn't respond when wine is started and compositing is enabled
Summary: KWin doesn't respond when wine is started and compositing is enabled
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (other bugs)
Version First Reported In: unspecified
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-09-28 15:53 UTC by Kiril Vladimiroff
Modified: 2018-10-27 02:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kiril Vladimiroff 2010-09-28 15:53:21 UTC 
Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

Every time when I decide to execute some app through wine I have to turn off desktop effects. Otherwise kwin stops responding, mouse is moving slow for 7-8 seconds.

Same thing happens after stopping wine and most of the times it's not for a few seconds, but until restart.



Reproducible: Always

Steps to Reproduce:
1. Make sure Desktop Effects are enabled
2. Start some wine application
3. Try to move your mouse, or minimize some window
Comment 1 Thomas Lübking 2010-09-29 01:03:56 UTC 
- does this happen with _all_ wine applications or only such using a 3d API (opengl/d3d)?
- in case of the latter: does it also happen with native gl apps?
- what's your gpu?

suspend/resume compositing could get you out of the issue.
Comment 2 Kiril Vladimiroff 2010-10-06 23:31:12 UTC 
(In reply to comment #1)
> - does this happen with _all_ wine applications or only such using a 3d API
> (opengl/d3d)?

Nope, it happens with _ALL_ applications, that I try to start with wine.

> - what's your gpu?
Intel 4500HD

> suspend/resume compositing could get you out of the issue.
I get myself out of it, with going to tty2 and killing all wine processes, but the point is not to get there :)
Comment 3 Martin Flöser 2014-01-08 13:51:27 UTC 
late reply: is this still an issue with newer versions of wine and/or KWin?
Comment 4 Martin Flöser 2016-11-02 13:29:02 UTC 
is this still an issue with newer versions of wine and/or KWin?
Comment 5 Andrew Crouthamel 2018-09-26 22:09:02 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 6 Andrew Crouthamel 2018-10-27 02:07:59 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!