When I start Wine application (Battle.net Launcher), the system completely freezes. I can only move mouse cursor, nothing else. This bug appeared after Plasma 5.4.1. I tried to install Plasma 5.4.49.9999 (development version of 5.4.x) and Plasma 9999 (development version of Plasma 5.5), but it also appeared there. Output of journalctl is in attachment. Reproducible: Always
Created attachment 94605 [details] journalctl output
Journalctl is useless. Please attach the output of "qdbus org.kde.KWin /KWin supportInformation" Suspending the compositor (after dumping above info, SHIFT+Alt+F12) will likely allow you to run battle.net. > This bug appeared after Plasma 5.4.1 What does that mean? Plasma 5.4.1 was good any anything after bad, or an update (from what) to Plasma 5.4.1 caused this. Did you also update other things (notably the graphics driver?)
Created attachment 94606 [details] qdbus org.kde.KWin /KWin supportInformation
(In reply to Thomas Lübking from comment #2) > Please attach the output of "qdbus org.kde.KWin /KWin supportInformation" Output of "qdbus org.kde.KWin /KWin supportInformation" is in attachment. > Suspending the compositor (after dumping above info, SHIFT+Alt+F12) will > likely allow you to run battle.net. I tried to switch from OpenGL 3.1 to OpenGL 2.0, then to XRandr, but bug didn't dissappeared. I'll try to switch off effects. > > This bug appeared after Plasma 5.4.1 > What does that mean? Plasma 5.4.1 was good any anything after bad, or an > update (from what) to Plasma 5.4.1 caused this. > > Did you also update other things (notably the graphics driver?) I noticed, that this bug appeared when I updated Plasma 5.4.0 to Plasma 5.4.1. I didn't update neither graphics drivers nor Wine version in that day.
> Compositing Type: XRender ;-) Can you please do the same with gl compositing? (so it prints drivers and used backend etc.) The xrender backend hasn't been touched for quite a while, but a stuck driver may require a reboot to clear the stage (or just reload the GPUs kernel module and restart X11)
Created attachment 94607 [details] qdbus org.kde.KWin /KWin supportInformation - 2
(In reply to Thomas Lübking from comment #5) > > Compositing Type: XRender > ;-) > > Can you please do the same with gl compositing? (so it prints drivers and > used backend etc.) > The xrender backend hasn't been touched for quite a while, but a stuck > driver may require a reboot to clear the stage (or just reload the GPUs > kernel module and restart X11) Yes, it's in attachment. I always used OpenGL 3.1, but I tried to switch modes today and when XRandr also didn't help, I started to write here. That's why you saw XRandr in my first report. Now I switched to OpenGL 3.1 back.
First, see whether it works with suspended compositor. If yes, log out and back in (you'll have to restart the X11 server), then try KWIN_EXPLICIT_SYNC=0 kwin_x11 --replace & (this restarts KWin) and see what happens. What's btw. the output of "grep -i triple /var/log/Xorg.0.log"?
In my case, switching to xrender or disabling compositor solves the problem. I use amd video card with open source radeon driver. "grep -i triple /var/log/Xorg.0.log" shows nothing.
Created attachment 94773 [details] qdbus org.kde.KWin /KWin (3)
@Victor: please try without EGL @Rinaldus: does it also freeze when suspending compositor?
waiting for feedback from comment #11
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!
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!