I checked the problem and was able to reproduce it with any game I run. I think it must have something to do related with graphics. 

The games are mostly running under openGL. Immediately after the game stops and the Game Window closes and you see your Desktop the message pops up.

Please look into this.

Does it crash when you go into window mode? Does it crash when you start the game or when you exit (Alt-tab while playing to see if it's the former)?

OpenGL is the reason as KWin and the game are trying to use the same device memory.

I start up the game in fullscreen mode. I play without problems or glitches. I stop the game and quit it. When the game window terminates from fullscreen and the desktop just refreshes and becomes visible the crash happens.

Best regards,

Chris

I think my bug could also be related at least roughly to this bug:
http://bugs.kde.org/show_bug.cgi?id=167690

Thank you for looking into this.

The backtrace is useless, please install debuginfo packages and try again (http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports).

I red the link and I installed kdelibs-dbg. During this I found out that I could not find kwin-dbg. I also found out that I have kwin installed, not kwin-kde4. But I cannot install kwin-kde4 due to some dependencies not met:

kwin-kde4: depends on: libkdecorations4 soll aber nicht installiert werden
             depends on libkwineffects1 (>= 4:4.0.80) soll aber nicht installiert werden

------------
So I only installed kdelibs-dbg and here is the new report:




Anwendung: KWin (kwin), Signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6544940 (LWP 12671)]
[KCrash handler]
#6  0xb7f6f410 in __kernel_vsyscall ()
#7  0xb7d8f085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb7d90a01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb7d8810e in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#10 0xb7f515b4 in ?? () from /usr/lib/kde4/lib/libkdeinit4_kwin.so
#11 0xb7f4263d in ?? () from /usr/lib/kde4/lib/libkdeinit4_kwin.so
#12 0xb7ee3039 in ?? () from /usr/lib/kde4/lib/libkdeinit4_kwin.so
#13 0xb7a7a4f9 in QMetaObject::activate (sender=0x80f8dfc, 
    from_signal_index=4, to_signal_index=4, argv=0x0)
    at kernel/qobject.cpp:3010
#14 0xb7a7abc2 in QMetaObject::activate (sender=0x80f8dfc, m=0xb7b5b004, 
    local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3080
#15 0xb7ab7e07 in QTimer::timeout (this=0x80f8dfc)
    at .moc/release-shared/moc_qtimer.cpp:126
#16 0xb7a8167e in QTimer::timerEvent (this=0x80f8dfc, e=0xbf961ec8)
    at kernel/qtimer.cpp:263
#17 0xb7a75c9a in QObject::event (this=0x80f8dfc, e=0xbf961ec8)
    at kernel/qobject.cpp:1105
#18 0xb701fc0c in QApplicationPrivate::notify_helper (this=0x8059450, 
    receiver=0x80f8dfc, e=0xbf961ec8) at kernel/qapplication.cpp:3772
#19 0xb7024799 in QApplication::notify (this=0xbf9621a4, receiver=0x80f8dfc, 
    e=0xbf961ec8) at kernel/qapplication.cpp:3366
#20 0xb6c8def3 in KApplication::notify (this=0xbf9621a4, receiver=0x80f8dfc, 
    event=0xbf961ec8)
    at /build/buildd/kde4libs-4.1.0/kdeui/kernel/kapplication.cpp:311
#21 0xb7efdbba in ?? () from /usr/lib/kde4/lib/libkdeinit4_kwin.so
#22 0xb7a656a9 in QCoreApplication::notifyInternal (this=0xbf9621a4, 
    receiver=0x80f8dfc, event=0xbf961ec8) at kernel/qcoreapplication.cpp:587
#23 0xb7a931a1 in QTimerInfoList::activateTimers (this=0x805c244)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#24 0xb7a90a40 in timerSourceDispatch (source=0x805c210)
    at kernel/qeventdispatcher_glib.cpp:166
#25 0xb6822bf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0xb6825e5e in ?? () from /usr/lib/libglib-2.0.so.0
#27 0xb68263ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#28 0xb7a90f98 in QEventDispatcherGlib::processEvents (this=0x80570b8, 
    flags=@0xbf962028) at kernel/qeventdispatcher_glib.cpp:325
#29 0xb70b3195 in QGuiEventDispatcherGlib::processEvents (this=0x80570b8, 
    flags=@0xbf962058) at kernel/qguieventdispatcher_glib.cpp:204
#30 0xb7a6492d in QEventLoop::processEvents (this=0xbf9620d0, 
    flags=@0xbf962094) at kernel/qeventloop.cpp:149
#31 0xb7a64abd in QEventLoop::exec (this=0xbf9620d0, flags=@0xbf9620d8)
    at kernel/qeventloop.cpp:200
#32 0xb7a66d3d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#33 0xb701f567 in QApplication::exec () at kernel/qapplication.cpp:3304
#34 0xb7eff0df in kdemain () from /usr/lib/kde4/lib/libkdeinit4_kwin.so
#35 0x08048582 in _start ()
#0  0xb7f6f410 in __kernel_vsyscall ()


if this information is not good enough or complete enough again, please tell me exactly how to proceed and what dbg-packages to install to help you find the problem.

Best regards,

Chris

forget what I said about kwin and kwin-kde4... I am sure I have the right kwin installed, only was installed and upgraded automatically and that is why adept package manager told me that it is not installed.

By the way:

I tried to attach 'gdb' to my kwin process. It does not work. Cannot let kwin run through gdb, that is why I could not get debug info for it. 
I ran the game through gdb, but the message says of course: Game quit normally. no BAcktrace, no stack.

When I am in the game and I press ALT+TAB to change to another window no any crash.

So I cannot give you debug info with gdb and I cannot find the right dbg-package for kwin to get debug info though KDE crash manager.

What to do?

since 4.1 KWin is in package kde-window-manager in Ubuntu

The debug package should be kdebase-workspace-dbg

Thank you very much ... that helped a lot:

The new report and valid report is as follows:

Anwendung: KWin (kwin), Signal SIGABRT
[Thread debugging using libthread_db enabled]
[New Thread 0xb6556940 (LWP 14147)]
[KCrash handler]
#6  0xb7f81410 in __kernel_vsyscall ()
#7  0xb7da1085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb7da2a01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb7d9a10e in __assert_fail () from /lib/tls/i686/cmov/libc.so.6
#10 0xb7f635b4 in KWin::SceneOpenGL::paint (this=0x83f0650, 
    damage=@0xbfbfeb3c, toplevels=@0xbfbfeb38)
    at /build/buildd/kdebase-workspace-4.1.0/kwin/scene_opengl.cpp:612
#11 0xb7f5463d in KWin::Workspace::performCompositing (this=0x80ec400)
    at /build/buildd/kdebase-workspace-4.1.0/kwin/composite.cpp:351
#12 0xb7ef5039 in KWin::Workspace::qt_metacall (this=0x80ec400, 
    _c=QMetaObject::InvokeMetaMethod, _id=137, _a=0xbfbfec18)
    at /build/buildd/kdebase-workspace-4.1.0/obj-i486-linux-gnu/kwin/workspace.moc:433
#13 0xb7a8c4f9 in QMetaObject::activate (sender=0x80ec64c, 
    from_signal_index=4, to_signal_index=4, argv=0x0)
    at kernel/qobject.cpp:3010
#14 0xb7a8cbc2 in QMetaObject::activate (sender=0x80ec64c, m=0xb7b6d004, 
    local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3080
#15 0xb7ac9e07 in QTimer::timeout (this=0x80ec64c)
    at .moc/release-shared/moc_qtimer.cpp:126
#16 0xb7a9367e in QTimer::timerEvent (this=0x80ec64c, e=0xbfbff118)
    at kernel/qtimer.cpp:263
#17 0xb7a87c9a in QObject::event (this=0x80ec64c, e=0xbfbff118)
    at kernel/qobject.cpp:1105
#18 0xb7031c0c in QApplicationPrivate::notify_helper (this=0x8059258, 
    receiver=0x80ec64c, e=0xbfbff118) at kernel/qapplication.cpp:3772
#19 0xb7036799 in QApplication::notify (this=0xbfbff3f4, receiver=0x80ec64c, 
    e=0xbfbff118) at kernel/qapplication.cpp:3366
#20 0xb6c9fef3 in KApplication::notify (this=0xbfbff3f4, receiver=0x80ec64c, 
    event=0xbfbff118)
    at /build/buildd/kde4libs-4.1.0/kdeui/kernel/kapplication.cpp:311
#21 0xb7f0fbba in KWin::Application::notify (this=0xbfbff3f4, o=0x80ec64c, 
    e=0xbfbff118) at /build/buildd/kdebase-workspace-4.1.0/kwin/main.cpp:369
#22 0xb7a776a9 in QCoreApplication::notifyInternal (this=0xbfbff3f4, 
    receiver=0x80ec64c, event=0xbfbff118) at kernel/qcoreapplication.cpp:587
#23 0xb7aa51a1 in QTimerInfoList::activateTimers (this=0x805c394)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#24 0xb7aa2a40 in timerSourceDispatch (source=0x805c360)
    at kernel/qeventdispatcher_glib.cpp:166
#25 0xb6834bf8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0xb6837e5e in ?? () from /usr/lib/libglib-2.0.so.0
#27 0xb68383ac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#28 0xb7aa2f98 in QEventDispatcherGlib::processEvents (this=0x80570b8, 
    flags=@0xbfbff278) at kernel/qeventdispatcher_glib.cpp:325
#29 0xb70c5195 in QGuiEventDispatcherGlib::processEvents (this=0x80570b8, 
    flags=@0xbfbff2a8) at kernel/qguieventdispatcher_glib.cpp:204
#30 0xb7a7692d in QEventLoop::processEvents (this=0xbfbff320, 
    flags=@0xbfbff2e4) at kernel/qeventloop.cpp:149
#31 0xb7a76abd in QEventLoop::exec (this=0xbfbff320, flags=@0xbfbff328)
    at kernel/qeventloop.cpp:200
#32 0xb7a78d3d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#33 0xb7031567 in QApplication::exec () at kernel/qapplication.cpp:3304
#34 0xb7f110df in kdemain (argc=3, argv=0xbfbff5c4)
    at /build/buildd/kdebase-workspace-4.1.0/kwin/main.cpp:511
#35 0x08048582 in main (argc=)
    at /build/buildd/kdebase-workspace-4.1.0/obj-i486-linux-gnu/kwin/kwin_dummy.cpp:3
#0  0xb7f81410 in __kernel_vsyscall ()

Does it still crash even when all desktop plugins are disabled? (Disable from the plugin list, not the single checkbox on the first tab)

sorry ... I checked for more than half an hour now... I cannot find where to disable all desktop plugins.

I have nothing on the desktop now. No folder view, no anything, but where to disable the plasmoids alltogether I could not find.

Kwin still crashing with

Sorry for the confusion--I'm referring to KWin desktop effect plugins, not Plasmoids. You can find the effects in System Settings -> Desktop -> Desktop effects -> All effects.

ok .. now I understood ,, sorry ,,

yes I disabled as you said and now the problem is gone ...

Please enable the effects one at a time until the problem reappears (This may take a while, maybe try blur first as it is known to cause lots of problems).

Dear Lucas,

thanks to your instructions I could find the responsible desktop effect, which causes the crash for me:

Fading effect
Author: Rivo Laks rivolaks@hot.ee
Version 0.2.0

I have a German system, so the above is only translated by me.

It shows in German as:
Verwischen
Version 0.2.0
Unter KDE 4.1.00 (KDE 4.1.0)
Author: Rivo Laks
rivolaks@hot.ee
Translation: Thomas Reitelbach
tr@erdfunkstelle.de

All the other effects are not causing this crash.

Best regards,

Chris

*** This bug has been marked as a duplicate of 152914 ***

ok .. so it is a duplicate ... but I have a intel graphics card for the record.

The bug 152914 is fixed? But I read the comments there and cannot find a fix... or I cannot find a fix which I can understand...

The effect, which is causing the problem, is the blur effect (verwischen=blur). So Lubos I'm not sure if this bug is then really a duplicate of #152914.

Comment #14 says fade. And comment #8 points to being a duplicate too.

well comment #14 says it is translated from German to English. And the mentioned German name (verwischen) is the blur effect. I'm using the German translation and so I am totally sure ;-)

But with comment #8 you are probably right.

sorry .. my mistake .. wrong copy and paste

It is the FADE effect.

It is 

Verblassen 
 Version 0.2.0 
 Unter KDE 4.1.00 (KDE 4.1.0) 
 Author: Rivo Laks 
 rivolaks at hot.ee 
 Translation: Thomas Reitelbach 
 tr at erdfunkstelle.de 

*** Bug 168121 has been marked as a duplicate of this bug. ***

I have testet it with no Effekt called verwischen and verblassen in German, it looks lika everthing is all right.

well, for me not ...

as soon I use "Verblassen" or "Fade" effect I get the crash.

Today i have update Kubuntu, after that shutdown maschine and plasma crashed, I use "Verblassen" / "Fade"

thank you for the confirmation

the bug is labeled wrong ... it should be

Bug 167798: Fade effect causes KWin to crash after closing fullscreen games

My problems are caused by the Fade effect.