Bug 274825

Summary:	KWin crashes after enabling desktop effects
Product:	[Plasma] kwin	Reporter:	León van de Pavert <leon2011>
Component:	general	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	crash
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description León van de Pavert 2011-06-03 11:46:40 UTC

Application: kwin (4.6.2 (4.6.2))
KDE Platform Version: 4.6.2 (4.6.2)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-8-generic i686
Distribution: Ubuntu 11.04

-- Information about the crash:
- What I was doing when the application crashed: After a clean start the desktop effects were not on. I selected System Settings > Configure desktop effects > Enable desktop effects then it crashed. This happens every time desktop effects are enabled.

- Custom settings of the application: Intel GMA945M on a Fujiteu Siemens laptop with built in monitor (1280x800) and external monitor (1920x1080)

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
[KCrash Handler]
#7  _mesa_generate_mipmap (ctx=0x85bab18, target=3553, texObj=0x894a998) at main/mipmap.c:1693
#8  0x0386b0cd in intelGenerateMipmap (ctx=0x85bab18, target=3553, texObj=0x894a998) at intel_tex.c:82
#9  0x03576b6d in _mesa_GenerateMipmapEXT (target=3553) at main/fbobject.c:2184
#10 0x00375a76 in KWin::GLTexture::enableFilter (this=0x894f020) at ../../../kwin/lib/kwinglutils.cpp:589
#11 0x00375abf in KWin::GLTexture::bind (this=0x894f020) at ../../../kwin/lib/kwinglutils.cpp:426
#12 0x003758f8 in KWin::GLTexture::setWrapMode (this=0x894f020, mode=10496) at ../../../kwin/lib/kwinglutils.cpp:565
#13 0x00380903 in KWin::ShaderEffect::loadData (this=0x8933bf8, shadername=...) at ../../../kwin/lib/kwinshadereffect.cpp:73
#14 0x003810e6 in KWin::ShaderEffect::ShaderEffect (this=0x8933bf8, shadername=...) at ../../../kwin/lib/kwinshadereffect.cpp:43
#15 0x03c09fd2 in KWin::SharpenEffect::SharpenEffect (this=0x8933bf0) at ../../../kwin/effects/sharpen/sharpen.cpp:36
#16 0x03c0a19d in KWin::effect_create_kwin4_effect_sharpen () at ../../../kwin/effects/sharpen/sharpen.cpp:32
#17 0x005c2229 in KWin::EffectsHandlerImpl::loadEffect (this=0x88d0640, name=...) at ../../kwin/effects.cpp:1128
#18 0x005c34ef in KWin::EffectsHandlerImpl::reconfigure (this=0x88d0640) at ../../kwin/effects.cpp:143
#19 0x0059a525 in KWin::Workspace::setupCompositing (this=0x85f26f0) at ../../kwin/composite.cpp:216
#20 0x005119f6 in KWin::Workspace::Workspace (this=0x85f26f0, restore=false) at ../../kwin/workspace.cpp:222
#21 0x0052b410 in KWin::Application::Application (this=0xbfade5c4) at ../../kwin/main.cpp:330
#22 0x0052d1b7 in kdemain (argc=3, argv=0xbfade844) at ../../kwin/main.cpp:516
#23 0x080485bb in main (argc=3, argv=0xbfade844) at kwin_dummy.cpp:3

Reported using DrKonqi

Comment 1 Thomas Lübking 2011-06-03 12:50:34 UTC

Driver bug.
Disable the "sharpen" effect, don't use the "looking glas" effect.
(They're gonna be dropped because of such incidents anyway)

@Martin:
Any idea what could be so hard about mipmap implementation in GL drivers?
Is there maybe actually a "bug" in kwin's mipmap using like mTarget is accidentally "0" (or any kind of other shit) on some setups? (shouldn't crash, but not produce usable results either)

Comment 2 Martin Flöser 2011-06-03 22:51:58 UTC

 > @Martin:
> Any idea what could be so hard about mipmap implementation in GL drivers?
> Is there maybe actually a "bug" in kwin's mipmap using like mTarget is
> accidentally "0" (or any kind of other shit) on some setups? (shouldn't
> crash, but not produce usable results either)
it's possible, but to find out we need such a crash situation to add gdb to it.

Comment 3 Thomas Lübking 2011-06-08 17:34:27 UTC

errr... for the records: "no"
#9  0x03576b6d in _mesa_GenerateMipmapEXT (target=3553) at main/fbobject.c:2184

google says "3553 == GL_TEXTURE_2D", so we're pretty much off the hook.