Summary: | Kwin crash after playing fullscreen embedded online flash video (youtube) | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Drew Adams <Druonysus> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | Druonysus, vivek.ap |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
Drew Adams
2010-08-07 04:42:19 UTC
Created attachment 49895 [details]
New crash information added by DrKonqi
kwin (4.4.95 (KDE 4.4.95 (KDE 4.5 >= 20100723))) on KDE Platform 4.4.95 (KDE 4.4.95 (KDE 4.5 >= 20100723)) using Qt 4.6.3
- What I was doing when the application crashed:
online flash video can't be full screened without crashing Kwin
-- Backtrace (Reduced):
#11 0xb77702db in KWin::SceneOpenGL::paintBackground (this=0x813fc60, region=...) at /usr/src/debug/kdebase-workspace-4.4.95/kwin/scene_opengl.cpp:892
#12 0xb77d7744 in KWin::Scene::paintGenericScreen (this=0x813fc60, orig_mask=40) at /usr/src/debug/kdebase-workspace-4.4.95/kwin/scene.cpp:187
#13 0xb77a4490 in KWin::Scene::finalPaintScreen (this=0x813fc60, mask=40, region=..., data=...) at /usr/src/debug/kdebase-workspace-4.4.95/kwin/scene.cpp:177
#14 0xb77dab03 in KWin::EffectsHandlerImpl::paintScreen (this=0x8466b90, mask=40, region=..., data=...) at /usr/src/debug/kdebase-workspace-4.4.95/kwin/effects.cpp:172
#15 0xafb21862 in KWin::LogoutEffect::paintScreen (this=0x87563d0, mask=40, region=..., data=...) at /usr/src/debug/kdebase-workspace-4.4.95/kwin/effects/logout/logout.cpp:207
(In reply to comment #0) > #7 0xb004b3d0 in ?? () from /usr/lib/dri/i965_dri.so > #8 0xb003ece2 in ?? () from /usr/lib/dri/i965_dri.so > #9 0xb0040fe8 in ?? () from /usr/lib/dri/i965_dri.so > #10 0xb0096216 in ?? () from /usr/lib/dri/i965_dri.so > #11 0xb77572db in KWin::SceneOpenGL::paintBackground (this=0x812e210, > region=...) at > /usr/src/debug/kdebase-workspace-4.4.95/kwin/scene_opengl.cpp:892 I'm sorry to say, but it is crashing in the OpenGL graphics driver. There is nothing we can do about it. Feel free to report the crash to the Intel developers (please install additional debugging symbols first). Created attachment 49969 [details]
New crash information added by DrKonqi
kwin (4.5.00 (KDE 4.5.0)) on KDE Platform 4.5.00 (KDE 4.5.0) using Qt 4.6.3
- What I was doing when the application crashed:
I have now upgraded to KDE 4.5 (very nice by the way) but this bug is still accuring. It is also causing my jfs /home partition to not mount until root runs fsck... this is very frustrating when this happens. I hope this gets mended soon.
-- Backtrace (Reduced):
#11 0xb77ac2db in KWin::SceneOpenGL::paintBackground (this=0x815c748, region=...) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/scene_opengl.cpp:892
#12 0xb7813744 in KWin::Scene::paintGenericScreen (this=0x815c748, orig_mask=40) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/scene.cpp:187
#13 0xb77e0490 in KWin::Scene::finalPaintScreen (this=0x815c748, mask=40, region=..., data=...) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/scene.cpp:177
#14 0xb7816b03 in KWin::EffectsHandlerImpl::paintScreen (this=0x8456160, mask=40, region=..., data=...) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/effects.cpp:172
#15 0xafb5a862 in KWin::LogoutEffect::paintScreen (this=0x8748b50, mask=40, region=..., data=...) at /usr/src/debug/kdebase-workspace-4.5.0/kwin/effects/logout/logout.cpp:207
the bug is in your driver, kwin just happens to acces an incredibly harmless OpenGL routine (mesa), that makes some driver calls (x11) and one of them is buggy (or rather the driver is buggy since it seems to mess up internal states) -> this will NOT fix by updating KDE ever! You either need a fixed driver (x11) or have to disable (opengl) compositing The mount thing is normal if you hard reset your system and prevents you from severe data loss, this is certainly not related to this issue. *** Bug 253713 has been marked as a duplicate of this bug. *** I have this problem as well, with same driver (intel). It should be reported upstream or is it alrady? dupe has a better backtrace *** This bug has been marked as a duplicate of bug 252817 *** |