Summary: | [kwin] Desktop Effects on Intel Graphics | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Georg Grabler <ggrabler> |
Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | alexdw, ggrabler, u.almasov |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Chakra | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Georg Grabler
2011-07-24 11:38:48 UTC
please install also the debug symbols of Mesa. From what we have right now we only see that it crashes in the driver It's by 99.9% chance a dupe of bug #229796 According to a apparently related mozilla bug report[1] it might be because "Mesa versions up to 7.10 cause a BadLength error during the first GLX call when the server GLX version < 1.3." And a post suggests that it has been fixed upstream [2] but i don't know whether that is true and part of Mesa 10.3 (it's in the 7.10 branch and comitted before the 10.3 release at least - theoretically it should be in 10.1) @ Georg: does "glxinfo" segfault for you? (part of "mesa-demos") [1] https://bugzilla.mozilla.org/show_bug.cgi?id=632867 [2] http://cgit.freedesktop.org/mesa/mesa/commit/?id=cbe9fc12a64c3ae89fd1b20e9e165aa4b76293a5 Hi, and sorry for the late answer. Yes, glxinfo segfaults for me. I'll have to rebuild mesa here for debugging symbols, what can take some time (chakra build system needs some time to be set up). Will report back with a new backtrace as soon as I've done that. *sigh* Please try whether mesa from git master works for you. If not, exporting (best globally) LIBGL_ALWAYS_INDIRECT=1 will likely "workaround" this... Hi Thomas, I just recompiled mesa from the git master, and the effects work, the crash is not reproducable any longer. Thanks for the hint. Can be set on "solved" i guess, even though, most people won't have it solved :-). At least a bug which is _really_ "resolved upstream" then ;-) *** Bug 280263 has been marked as a duplicate of this bug. *** *** Bug 303534 has been marked as a duplicate of this bug. *** |