Application: kwin (4.4.2 (KDE 4.4.2)) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-23-generic x86_64 Distribution: Ubuntu 10.04 LTS -- Information about the crash: Hello, I running kubuntu lucid 10.04 LTS on x86 64 , and after have launched a game (call of duty 4 ) , kwin crashed and crated a bug report. i never experimented such bug early. wine: wine-1.2-rc4 Linux xxxxxxxxxxxxxxx 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux -- Backtrace: Application: KWin (kwin), signal: Aborted [Current thread is 1 (Thread 0x7f50e73e67a0 (LWP 2343))] Thread 2 (Thread 0x7f50c70dc710 (LWP 2344)): #0 0x00007f50e6d6ff83 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007f50dbb8c4a9 in ?? () from /lib/libglib-2.0.so.0 #2 0x00007f50dbb8c8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x00007f50e2ca2566 in QEventDispatcherGlib::processEvents (this=0x1d1c870, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414 #4 0x00007f50e2c77992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #5 0x00007f50e2c77d6c in QEventLoop::exec (this=0x7f50c70dbd70, flags=) at kernel/qeventloop.cpp:201 #6 0x00007f50e2b81d59 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:487 #7 0x00007f50e2c58178 in QInotifyFileSystemWatcherEngine::run (this=0x20af950) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x00007f50e2b84775 in QThreadPrivate::start (arg=0x20af950) at thread/qthread_unix.cpp:248 #9 0x00007f50e28f49ca in start_thread (arg=<value optimized out>) at pthread_create.c:300 #10 0x00007f50e6d7c6fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f50e73e67a0 (LWP 2343)): [KCrash Handler] #5 0x00007f50e6cc9a75 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #6 0x00007f50e6ccd5c0 in *__GI_abort () at abort.c:92 #7 0x00007f50e6d034fb in __libc_message (do_abort=<value optimized out>, fmt=<value optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189 #8 0x00007f50e6d0d5b6 in malloc_printerr (action=3, str=0x7f50e6ddd922 "corrupted double-linked list", ptr=<value optimized out>) at malloc.c:6264 #9 0x00007f50e6d12394 in _int_malloc (av=0x7f50e7014e40, bytes=128) at malloc.c:4633 #10 0x00007f50e6d1258e in *__GI___libc_malloc (bytes=128) at malloc.c:3660 #11 0x00007f50e2bc9559 in QString::realloc (this=0x7fff88f53050, alloc=0) at tools/qstring.cpp:1219 #12 0x00007f50e2bc9c75 in QString::resize (this=0x7fff88f53050, size=36) at tools/qstring.cpp:1155 #13 0x00007f50e2bd3590 in operator>> (in=..., str=...) at tools/qstring.cpp:7300 #14 0x00007f50e3fd1bfb in QDataStream& operator>><QString, QVariant>(QDataStream&, QMap<QString, QVariant>&) () from /usr/lib/libkdecore.so.5 #15 0x00007f50e3fe37f2 in KServicePrivate::load (this=0x94a8f00, s=<value optimized out>) at ../../kdecore/services/kservice.cpp:338 #16 0x00007f50e3fe3b96 in KServicePrivate (this=0x30e2d70, _str=..., _offset=1190178) at ../../kdecore/services/kservice_p.h:41 #17 KService (this=0x30e2d70, _str=..., _offset=1190178) at ../../kdecore/services/kservice.cpp:404 #18 0x00007f50e3febf0a in KServiceFactory::createEntry (this=<value optimized out>, offset=1190178) at ../../kdecore/services/kservicefactory.cpp:196 #19 0x00007f50e3feabeb in KServiceFactory::serviceOffers (this=0x3f2d1d0, serviceTypeOffset=21153, serviceOffersOffset=<value optimized out>) at ../../kdecore/services/kservicefactory.cpp:283 #20 0x00007f50e3ffa970 in KServiceTypeTrader::defaultOffers (this=<value optimized out>, serviceType=<value optimized out>, constraint=...) at ../../kdecore/services/kservicetypetrader.cpp:125 #21 0x00007f50e3ffadb1 in KServiceTypeTrader::query (this=0x1b88710, serviceType=..., constraint=...) at ../../kdecore/services/kservicetypetrader.cpp:141 #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 #26 0x00007f50e2c8be3f in QMetaObject::activate (sender=0x2b3bf40, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0xffffffffffffffff) at kernel/qobject.cpp:3293 #27 0x00007f50e2c9365f in QSingleShotTimer::timerEvent (this=0x2b3bf40) at kernel/qtimer.cpp:308 #28 0x00007f50e2c88a63 in QObject::event (this=0x2b3bf40, e=0x7fff88f544c0) at kernel/qobject.cpp:1212 #29 0x00007f50e33c522c in QApplicationPrivate::notify_helper (this=0x18fb3a0, receiver=0x2b3bf40, e=0x7fff88f544c0) at kernel/qapplication.cpp:4300 #30 0x00007f50e33cb6fb in QApplication::notify (this=0x7fff88f54820, receiver=0x2b3bf40, e=0x7fff88f544c0) at kernel/qapplication.cpp:4183 #31 0x00007f50e6880526 in KApplication::notify (this=0x7fff88f54820, receiver=0x2b3bf40, event=0x7fff88f544c0) at ../../kdeui/kernel/kapplication.cpp:302 #32 0x00007f50e2c7906c in QCoreApplication::notifyInternal (this=0x7fff88f54820, receiver=0x2b3bf40, event=0x7fff88f544c0) at kernel/qcoreapplication.cpp:704 #33 0x00007f50e2ca5d42 in QCoreApplication::sendEvent (this=0x18ff110) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #34 QTimerInfoList::activateTimers (this=0x18ff110) at kernel/qeventdispatcher_unix.cpp:603 #35 0x00007f50e2ca2848 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184 #36 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231 #37 0x00007f50dbb888c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #38 0x00007f50dbb8c748 in ?? () from /lib/libglib-2.0.so.0 #39 0x00007f50dbb8c8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #40 0x00007f50e2ca2513 in QEventDispatcherGlib::processEvents (this=0x18e1c40, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412 #41 0x00007f50e347546e in QGuiEventDispatcherGlib::processEvents (this=0x927, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #42 0x00007f50e2c77992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #43 0x00007f50e2c77d6c in QEventLoop::exec (this=0x7fff88f54760, flags=) at kernel/qeventloop.cpp:201 #44 0x00007f50e2c7baab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #45 0x00007f50e70687be in kdemain () from /usr/lib/libkdeinit4_kwin.so #46 0x00007f50e6cb4c4d in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff88f54d28) at libc-start.c:226 #47 0x00000000004006b9 in _start () Possible duplicates by query: bug 236519, bug 232041, bug 216620, bug 212154, bug 208881. Reported using DrKonqi
#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!