Bug 270382 - kwin crash when desktop initialize
Summary: kwin crash when desktop initialize
Status: RESOLVED DUPLICATE of bug 254568
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-07 23:46 UTC by Néstor Echeverría
Modified: 2011-04-08 00:06 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Néstor Echeverría 2011-04-07 23:46:25 UTC
Application: kwin (4.6.00 (4.6.0) "release 6")
KDE Platform Version: 4.6.00 (4.6.0) "release 6"
Qt Version: 4.7.1
Operating System: Linux 2.6.37.1-1.2-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: Never, system just boot, and desktop init.
Sometimes not, but the vast majority does.
Are configured desktop effects. The video card is Nvidia 7300 LE.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin), signal: Aborted
[KCrash Handler]
#6  0x00007f93f87cfab5 in raise () from /lib64/libc.so.6
#7  0x00007f93f87d0fb6 in abort () from /lib64/libc.so.6
#8  0x00007f93f3968a9d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6
#9  0x00007f93f3966cb6 in ?? () from /usr/lib64/libstdc++.so.6
#10 0x00007f93f3966ce3 in std::terminate() () from /usr/lib64/libstdc++.so.6
#11 0x00007f93f3966dee in __cxa_throw () from /usr/lib64/libstdc++.so.6
#12 0x00007f93f39671fd in operator new(unsigned long) () from /usr/lib64/libstdc++.so.6
#13 0x00007f93f39672b9 in operator new[](unsigned long) () from /usr/lib64/libstdc++.so.6
#14 0x00007f93f6cd872b in KWin::GLShader::load (this=0x9b3de0, vertexsource=<value optimized out>, fragmentsource=...) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/lib/kwinglutils.cpp:767
#15 0x00007f93f6cd916b in KWin::GLShader::loadFromFiles (this=0x9b3de0, vertexfile=..., fragmentfile=...) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/lib/kwinglutils.cpp:731
#16 0x00007f93f6ce1c03 in KWin::ShaderEffect::loadData (this=0x9b3da0, shadername=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/lib/kwinshadereffect.cpp:86
#17 0x00007f93f6ce1ef2 in KWin::ShaderEffect::ShaderEffect (this=0x9b3da0, shadername=...) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/lib/kwinshadereffect.cpp:43
#18 0x00007f93deaac328 in KWin::SharpenEffect::SharpenEffect (this=0x9b3d90) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/effects/sharpen/sharpen.cpp:36
#19 0x00007f93deaac496 in KWin::effect_create_kwin4_effect_sharpen () at /usr/src/debug/kdebase-workspace-4.6.0/kwin/effects/sharpen/sharpen.cpp:32
#20 0x00007f93f8be96bf in KWin::EffectsHandlerImpl::loadEffect (this=0x8e1310, name=...) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/effects.cpp:1128
#21 0x00007f93f8bea8d1 in KWin::EffectsHandlerImpl::reconfigure (this=0x8e1310) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/effects.cpp:143
#22 0x00007f93f8bc63f6 in KWin::Workspace::setupCompositing (this=0x7af460) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/composite.cpp:216
#23 0x00007f93f8b4c6dd in KWin::Workspace::Workspace (this=0x7af460, restore=false) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/workspace.cpp:222
#24 0x00007f93f8b63f2e in KWin::Application::Application (this=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/main.cpp:330
#25 0x00007f93f8b65931 in kdemain (argc=<value optimized out>, argv=0x7fff0e495de0) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/main.cpp:516
#26 0x00007f93f87bbbfd in __libc_start_main () from /lib64/libc.so.6
#27 0x0000000000400699 in _start () at ../sysdeps/x86_64/elf/start.S:113

Possible duplicates by query: bug 265824, bug 254568.

Reported using DrKonqi
Comment 1 Thomas Lübking 2011-04-08 00:06:13 UTC
a) this bug #254568
b) as mentioned there: do not use the sharpen effect. The nvidia driver has this built in and does it with zero overhead.
c) both bugs might ultimately be the no more mysterious rethrow bug #241163

*** This bug has been marked as a duplicate of bug 254568 ***