Summary: | kwin crash when enabling GL desktop effects | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Adrian Baugh <mail> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Adrian Baugh
2011-08-07 16:57:42 UTC
An addition to the above - given the crash happened in a blur shader I tried switching off the Blur effect (blue background of semitransparent windows) and this works around the problem perfectly. I've quickly tried the other available effects and although there are a couple that flatly refuse to start none of the others cause kwin to crash, so it looks like there is a real bug there. The blur effect is the only one that calls glGenProgramsARB() which causes all those crashes. They all (probably, at least all with complete traces) walk through __indirect_glProgramParameters4fvNV and end up in memcpy what's a bit too reproducable to be a general memory corruption in kwin but is rather a mesa issue?! Ensure to enable direct rendering in "kcmshell4 kwincompositing", "advanced" tab and to NOT have LIBGL_ALWAYS_INDIRECT=1 exported - The line in the kwin output should say: Direct rendering: yes *** This bug has been marked as a duplicate of bug 270818 *** |