Summary: | kwin crashed after started a game (call of Duty 4 ) | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | stars |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | Keywords: | investigated, triaged |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
stars
2010-06-21 19:19:40 UTC
#22 0x00007f50e70e2c08 in ?? () from /usr/lib/libkdeinit4_kwin.so #23 0x00007f50e70e3f79 in ?? () from /usr/lib/libkdeinit4_kwin.so #24 0x00007f50e70c5abc in ?? () from /usr/lib/libkdeinit4_kwin.so #25 0x00007f50e704c494 in ?? () from /usr/lib/libkdeinit4_kwin.so the backtrace is unfortunately useless. If you are able to reproduce the crash please install package kdebase-workspace-dbg and attach a new backtrace. hello Martin, Thanks for your advice, i have installed the dbg package you told me and i see that in fact that's with OpenGl that Kwin crashed, if i use directX instead, it doesn't crash. It will interesting to get a useful backtrace because it was recommenaded to use OpenGl for this game .. i give backtrace soon as i can get it did you suspend compositing before running the game? Hi Thomas, No, since KDE 4.4, i don't need anymore to suspend compositing like old KDE. I have tested again with OpenGl and i was able to play without any crash this time. The only difference between the first time i tested are that the recommended configuration said that i need use: string: OffscreenRenderingMode value: fbo <------- i don't know what do fbo but this time the game start without graphic . If i use "backbuffer" it run very well and better than directX . Their another option for the same string and that's " pbuffer" but i never tested and don't know what it does.. So it's complicate while their no infos about what does that 3 options.. Fbo was the one who have caused the crash with OpenGl but when i was gaming ... Now it just don't give anymore graphic if i use fbo. For info, when i exit the game , i get my desktop on the right resolution and compositing still working like it does. I use Monitor pc HDMI for info . I hope that will help you (In reply to comment #4) > No, since KDE 4.4, i don't need anymore to suspend compositing like old KDE. it segfaulted on OpenGL interference, yesno? > string: OffscreenRenderingMode value: fbo <------- i don't know what do > fbo but this time the game start without graphic . "FrameBuffer Object" this is probably a (fixed) mesa bug (in case you've support for them at all, check "glxinfo | grep framebuffer") > If i use "backbuffer" it run very well and better than directX . what'S been the default then? pbuffers?? > Their another option for the same string and that's " pbuffer" but i never > tested and don't know what it does.. http://www.opengl.org/registry/specs/ARB/wgl_pbuffer.txt > I hope that will help you stupid question: does it now (after an mesa/x11 update?) work for you? > it segfaulted on OpenGL interference, yesno? no, so far i don't experienced anymore segfault or fatal system crash but as a possible OpenGL interference , when i quit most of games, the desktop use a very low resolution but still working with compositing, i just need change to 1920x1200 and it come right again without any problems. > "FrameBuffer Object" this is probably a (fixed) mesa bug (in case you've support for them at all, check "glxinfo | grep framebuffer") i am confuse about wineHQ wiki, about the defaut config and there said that fbo are the default "string: OffscreenRenderingMode" and for this game in exemple it must set like that. On my system it was set on Backbuffer by default, who are the only one running on the most recent wine version . glxinfo | grep framebuffer GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB, GLX_ARB_fbconfig_float, GLX_EXT_framebuffer_sRGB, GL_ARB_fragment_shader, GL_ARB_framebuffer_object, GL_ARB_framebuffer_sRGB, GL_ARB_geometry_shader4, GL_ARB_half_float_pixel, GL_EXT_fog_coord, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, GL_EXTX_framebuffer_mixed_formats, GL_EXT_framebuffer_object, GL_EXT_framebuffer_sRGB, GL_EXT_geometry_shader4, GL_NV_fragment_program2, GL_NV_framebuffer_multisample_coverage, After your explain, i think that the recommended configuration are outdated and seem not correct. i will try again with "fbo" and a older wine version and so i hope that it will crash again to give you the backtrace. what'S been the default then? pbuffers?? > on my Kubuntu Lucid and Playonlinux, most recent wineHQ, it's BAckbuffer by fefaut and who work perefctly , after i have pbuffer and fbo to choose if i want. > Their another option for the same string and that's " pbuffer" but i never > tested and don't know what it does.. > Thanks to pint me too, seem like a very old option and that's why it was not in the FAQ and Wiki in WineHQ and Playonlinux stupid question: does it now (after an mesa/x11 update?) work for you? > sorry, i am quite new on linux and try to do my best, sure i understand what you mean ;) i don't really understand about "after a update mesa/x11", i don't see new update for it , i keep my system most updated as possible excepted backport . Thanks for all your time and answers Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |