| Summary: | KWin crashes after resuming | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | René Serral <rserral> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | kapamaroo |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | Backtrace | ||
|
Description
René Serral
2011-08-25 12:48:17 UTC
most likely related to 280766 and in glDrawArrays (what should iirc however not crash but produce GL errors) can you please install the mesa-dev packages and post a complete bug. As workaround, suspend compositing before STR or hibernating. Created attachment 63209 [details]
Backtrace
I just uploaded a backtrace with DBG symbols on mesa. I hope it helps Thread 1 (Thread 0xb1f3d720 (LWP 29184)): [KCrash Handler] #7 intel_region_buffer (intel=0x9c58c98, region=0x0, flag=2) at intel_regions.c:514 #8 0xb007ea5d in intelClearWithBlit (ctx=0x9c58c98, mask=2) at intel_blit.c:262 #9 0xb008127d in intelClear (ctx=0x9c58c98, mask=2) at intel_clear.c:177 #10 0xb0284fc0 in _mesa_Clear (mask=<optimized out>) at main/clear.c:241 #11 0xb7728e98 in KWin::SceneOpenGL::paintBackground (this=0x9bee6d0, region=...) at /media/kdesvn/kde4svn/src/kde-workspace/kwin/scene_opengl.cpp:182 #12 0xb7712985 in KWin::Scene::paintGenericScreen (this=0x9bee6d0, orig_mask=520) at /media/kdesvn/kde4svn/src/kde-workspace/kwin/scene.cpp:185 #13 0xb77231b4 in KWin::SceneOpenGL::paintGenericScreen (this=0x9bee6d0, mask=520, data=...) at /media/kdesvn/kde4svn/src/kde-workspace/kwin/scene_opengl.cpp:169 #14 0xb770f2f0 in KWin::Scene::finalPaintScreen (this=0x9bee6d0, mask=520, region=..., data=...) at /media/kdesvn/kde4svn/src/kde-workspace/kwin/scene.cpp:175 ... That's a different trace and it's bug #252817 -> Did you obtain the new trace the very same way as the other one (resume from STR)? It's hoever unlikely that bug #280766 (this one) a dupe of bug #252817 but rather intel exposes both issues because the backtrace here looks very much like bug #279246 and nvidia does (so far) not cause #252817 at all Well, I didn't realize that the backtrace was different, it happened to me resuming from disk, after the resume I typed my password on the screensaver and I got this crash I thought it was related to the other one. Just in case it is not clear from the backtrace I have an Intel GM965. Thanks for the efforts in solving the issue. Best. (In reply to comment #5) > I got this crash I thought it was related to the other one. No. The latter backtrace is the most hated bug around here (unfortunately in the intel driver...) which can circumvented by NOT unredirecting fullscreen windows (kcmshell4 kwincompositing, 3rd tab, UNcheck "suspend compositing for fullscreen windows") The other backtrace is a crash in a GL call as well, but an entirely different one and likely for different reasons. -> Does STR resume work for you with the change mentioned above? (could indeed be the same very deep source in the driver then) I've been trying the suspension with your suggestion and I can say that I didn't experience the crash anymore. Thanks! René more (2nd) or less (1st) a dupe of "intel cannot handle unredirection" *** This bug has been marked as a duplicate of bug 252817 *** *** Bug 301315 has been marked as a duplicate of this bug. *** |