Bug 327067 - kwineffect disablen?
Summary: kwineffect disablen?
Status: RESOLVED DUPLICATE of bug 320562
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-11-03 05:31 UTC by ijont
Modified: 2013-11-03 06:40 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ijont 2013-11-03 05:31:42 UTC
Application: kwin (4.10.5 "release 1")
KDE Platform Version: 4.10.5 "release 1"
Qt Version: 4.8.4
Operating System: Linux 3.7.10-1.16-desktop x86_64
Distribution: "openSUSE 12.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

it starts to begin annoying... same crash afer/while playing an opengl-game, same crash-context (kwineffects.cpp) . may be, disable kde-effects at all?
when sending error report, does kwin starts then new after report?

- Unusual behavior I noticed:
ok, not really unusual, but was surprising that meta+s stops the activities ! thought, i lost my desktop! .... will change this shortcut, because in "mc" alt+s is searching and alt key direct near meta key. should be a WARNING ala "do you really want to stop the activity? imho... although this sounds a bit like windows ;)

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0aad2ff7c0 (LWP 2338))]

Thread 2 (Thread 0x7f0a8affd700 (LWP 2348)):
#0  0x00007f0aa7ab4964 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f0aa9403307 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f0aa9710660 <QTWTF::pageheap_memory>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x00007f0aa9403339 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x00007f0aa7ab0e0f in start_thread () from /lib64/libpthread.so.0
#4  0x00007f0aacb2844d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f0aad2ff7c0 (LWP 2338)):
[KCrash Handler]
#6  0x00007f0aa7e4ce2a in QMetaObject::invokeMethod (obj=0x2980850, member=<optimized out>, type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1166
#7  0x00007f0aab2f5a70 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=0x7f0aab304002 "addLayerRepaint", obj=<optimized out>) at /usr/include/QtCore/qobjectdefs.h:434
#8  KWin::EffectWindow::addLayerRepaint (this=<optimized out>, r=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/libkwineffects/kwineffects.cpp:793
#9  0x00007f0aab30188d in KWin::AnimationEffect::postPaintScreen (this=<optimized out>) at /usr/src/debug/kde-workspace-4.10.5/kwin/libkwineffects/kwinanimationeffect.cpp:543
#10 0x00007f0aacec6cf8 in KWin::EffectsHandlerImpl::postPaintScreen (this=0x28fe410) at /usr/src/debug/kde-workspace-4.10.5/kwin/effects.cpp:260
#11 0x00007f0aacea7095 in KWin::Scene::paintScreen (this=0x27c4050, mask=<optimized out>, region=0x7fffd8191d10) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene.cpp:144
#12 0x00007f0aacead6dc in KWin::SceneXrender::paint (this=0x27c4050, damage=..., toplevels=...) at /usr/src/debug/kde-workspace-4.10.5/kwin/scene_xrender.cpp:187
#13 0x00007f0aacea136c in KWin::Compositor::performCompositing (this=0x27dbb00) at /usr/src/debug/kde-workspace-4.10.5/kwin/composite.cpp:610
#14 0x00007f0aa7e575ac in QObject::event (this=0x27dbb00, e=<optimized out>) at kernel/qobject.cpp:1165
#15 0x00007f0aa6fd086c in QApplicationPrivate::notify_helper (this=this@entry=0x264bdf0, receiver=receiver@entry=0x27dbb00, e=e@entry=0x7fffd81924f0) at kernel/qapplication.cpp:4562
#16 0x00007f0aa6fd4ceb in QApplication::notify (this=0x7fffd8192b30, receiver=0x27dbb00, e=0x7fffd81924f0) at kernel/qapplication.cpp:4423
#17 0x00007f0aac6207f6 in KApplication::notify (this=0x7fffd8192b30, receiver=0x27dbb00, event=0x7fffd81924f0) at /usr/src/debug/kdelibs-4.10.5/kdeui/kernel/kapplication.cpp:311
#18 0x00007f0aa7e42d8e in QCoreApplication::notifyInternal (this=0x7fffd8192b30, receiver=0x27dbb00, event=0x7fffd81924f0) at kernel/qcoreapplication.cpp:946
#19 0x00007f0aa7e73b61 in sendEvent (event=0x7fffd81924f0, receiver=<optimized out>) at kernel/qcoreapplication.h:231
#20 QTimerInfoList::activateTimers (this=0x264c7e8) at kernel/qeventdispatcher_unix.cpp:637
#21 0x00007f0aa7e741a0 in QEventDispatcherUNIX::activateTimers (this=this@entry=0x25a4a70) at kernel/qeventdispatcher_unix.cpp:894
#22 0x00007f0aa7e742f8 in QEventDispatcherUNIX::processEvents (this=0x25a4a70, flags=...) at kernel/qeventdispatcher_unix.cpp:956
#23 0x00007f0aa7071a3f in QEventDispatcherX11::processEvents (this=0x25a4a70, flags=...) at kernel/qeventdispatcher_x11.cpp:152
#24 0x00007f0aa7e41adf in QEventLoop::processEvents (this=this@entry=0x7fffd8192840, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007f0aa7e41d68 in QEventLoop::exec (this=0x7fffd8192840, flags=...) at kernel/qeventloop.cpp:204
#26 0x00007f0aa7e46a08 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#27 0x00007f0aace57d9a in kdemain (argc=3, argv=0x7fffd8192c78) at /usr/src/debug/kde-workspace-4.10.5/kwin/main.cpp:537
#28 0x00007f0aaca60a15 in __libc_start_main () from /lib64/libc.so.6
#29 0x0000000000400761 in _start () at ../sysdeps/x86_64/start.S:123

This bug may be a duplicate of or related to bug 320562.

Possible duplicates by query: bug 326154, bug 323624, bug 321125.

Reported using DrKonqi
Comment 1 Thomas Lübking 2013-11-03 06:40:04 UTC
It is the very same bug you reported at least two times before for the very same KDE version.

The bug has been fixed in June for 4.11, but it's not gonna magically fix on your disk.

Since the crash condition is odd, it might rather be a follow up crash (ie. the driver crashes when you close the GL game, kwin autorestarts and crashes in that occasion)

Check whether this is set to "true"

   qdbus org.kde.kwin /KWin supportInformation | grep unredirectFullscreen

If so, disable it. ("kcmshell4 kwincompositing", 3rd tab, "suspend compositing for fullscreen windows")

-------
Just ftr:
First report:                        2013-06-01 03:17:55 UTC
Proposed patch:                2013-06-01 09:40:20 UTC
Patch initially confirmed: 2013-06-05 22:53:44 UTC
Patch pushed:                    2013-06-10 14:57:11 UTC

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