Bug 341110 - KWin-5.1.1 becomes unusable on rare occassions
Summary: KWin-5.1.1 becomes unusable on rare occassions
Status: RESOLVED DUPLICATE of bug 339235
Alias: None
Product: kwin
Classification: Plasma
Component: aurorae (show other bugs)
Version: 5.1.1
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-20 00:23 UTC by Armin K.
Modified: 2014-11-27 16:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of the broken KWin (480.68 KB, image/jpeg)
2014-11-20 00:24 UTC, Armin K.
Details
supportInfo after KWin becomes unusable (4.49 KB, text/plain)
2014-11-20 11:56 UTC, Armin K.
Details
supportInfo when KWin is working fine (4.49 KB, text/plain)
2014-11-20 11:56 UTC, Armin K.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Armin K. 2014-11-20 00:23:11 UTC
When using KWin-5.1.1 in combination with either Plasma 5.1.1 or LXQt-0.8.0, on very rare occassions KWin will become unusable, displaying a gray color all over the screen. I have managed to create a screenshot with my mobile phone (a screenshot of overview (mouse moved to the top left corner)) that displays what KWin actually renders. It is still running though, since all effects seem to be working (the top left corner, for example) but I can't see anything.

It happens when I close a window, sometimes when I move it, etc. I am not sure how to reproduce it, since it's very hard to do so.

My setup is KDE Plasma-5.1.1, KDE Frameworks-5.4.0, Qt-5.3.2, Xorg-Server-1.16.2, Xf86-video-Intel-2.99.916 with SNA and Present enabled, DRI3 and TearFree disabled. MesaLib-10.3.3 and Linux Kernel 3.17.3.

Journal managed to capture these messages, although they don't seem that much useful:

Nov 20 01:07:02 krejzi kwin_x11[527]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 24201, resource id: 60817533, major code: 15 (QueryTree), minor code: 0
Nov 20 01:07:02 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:02 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"
Nov 20 01:07:02 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:02 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"
Nov 20 01:07:02 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:02 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"
Nov 20 01:07:02 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:02 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"
Nov 20 01:07:02 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:02 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"
Nov 20 01:07:02 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:02 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"

... several lines repeated ...

Nov 20 01:07:03 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"
Nov 20 01:07:03 krejzi kwin_x11[527]: file:///usr/lib/qt5/qml/QtQuick/Controls/Styles/Base/ButtonStyle.qml:153:31: QML Item: Binding loop detected for property "implicitWidth"
Nov 20 01:07:04 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"

... several lines repeated ...

Nov 20 01:07:08 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"
Nov 20 01:07:08 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:08 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"

... several lines repeated ...

Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( update texture ):  "GL_INVALID_OPERATION"
Nov 20 01:07:09 krejzi kwin_x11[527]: GL error ( PostPaint ):  "GL_INVALID_OPERATION"



And so on, until I restart it. I was suggested to use MESA_DEBUG to try and figure out what GL_INVALID_OPERATION is related to, but even if I set MESA_DEBUG=1 in .pam_environment (and hence graphical session, since sddm uses PAM and sets it correctly), I haven't managed to capture anything as you can see.

Reproducible: Couldn't Reproduce
Comment 1 Armin K. 2014-11-20 00:24:12 UTC
Created attachment 89640 [details]
Screenshot of the broken KWin
Comment 2 Armin K. 2014-11-20 00:25:49 UTC
Forgot to add: This laptop has sandybridge graphics (HD3000) and radeon hd6470m discrete gpu (hybrid graphics), but the second one isn't used at all.
Comment 3 Martin Flöser 2014-11-20 08:33:26 UTC
please provide output of:
qdbus org.kde.KWin /KWin supportInformation

preferable once when it's working and once when it is broken.

Also have a look at dmesg whether there are any GPU related messages and 
please also look into /var/log/Xorg.0.log to see for any reported warnings or 
errors when the problem happens.
Comment 4 Armin K. 2014-11-20 11:56:30 UTC
Created attachment 89648 [details]
supportInfo after KWin becomes unusable
Comment 5 Armin K. 2014-11-20 11:56:59 UTC
Created attachment 89649 [details]
supportInfo when KWin is working fine
Comment 6 Armin K. 2014-11-20 11:58:51 UTC
Both of the supportInfo's seem to be exactly the same. I had a problem using qtdbus from VT after kwin becomes unusable, but I think I did it right by setting DISPLAY=:0 and running qtdbus while doing a VT switch to a "broken" session. That's the only time I could get it to run correctly.

As for dmesg, there's nothing related to intel gpu. Only discrete one powering up and down when xserver restarts (radeon's DPM). As for Xorg.0.log there's nothing that I can't usually find there.
Comment 7 Thomas Lübking 2014-11-20 12:57:27 UTC
> Current Plugin: aurorae

Please see whether you can reproduce this with the oxygen decoration
(yes, "but i'm using breeze!!" - it's atm. "only" an aurorae theme)

Very likely bug #339235
Comment 8 Armin K. 2014-11-20 13:03:34 UTC
(In reply to Thomas Lübking from comment #7)
> > Current Plugin: aurorae
> 
> Please see whether you can reproduce this with the oxygen decoration
> (yes, "but i'm using breeze!!" - it's atm. "only" an aurorae theme)
> 
> Very likely bug #339235

Okay, I've switched to Oxygen for the time being. I'll wait a bit to see if the issue happens again.
Comment 9 Armin K. 2014-11-27 14:26:29 UTC
After using Oxygen for a week, I haven't seen a single crash as described in the initial report. I suppose the issue is in Breeze, as noted by Thomas. Please do whatever the right thing is to do with this ticket.
Comment 10 Thomas Lübking 2014-11-27 16:49:33 UTC

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