| Summary: | Kwin crashes after logging after kdm crash | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Dmitriy A. Perlow <dap.darkness> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | dap.darkness |
| Priority: | NOR | Flags: | mgraesslin:
NVIDIA+
|
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Dmitriy A. Perlow
2012-04-12 12:54:11 UTC
Created attachment 70339 [details]
New crash information added by DrKonqi
kwin (4.8.2 (4.8.2) "release 491") on KDE Platform 4.8.2 (4.8.2) "release 491" using Qt 4.8.1
Just logging in after kdm crash... The second crash of kwin.
-- Backtrace (Reduced):
#11 0x00007f5f37c836d4 in KWin::GLShader::setUniform (this=<optimized out>, location=5, value=<optimized out>) at /usr/src/debug/kde-workspace-4.8.2/kwin/libkwineffects/kwinglutils.cpp:516
#12 0x00007f5f3bb60d95 in KWin::SceneOpenGL::Window::restoreShaderRenderStates (this=<optimized out>, type=KWin::SceneOpenGL::Window::Content, opacity=<optimized out>, brightness=<optimized out>, saturation=<optimized out>, shader=<optimized out>) at /usr/src/debug/kde-workspace-4.8.2/kwin/scene_opengl.cpp:1044
#13 0x00007f5f3bb67660 in KWin::SceneOpenGL::Window::performPaint (this=0xf51e30, mask=9, region=..., data=...) at /usr/src/debug/kde-workspace-4.8.2/kwin/scene_opengl.cpp:593
#14 0x00007f5f3bb4fd89 in KWin::Scene::finalDrawWindow (this=<optimized out>, w=<optimized out>, mask=9, region=<optimized out>, data=<optimized out>) at /usr/src/debug/kde-workspace-4.8.2/kwin/scene.cpp:438
#15 0x00007f5f3bb72715 in KWin::EffectsHandlerImpl::drawWindow (this=0xb16490, w=0xf49aa0, mask=9, region=<optimized out>, data=...) at /usr/src/debug/kde-workspace-4.8.2/kwin/effects.cpp:286
does the 64bit variant of the nvidia blob really still come with glcore? to workaround, pot. disable the translucency effect or OpenGL2 shaders. -> what GPU/chip is that? *** This bug has been marked as a duplicate of bug 284332 *** GTS 250. No sense in using effects without translucency. It happens once in two days. But I found and disabled OpenGL2 shaders. Thanks! |