Version: (using Devel) Compiler: Using Project Neon nightly snapshots OS: Linux Installed from: Compiled sources Environment description: Intel 945 kwin with compositing enabled using xrender dual head setup with krandr Using the above configuration I have 2 monitors that are running different resolutions. Please see screenshot attached. As the 2 monitors have differing sizes, I have a 'dead zone' beneath the panel that is shown as black in the screenshot. When the cursor is moved into this zone and the left mouse button clicked, kwin crashes with the following backtrace: Application: KWin (kwin), signal SIGABRT Thread 1 (Thread 0xb679a6c0 (LWP 1794)): [KCrash Handler] #6 0xb804a430 in __kernel_vsyscall () #7 0xb6b35880 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb6b37248 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb6fcd51d in qt_message_output () from /opt/project-neon/lib/libQtCore.so.4 #10 0xb6fcd5d2 in qFatal () from /opt/project-neon/lib/libQtCore.so.4 #11 0xb6fcd62c in qt_assert_x () from /opt/project-neon/lib/libQtCore.so.4 #12 0xb7ff1c25 in ?? () from /opt/kde-nightly/lib/libkdeinit4_kwin.so #13 0xb7fe6203 in ?? () from /opt/kde-nightly/lib/libkdeinit4_kwin.so #14 0xb7fe637f in ?? () from /opt/kde-nightly/lib/libkdeinit4_kwin.so #15 0xb7ffb040 in ?? () from /opt/kde-nightly/lib/libkdeinit4_kwin.so #16 0xb7ffc792 in ?? () from /opt/kde-nightly/lib/libkdeinit4_kwin.so #17 0xb7ffcb79 in ?? () from /opt/kde-nightly/lib/libkdeinit4_kwin.so #18 0xb7f99036 in ?? () from /opt/kde-nightly/lib/libkdeinit4_kwin.so #19 0xb70d6ee2 in QMetaObject::activate () from /opt/project-neon/lib/libQtCore.so.4 #20 0xb70d74c2 in QMetaObject::activate () from /opt/project-neon/lib/libQtCore.so.4 #21 0xb710f9b7 in QTimer::timeout () from /opt/project-neon/lib/libQtCore.so.4 #22 0xb70dd4ae in QTimer::timerEvent () from /opt/project-neon/lib/libQtCore.so.4 #23 0xb70d0ecf in QObject::event () from /opt/project-neon/lib/libQtCore.so.4 #24 0xb72fc6ec in QApplicationPrivate::notify_helper () from /opt/project-neon/lib/libQtGui.so.4 #25 0xb7303a9f in QApplication::notify () from /opt/project-neon/lib/libQtGui.so.4 #26 0xb7dae303 in KApplication::notify () from /opt/kde-nightly/lib/libkdeui.so.5 #27 0xb7fb525a in ?? () from /opt/kde-nightly/lib/libkdeinit4_kwin.so #28 0xb70c15a1 in QCoreApplication::notifyInternal () from /opt/project-neon/lib/libQtCore.so.4 #29 0xb70edcf7 in ?? () from /opt/project-neon/lib/libQtCore.so.4 #30 0xb70eaf60 in ?? () from /opt/project-neon/lib/libQtCore.so.4 #31 0xb68546f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #32 0xb6857da3 in ?? () from /usr/lib/libglib-2.0.so.0 #33 0xb6857f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #34 0xb70eaeb8 in QEventDispatcherGlib::processEvents () from /opt/project-neon/lib/libQtCore.so.4 #35 0xb7390315 in ?? () from /opt/project-neon/lib/libQtGui.so.4 #36 0xb70bffaa in QEventLoop::processEvents () from /opt/project-neon/lib/libQtCore.so.4 #37 0xb70c016a in QEventLoop::exec () from /opt/project-neon/lib/libQtCore.so.4 #38 0xb70c520d in QCoreApplication::exec () from /opt/project-neon/lib/libQtCore.so.4 #39 0xb72fc417 in QApplication::exec () from /opt/project-neon/lib/libQtGui.so.4 #40 0xb7fb67bf in kdemain () from /opt/kde-nightly/lib/libkdeinit4_kwin.so #41 0x080487c2 in _start () This is reproducible 100% of the time. Expected behavior: Cursor should not be allowed to enter this space and therefore the crash should never be possible. Additional notes: - The dead zone can be entered from either screen - The crash seems to only occur when there is more than 1 item in the task manager. Not sure why this would be the case but seems to hold true.
Created attachment 31139 [details] Dual head screenshot showing deadzone Dead zone is shown as a black area beneath the taskbar on the right hand screen. Clicking anywhere in this black space causes the crash.
As you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? You need to install debug symbols for "kdebase-workspace" Thanks :)
Sorry, thought the lack of '(No debugging symbols found)' meant I had them installed. Here is the backtrace with kdebase* debug packages: Application: KWin (kwin), signal SIGABRT Thread 1 (Thread 0xb67706c0 (LWP 6909)): [KCrash Handler] #6 0xb8022430 in __kernel_vsyscall () #7 0xb6b0b880 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb6b0d248 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb6fa351d in qt_message_output () from /opt/project-neon/lib/libQtCore.so.4 #10 0xb6fa35d2 in qFatal () from /opt/project-neon/lib/libQtCore.so.4 #11 0xb6fa362c in qt_assert_x () from /opt/project-neon/lib/libQtCore.so.4 #12 0xb7fc8e15 in QVector<QRect>::operator[] (this=0x3, i=-1228691388) at /opt/project-neon/include/QtCore/qvector.h:321 #13 0xb7fbd3f3 in KWin::Workspace::clientArea (this=0x91dd8d8, opt=KWin::FullArea, screen=-1, desktop=4) at /build/buildd/kde-nightly-kdebase-20090206+svn922409/workspace/kwin/geometry.cpp:239 #14 0xb7fbd56f in KWin::Workspace::clientArea (this=0x91dd8d8, opt=KWin::FullArea, p=@0xbfb23158, desktop=4) at /build/buildd/kde-nightly-kdebase-20090206+svn922409/workspace/kwin/geometry.cpp:283 #15 0xb7fd2230 in KWin::Unmanaged::shouldUnredirect (this=0x92f4d18) at /build/buildd/kde-nightly-kdebase-20090206+svn922409/workspace/kwin/composite.cpp:927 #16 0xb7fd39e2 in KWin::Toplevel::updateUnredirectedState (this=0x92f4d18) at /build/buildd/kde-nightly-kdebase-20090206+svn922409/workspace/kwin/composite.cpp:849 #17 0xb7fd3dc9 in KWin::Workspace::delayedCheckUnredirect (this=0x91dd8d8) at /build/buildd/kde-nightly-kdebase-20090206+svn922409/workspace/kwin/composite.cpp:617 #18 0xb7f70096 in KWin::Workspace::qt_metacall (this=0x91dd8d8, _c=QMetaObject::InvokeMetaMethod, _id=145, _a=0xbfb23358) at /build/buildd/kde-nightly-kdebase-20090206+svn922409/obj-i486-linux-gnu/workspace/kwin/workspace.moc:450 #19 0xb70acee2 in QMetaObject::activate () from /opt/project-neon/lib/libQtCore.so.4 #20 0xb70ad4c2 in QMetaObject::activate () from /opt/project-neon/lib/libQtCore.so.4 #21 0xb70e59b7 in QTimer::timeout () from /opt/project-neon/lib/libQtCore.so.4 #22 0xb70b34ae in QTimer::timerEvent () from /opt/project-neon/lib/libQtCore.so.4 #23 0xb70a6ecf in QObject::event () from /opt/project-neon/lib/libQtCore.so.4 #24 0xb72d26ec in QApplicationPrivate::notify_helper () from /opt/project-neon/lib/libQtGui.so.4 #25 0xb72d9a9f in QApplication::notify () from /opt/project-neon/lib/libQtGui.so.4 #26 0xb7d844a3 in KApplication::notify (this=0xbfb23b20, receiver=0x91ddb80, event=0xbfb2382c) at /build/buildd/kde-nightly-kdelibs-20090206+svn922409/kdeui/kernel/kapplication.cpp:307 #27 0xb7f8c44a in KWin::Application::notify (this=0xbfb23b20, o=0x91ddb80, e=0xbfb2382c) at /build/buildd/kde-nightly-kdebase-20090206+svn922409/workspace/kwin/main.cpp:368 #28 0xb70975a1 in QCoreApplication::notifyInternal () from /opt/project-neon/lib/libQtCore.so.4 #29 0xb70c3cf7 in ?? () from /opt/project-neon/lib/libQtCore.so.4 #30 0xb70c0f60 in ?? () from /opt/project-neon/lib/libQtCore.so.4 #31 0xb682a6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #32 0xb682dda3 in ?? () from /usr/lib/libglib-2.0.so.0 #33 0xb682df61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #34 0xb70c0eb8 in QEventDispatcherGlib::processEvents () from /opt/project-neon/lib/libQtCore.so.4 #35 0xb7366315 in ?? () from /opt/project-neon/lib/libQtGui.so.4 #36 0xb7095faa in QEventLoop::processEvents () from /opt/project-neon/lib/libQtCore.so.4 #37 0xb709616a in QEventLoop::exec () from /opt/project-neon/lib/libQtCore.so.4 #38 0xb709b20d in QCoreApplication::exec () from /opt/project-neon/lib/libQtCore.so.4 #39 0xb72d2417 in QApplication::exec () from /opt/project-neon/lib/libQtGui.so.4 #40 0xb7f8d9af in kdemain (argc=3, argv=0xbfb23d04) at /build/buildd/kde-nightly-kdebase-20090206+svn922409/workspace/kwin/main.cpp:519 #41 0x080487c2 in main (argc=) at /build/buildd/kde-nightly-kdebase-20090206+svn922409/obj-i486-linux-gnu/workspace/kwin/kwin_dummy.cpp:3
*** This bug has been marked as a duplicate of bug 177006 ***