Summary: | kwin crash while playing with "Advanced" settings | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Andrei ILIE <andrei.ilie> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andrei.ilie |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Andrei ILIE
2011-05-25 23:39:05 UTC
Created attachment 60336 [details]
New crash information added by DrKonqi
kwin (4.6.3 (4.6.3)) on KDE Platform 4.6.3 (4.6.3) using Qt 4.7.2
- What I was doing when the application crashed:
i was trying different advanced kwin settings
-- Backtrace (Reduced):
#6 0x00007f7df53fe2f6 in intelDRI2Flush (drawable=0x21c77b0) at intel_screen.c:108
#7 0x0000003217c43b9a in dri2SwapBuffers (pdraw=0x2ec2790, target_msc=0, divisor=0, remainder=0) at dri2_glx.c:529
#8 0x00007f7e0c0a2b87 in KWin::SceneOpenGL::flushBuffer (this=<value optimized out>, mask=<value optimized out>, damage=...) at /usr/src/debug/kdebase-workspace-4.6.3/kwin/scene_opengl.cpp:860
#9 0x00007f7e0c0a3395 in KWin::SceneOpenGL::paint (this=0x31202d0, damage=..., toplevels=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.6.3/kwin/scene_opengl.cpp:789
#10 0x00007f7e0c08a3d7 in KWin::Workspace::performCompositing (this=0x1e23610) at /usr/src/debug/kdebase-workspace-4.6.3/kwin/composite.cpp:448
driver bug. *** This bug has been marked as a duplicate of bug 253703 *** Sorry, but I cannot resist: why do you think the tab is labeled "Advanced"? What do you think that means? Probably not that users are supposed to "play around". It means that only users knowing what they do should change the settings! Sigh, because of such reports we had to remove the option in 4.7. Sorry, but I cannot resist: why do you think the tab is labeled "Advanced"? What do you think that means? Probably not that users are supposed to "play around". It means that only users knowing what they do should change the settings! Sigh, because of such reports we had to remove the option in 4.7. Hello Martin, This bug report is about a SEGFAULT in kwin. I played with advanced settings :) is this a crime ? I think KDE (and linux in general) should be o robust piece of software. In view of this, the worst case scenario "advanced playing" should be the display stop working for, let's say, 10 secs (the timeout for no confirmation of video changes). The user shouldn't be able to trigger a SEGFAULT, in any robust software. It's not a crime to play with a loaded gun, but don't cry if you shoot yourself ;-) Aside this and quoting comment #2 "driver bug". So just get fixed drivers/mesa for your GPU then and or export LIBGL_ALWAYS_INDIRECT=1 (what will likely workaround this issue which is likely rather *not* restricted to the Texture Generation mode but to the recreation of the GL context) > The user shouldn't be able to trigger a SEGFAULT, in any robust software. No, that's right. Now show me robust software (Saturn V control code doesn't count - it's outdated ;-) What you expect can only be achieved by systems like Apple which are - developers - distributors - HW vendors (on a very limited HW set) ie., ship you the entire system. We cannot prevent sublying libs and/or drivers from having implementation issues (OpenGL calls /are/ -supposed to be- crash safe, ie. even /iff/ kwin did bogus shit, GL should throw an GL_ERROR and maybe paint ugly stuff, but /never/ cause a segfault) fallback mode is removed in master -> fixed |