Summary: | kwin crash on alt+tab | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Martin Bednar <martin+kde> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WAITINGFORINFO | ||
Severity: | crash | CC: | martin+kde |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.6.4 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | kwin supportinformation |
Description
Martin Bednar
2016-06-16 16:34:36 UTC
Created attachment 99534 [details]
kwin supportinformation
Welcome to the most epic bug of Qt 5.5, update to 5.6.1 asap - every client code might randomly crash. *** This bug has been marked as a duplicate of bug 341497 *** Oh I think this one is actually a different case.
> #10 0x00007f1c39ede409 in QXcbEglWindow::create (this=0x2e27ff0) at qxcbeglwindow.cpp:83
Qt is using EGL instead of GLX and that probably doesn't work. Why did you compile Qt to prefer EGL?
bug #353606 suggests it's due to OpenGL being broken entirely (what would explain the disabled compositor) and probably the reason why (iff) the "wrong" GL api is used. (In reply to Martin Gräßlin from comment #3) > Qt is using EGL instead of GLX and that probably doesn't work. Why did you > compile Qt to prefer EGL? TBH I don't remember actively making that choice, my combination of use flags kind of forced me into it. Right now I'm upgrading to qt 5.6.1 (with the same useflags) and I'll report back when done. please check the output of "glxinfo" - if the other bug is right, your gl installation is broken. qtquick then simply doesn't work. (In reply to Thomas Lübking from comment #6) > please check the output of "glxinfo" - if the other bug is right, your gl > installation is broken. qtquick then simply doesn't work. GL works ok : OpenGL renderer string: Gallium 0.4 on AMD CAYMAN (DRM 2.43.0, LLVM 3.8.0) Kodi is running right now, and warzone2100 starts. This is weird : compositing gets disabled the moment I set kodi to fullscreen... hadn't noticed that before. |