Summary: | crash when trying to play game using wine | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | giluxxx |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | ||
Version: | 4.11.5 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
giluxxx
2014-02-16 13:41:59 UTC
driver bug, pot. due to multiple GL contexts. suspend the compositor before starting a game (Shift+Alt+F12) - you can also use a window rule to do that automatically. > used to be fine before update What update? KDE, kernel, MESA, wine, entier distro? *** This bug has been marked as a duplicate of bug 299333 *** well the update consisted of 120+ packages so hard to tell.. tried Shift+Alt+F12 then start game this results in a black screen with only mouse pointer visable... and nothing else happens.. only thing to snap out of it is doing Shift+Alt+F12 again which results in the same crash again seems a more general GL issue then and rather induced by wine/the game (while compositing is suspended, kwin neither holds a GL context nor impacts the scanout buffer, ie. "what you see on screen") I assume that glxgears works fine (w/ and w/o compositing)? Any related errors in ~/.xsession-errors, /var/log/Xorg.0.log, dmesg? You can also export MESA / libgl debug envs to check for issues: MESA_DEBUG=1 LIBGL_DEBUG=verbose glxinfo See http://www.mesa3d.org/envvars.html for a full reference. made me think.. glxgears works.. optirun glxgears works optirun -b primus glxgears invokes the bug.. guess this should be tackled by bumblebee team |