| Summary: | Segfault in KWin::ARBBlurShader::init | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | kovrov <kovrov+kde> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | crash | CC: | abhijeet.linux, andrew, asbaz, bobmano, bruno, cdf, chad, diego.ercolani, dlm659, droms, freekdekruijf, hendy, hrvoje.senjan, ingolf, jogimar.erik, juan.roldan, keha, lflerlage, ludmiloff, mail, Martin, mhoppstaedter, morowhind, muackl, null, p, randy_m1989, raul.ferriz, rudolfwetzels, salsa_temps, sclifcon, shiki.biomernok, Shininggg2000, systemshock2, thomas, v.babosha, woaiwode.jiejie, ystguing, zexnimer |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
glxinfo
glxinfo New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
kovrov
2011-04-13 11:29:25 UTC
crashes in glGenProgramsARB(1, &program);
either the driver claims ARB shader support but doesn't actually provide or this is a memory corruption.
a) the crash occurs in the blur effect, so disbale blurring to workaround it
b) please specify your GPU, driver and mesa version (in doubt attach a dump of "glxinfo > my.glxinfo.txt")
c) there's a memory corruption prone statement in the lanczos filter, so set the scale method to "smooth" ("kcmshell4 kwincompositing" / "advanced" tab)
Created attachment 58927 [details] glxinfo (In reply to comment #1) I would guess this is a memory corruption. As you can see I use Kubuntu Natty 64-bit. It was working fine before and got broken at some point around month ago. It's hard to say what exactly was changed - as it is an alpha release, updates happens almost daily. Quite often something breaks, but get fixed very quickly. Usually, but not this time. I didn't bother to reinstall system, but I have tried daily live cd (same distro - Kubuntu Natty) and kwin crashes there as well. My best guess that it is memcpy problem discussed here: https://bugzilla.redhat.com/show_bug.cgi?id=638477 Let me know if anything else is needed. "server glx vendor string: SGI" ... "OpenGL renderer string: Software Rasterizer" are you running this in VirtualBox or sth. similar? (In reply to comment #4) > "server glx vendor string: SGI" > ... > "OpenGL renderer string: Software Rasterizer" > > are you running this in VirtualBox or sth. similar? No, it is normal (real) installation. It is acer extensa 4630 laptop (intel gma 4500) could you please start kwin from a command line and paste the log output. The glxinfo does not match the crash. If it is software rasterizer OpenGL backend *should* not get enabled. Created attachment 58936 [details]
glxinfo
Indeed it was software rendering. After countless removing/installing and reconfiguring packages I got hardware opengl.
KWin still crashes on enabling blur effect. Restarting kwin (with --replace) doesnt provide much info as for some reason it starts without any of desktop effect plugins. And I have no idea how to restart it normally after that.
> KWin still crashes on enabling blur effect
With the /very/ same backtrace? Otherwise please attach the current one or make a new bugreport.
Looks like this issue affects not only me.. http://blog.martin-graesslin.com/blog/2011/04/why-blur-does-not-work-in-kubuntu-natty-with-intel/ That's not the same issue as the original bug and you have so far not provided information on the current blur "crash" (if that means a segfault at all) Sorry, cannot reproduce this anymore - after last update blur shader starts working for me again.. Given the invalid "software rasterizer" thing, the original bug has probably been a downstream issue (wrong/no driver installed or configured by either yourself or your distro) I assume the follow-up issue was that blurring wasn't activatable (due to the issues in the post you linked. discussion around this is apparently ongoing ;-) and this has also been (temp.) "fixed" by your distro by either patching mesa or kwin. So i'll close this one - the other one is dealt as bug #270942 *** Bug 273694 has been marked as a duplicate of this bug. *** *** Bug 274090 has been marked as a duplicate of this bug. *** *** Bug 275325 has been marked as a duplicate of this bug. *** *** Bug 279597 has been marked as a duplicate of this bug. *** *** Bug 280337 has been marked as a duplicate of this bug. *** *** Bug 281540 has been marked as a duplicate of this bug. *** *** Bug 281692 has been marked as a duplicate of this bug. *** *** Bug 281799 has been marked as a duplicate of this bug. *** *** Bug 284307 has been marked as a duplicate of this bug. *** *** Bug 284308 has been marked as a duplicate of this bug. *** *** Bug 284375 has been marked as a duplicate of this bug. *** *** Bug 284656 has been marked as a duplicate of this bug. *** *** Bug 286479 has been marked as a duplicate of this bug. *** *** Bug 287609 has been marked as a duplicate of this bug. *** *** Bug 289910 has been marked as a duplicate of this bug. *** Git commit 8ecd9befaf80cdf5963b7ef24588679db7515b63 by Martin Gräßlin. Committed on 31/12/2011 at 08:54. Pushed by graesslin into branch 'KDE/4.8'. Disable Lanczos and Blur for fglrx Too many crash reports in the fglrx driver when using ARB shaders. It's a pity to disable functionality for all fglrx users, but it's better than crash reports. Blur effect can still be enabled manually and Lanczos can still be enabled through the environment variable. REVIEW: 103556 Related: bug 286795 M +4 -0 kwin/effects/blur/blur.cpp M +4 -0 kwin/lanczosfilter.cpp http://commits.kde.org/kde-workspace/8ecd9befaf80cdf5963b7ef24588679db7515b63 *** Bug 290325 has been marked as a duplicate of this bug. *** *** Bug 290390 has been marked as a duplicate of this bug. *** *** Bug 290693 has been marked as a duplicate of this bug. *** Created attachment 67861 [details]
New crash information added by DrKonqi
kwin (4.7.2 (4.7.2) "release 5") on KDE Platform 4.7.2 (4.7.2) "release 5" using Qt 4.7.4
- What I was doing when the application crashed:
go with the mouse pointer for windows toolbar
-- Backtrace (Reduced):
#7 0x00007faa5786dd05 in __indirect_glProgramParameters4fvNV (target=1, index=11061332, num=1470845824, params=0x7faa562332a0) at /usr/include/bits/string3.h:52
#8 0x00007faa5a3c1ed9 in KWin::LanczosShader::init (this=0xa8c6b0) at /usr/src/debug/kde-workspace-4.7.2/kwin/lanczosfilter.cpp:669
#9 0x00007faa5a3c252c in KWin::LanczosFilter::init (this=0x8dca80) at /usr/src/debug/kde-workspace-4.7.2/kwin/lanczosfilter.cpp:76
#10 0x00007faa5a3c2e10 in KWin::LanczosFilter::performPaint (this=0x8dca80, w=0x9dd5c0, mask=262, region=..., data=...) at /usr/src/debug/kde-workspace-4.7.2/kwin/lanczosfilter.cpp:170
#11 0x00007faa5a3a7257 in KWin::Scene::finalDrawWindow (this=0x8dd1d0, w=0x9dd5c0, mask=262, region=<optimized out>, data=<optimized out>) at /usr/src/debug/kde-workspace-4.7.2/kwin/scene.cpp:319
*** Bug 291743 has been marked as a duplicate of this bug. *** *** Bug 292071 has been marked as a duplicate of this bug. *** Created attachment 68668 [details]
New crash information added by DrKonqi
kwin (4.8.00 (4.8.0) on KDE Platform 4.8.00 (4.8.0 using Qt 4.7.4
- What I was doing when the application crashed:
Login to KDE Plasma Workspace.
Simply wait...
Then KWin crashes.
However KDE can then be used normally.
-- Backtrace (Reduced):
#6 __memcpy_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1579
[...]
#8 0x00007ff43f5a778f in KWin::ARBBlurShader::init (this=0x2704170) at ../../../kwin/effects/blur/blurshader.cpp:471
#9 0x00007ff43f5a2d19 in KWin::BlurEffect::reconfigure (this=0x2704020, flags=<optimized out>) at ../../../kwin/effects/blur/blur.cpp:85
#10 0x00007ff43f5a2ff7 in KWin::BlurEffect::BlurEffect (this=0x2704020) at ../../../kwin/effects/blur/blur.cpp:53
#11 0x00007ff43f5a30f6 in KWin::effect_create_kwin4_effect_blur () at ../../../kwin/effects/blur/blur.cpp:34
"kcmshell4 kwincompositing", disable blur effect (2nd tab) and set the scale method to smooth (3rd tab) for the records pleaSe also specify your gpu and mesa/driver version - in doubt run "kwin --replace&" fro konsole and post the output *** Bug 297632 has been marked as a duplicate of this bug. *** Created attachment 70528 [details]
New crash information added by DrKonqi
kwin (4.8.2 (4.8.2)) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1
Crashes on Boot. Restart Crashes aswell
-- Backtrace (Reduced):
#6 __memcpy_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1579
[...]
#8 0x00007fdf45b23abf in KWin::ARBBlurShader::init (this=0x2a1a660) at ../../../kwin/effects/blur/blurshader.cpp:471
#9 0x00007fdf45b1f049 in KWin::BlurEffect::reconfigure (this=0x2a43e80, flags=<optimized out>) at ../../../kwin/effects/blur/blur.cpp:85
#10 0x00007fdf45b1f327 in KWin::BlurEffect::BlurEffect (this=0x2a43e80) at ../../../kwin/effects/blur/blur.cpp:53
#11 0x00007fdf45b1f426 in KWin::effect_create_kwin4_effect_blur () at ../../../kwin/effects/blur/blur.cpp:34
*** Bug 299184 has been marked as a duplicate of this bug. *** Created attachment 71003 [details]
New crash information added by DrKonqi
kwin (4.8.2 (4.8.2)) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1
- What I was doing when the application crashed:
KWin sometimes crash after reboot or wake up.
-- Backtrace (Reduced):
#6 __memcpy_ssse3_back () at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:1516
#7 0x00007fd33f0a7846 in __indirect_glProgramParameters4fvNV (target=1, index=17650916, num=1124882296, params=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:52
#8 0x00007fd32747714f in KWin::ARBBlurShader::init (this=0x10d54d0) at ../../../kwin/effects/blur/blurshader.cpp:471
#9 0x00007fd3274726d9 in KWin::BlurEffect::reconfigure (this=0x10d5380, flags=...) at ../../../kwin/effects/blur/blur.cpp:85
#10 0x00007fd3274729b7 in KWin::BlurEffect::BlurEffect (this=0x10d5380) at ../../../kwin/effects/blur/blur.cpp:53
*** Bug 301054 has been marked as a duplicate of this bug. *** Created attachment 71695 [details]
New crash information added by DrKonqi
kwin (4.8.3 (4.8.3)) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1
- What I was doing when the application crashed:
This has started happening since the past few days, every time I boot/restart my machine.
My current installation has the latest proprietary graphics driver from AMD instead of the fglrx found in the repos.
-- Backtrace (Reduced):
#6 __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:2822
[...]
#8 0x00007f4b16ec118f in KWin::ARBBlurShader::init (this=0x22b6c60) at ../../../kwin/effects/blur/blurshader.cpp:471
#9 0x00007f4b16ebc719 in KWin::BlurEffect::reconfigure (this=0x22b6b20, flags=...) at ../../../kwin/effects/blur/blur.cpp:85
#10 0x00007f4b16ebc9f7 in KWin::BlurEffect::BlurEffect (this=0x22b6b20) at ../../../kwin/effects/blur/blur.cpp:53
#11 0x00007f4b16ebcaf6 in KWin::effect_create_kwin4_effect_blur () at ../../../kwin/effects/blur/blur.cpp:34
fglrx users may: - try the radeon driver (xf86-video-ati/ati-dri) - try fglx with enforced direct rendering (late versions have been reported to be reliable) "KWIN_DIRECT_GL=1 kwin --replace &" - remain staying away from the ARB shader using code (disable blur effect and set the scale method to smooth and esp. NOT accurate) - ensure that this issue in fglrx is not caused by it's setup demands (afaik one has to run some script after un/installing it) *** Bug 302495 has been marked as a duplicate of this bug. *** *** Bug 303995 has been marked as a duplicate of this bug. *** 1) What's the platform, ASIC, OS, driver you use? And how many displays connected to the ASIC? 2) How can I reproduce this issue? Can you provide the detailed steps? As this issue occurs while enable Lanczos and Blur effects. Blur effects can be enabled in the Desktop Effects. But how can I enable Lanczos through the environment variable? 3) Does the crash definitely can be seen while reboot the system? If not, is there any way that can increase the rate of the crash? lanczos filter is enabled by setting the scale method to "accurate" (3rd tab in kwincompositing kcm) *** Bug 306972 has been marked as a duplicate of this bug. *** Git commit 965892bf9737b6d4a3f7fcadc58ecf75c8bb2cf0 by Martin Gräßlin. Committed on 09/10/2012 at 19:46. Pushed by graesslin into branch 'master'. Re-enable Blur/Lanczos for Catalyst on OpenGL 2 Given that the Catalyst driver is now supporting direct rendering and by that can use the OpenGL 2 code path we do no longer need to force disable the Blur effect and Lanczos filters which used to crash in the ARB shader path. The ARB shader path - which can only be used in OpenGL 1 - is kept disabled for Catalyst. Related: bug 286795 REVIEW: 106798 M +1 -1 kwin/effects/blur/blur.cpp M +2 -2 kwin/lanczosfilter.cpp http://commits.kde.org/kde-workspace/965892bf9737b6d4a3f7fcadc58ecf75c8bb2cf0 *** Bug 309625 has been marked as a duplicate of this bug. *** *** Bug 311930 has been marked as a duplicate of this bug. *** Created attachment 75949 [details]
New crash information added by DrKonqi
kwin (4.8.5 (4.8.5)) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1
- What I was doing when the application crashed:login
- Unusual behavior I noticed: sometime i can restart with hotkey alt-shift F12, sometimes not
- Custom settings of the application: none
-- Backtrace (Reduced):
#6 __memcpy_sse2 () at ../sysdeps/x86_64/multiarch/../memcpy.S:377
#7 0x00007f110285f856 in __indirect_glProgramParameters4fvNV (target=1, index=27019012, num=109586296, params=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:52
#8 0x00007f10e971020f in KWin::ARBBlurShader::init (this=0x19c46f0) at ../../../kwin/effects/blur/blurshader.cpp:471
#9 0x00007f10e970b799 in KWin::BlurEffect::reconfigure (this=0x19beec0, flags=...) at ../../../kwin/effects/blur/blur.cpp:85
#10 0x00007f10e970ba77 in KWin::BlurEffect::BlurEffect (this=0x19beec0) at ../../../kwin/effects/blur/blur.cpp:53
*** Bug 313923 has been marked as a duplicate of this bug. *** Created attachment 77677 [details]
New crash information added by DrKonqi
kwin (4.8.5 (4.8.5) "release 2") on KDE Platform 4.8.5 (4.8.5) "release 2" using Qt 4.8.1
- What I was doing when the application crashed:
Crashes on a fresh login. Will happen after I do a fresh reboot as well.
-- Backtrace (Reduced):
#6 0x00007f8030572d1b in memcpy (__len=<optimized out>, __src=<optimized out>, __dest=<optimized out>) at /usr/include/bits/string3.h:52
#7 __indirect_glProgramParameters4fvNV (target=881938112, index=24104944, num=1166358624, params=0x180000) at indirect.c:9317
#8 0x00007f801a4fb48e in KWin::ARBBlurShader::init (this=0x16b39e0) at /usr/src/debug/kde-workspace-4.8.5/kwin/effects/blur/blurshader.cpp:471
#9 0x00007f801a4f6b77 in KWin::BlurEffect::reconfigure (this=this@entry=0x16b6670, flags=...) at /usr/src/debug/kde-workspace-4.8.5/kwin/effects/blur/blur.cpp:85
#10 0x00007f801a4f6e07 in KWin::BlurEffect::BlurEffect (this=0x16b6670) at /usr/src/debug/kde-workspace-4.8.5/kwin/effects/blur/blur.cpp:53
First of all, this bug is not solved. This bug does not even exist, to say. It's a generic "common" bug. There are many causes, and every time we get here. I think KDE needs to implement some other triggers or some other separation, so the proper bugs will be fixed or dealt with. We still get crashes, and they have nothing to do with the original crash. Could you guys fix this? the bug is in mesa and exposed by using arb shaders on indirect contexts. the only two occasions are software rasterizers (which you rather don't want to use) and older versions of fglrx (where direct rendering was broken then as indirect rendering is in other occasions now) if you run into it, there's a good chance of a misconfigured system (running the vesa driver) what also was the case for the original bug (thus marked as downstream) The fix from kwin *could* be to block all shader invocation for indirect contexts (mostly affecting the blur effect anyway - so simply disable it to bypass the problem and for < 4.10 ensure to set the scale method to smooth) but as mentioned, the proper fix is -quite likely- to install proper and current drivers for your GPU *** Bug 319520 has been marked as a duplicate of this bug. *** *** Bug 321613 has been marked as a duplicate of this bug. *** *** Bug 321790 has been marked as a duplicate of this bug. *** |