Bug 333920 - Crash after using the exposé effect
Summary: Crash after using the exposé effect
Status: RESOLVED DUPLICATE of bug 326032
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 4.11.8
Platform: Chakra Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-04-26 15:12 UTC by Fabian
Modified: 2014-04-30 12:17 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 Fabian 2014-04-26 15:12:56 UTC
Application: kwin (4.11.8)
KDE Platform Version: 4.13.0
Qt Version: 4.8.5
Operating System: Linux 3.12.15-1-CHAKRA x86_64
Distribution: "Chakra"

-- Information about the crash:
- What I was doing when the application crashed:
I activatedd the exposé effect (the one showing all virtual desktop) and moved one window from  one virtual desktop to another.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[KCrash Handler]
#6  size (this=0x8) at /usr/include/QtCore/qhash.h:295
#7  QHash<KWin::EffectWindow*, KWin::WindowMotionManager::WindowMotion>::keys (this=0x8) at /usr/include/QtCore/qhash.h:651
#8  0x00007f927437a119 in managedWindows (this=0x0) at /chakra/desktop-testing/kde-workspace/src/kde-workspace-4.11.8/kwin/libkwineffects/kwineffects.h:2519
#9  KWin::DesktopGridEffect::windowInputMouseEvent (this=0x2ea5560, e=<optimized out>) at /chakra/desktop-testing/kde-workspace/src/kde-workspace-4.11.8/kwin/effects/desktopgrid/desktopgrid.cpp:576
#10 0x00007f929b1c2bdb in KWin::EffectsHandlerImpl::checkInputWindowEvent (this=<optimized out>, e=0x7fffd920e450) at /chakra/desktop-testing/kde-workspace/src/kde-workspace-4.11.8/kwin/effects.cpp:1247
#11 0x00007f929b1594f5 in KWin::Workspace::workspaceEvent (this=0x27a8920, e=0x7fffd920e450) at /chakra/desktop-testing/kde-workspace/src/kde-workspace-4.11.8/kwin/events.cpp:113
#12 0x00007f929b14e1c0 in KWin::Application::x11EventFilter (this=0x7fffd920e850, e=0x7fffd920e450) at /chakra/desktop-testing/kde-workspace/src/kde-workspace-4.11.8/kwin/main.cpp:422
#13 0x00007f92941789dc in qt_x11EventFilter (ev=0x7fffd920e450) at kernel/qapplication_x11.cpp:435
#14 0x00007f9294187698 in QApplication::x11ProcessEvent (this=0x7fffd920e850, event=0x7fffd920e450) at kernel/qapplication_x11.cpp:3352
#15 0x00007f92941b05a8 in QEventDispatcherX11::processEvents (this=0x246db00, flags=...) at kernel/qeventdispatcher_x11.cpp:132
#16 0x00007f929502b26f in QEventLoop::processEvents (this=this@entry=0x7fffd920e6c0, flags=...) at kernel/qeventloop.cpp:149
#17 0x00007f929502b505 in QEventLoop::exec (this=0x7fffd920e6c0, flags=...) at kernel/qeventloop.cpp:204
#18 0x00007f92950313d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#19 0x00007f929b14f0a6 in kdemain (argc=3, argv=0x7fffd920e998) at /chakra/desktop-testing/kde-workspace/src/kde-workspace-4.11.8/kwin/main.cpp:597
#20 0x00007f929ad49bc5 in __libc_start_main () from /lib/libc.so.6
#21 0x00000000004006d1 in _start ()

Reported using DrKonqi
Comment 1 Thomas Lübking 2014-04-26 15:21:01 UTC
Is it a multiscreen setup?

FYI: Apples pendant of "Desktop Grid" is "Spaces"
I initially looked up the wrong code ;-)
Comment 2 Fabian 2014-04-26 15:29:36 UTC
I'm actually not sure. It's  dual monitor setup, but with the laptop monitor turned off. And sorry for the naming confusion.
Comment 3 Thomas Lübking 2014-04-26 15:42:07 UTC
could easily be dupe of bug #326032 then (supposingly fixed in 4.11.9) - it requires the desktop grid active while the screencount changes.
could you reproduce this (or similar) crashes (for confirmation - 11.9 should hit arch repos next week)
Comment 4 Fabian 2014-04-26 15:43:58 UTC
Arch repos won't help, as they're incompatible with Chakra's, but sure, once I have some time I'll compile 4.11.9 and try to reproduce it.
Comment 5 Fabian 2014-04-30 08:57:47 UTC
With 4.11.9, I've been unable to reproduce this bug and 326032, so I consider this to be fixed.
Comment 6 Thomas Lübking 2014-04-30 12:17:33 UTC

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