| Summary: | Kwin crash when activating Present Windows - Current desktop shortcut | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | aku.pietikainen |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | andresbajotierra, ignacio.peixoto, kontakt, richard-bugs |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Unlisted Binaries | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
The code section in question says you were using alt+tab at that time. Is that right? Did you before or after triggering the edge use alt+tab? Is it possible that a window was closed at that time or that no window at all was visible? I used alt+tab before triggering the edge. I believe there was one window on the desktop. I did not close any before or after alt+tab. Do you use present windows as the effect for alt+tab? Yes, present windows for alt+tab. SVN commit 1073247 by graesslin: Do not add NULL effect windows to the motion manager. BUG: 222193 M +2 -0 presentwindows.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1073247 SVN commit 1073249 by graesslin: Backport rev 1073247 Do not add NULL effect windows to the motion manager. CCBUG: 222193 M +2 -0 presentwindows.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1073249 SVN commit 1073251 by graesslin: Backport rev 1073247 Do not add NULL effect windows to the motion manager. CCBUG: 222193 M +2 -0 presentwindows.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1073251 @Martin: - Does this also fix bug 220789 and bug 222736? (the backtraces seem to be related/the same) Thanks *** Bug 220789 has been marked as a duplicate of this bug. *** *** Bug 222736 has been marked as a duplicate of this bug. *** *** Bug 251477 has been marked as a duplicate of this bug. *** |
Application that crashed: kwin Version of the application: 4.3.4 (KDE 4.3.4) KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.2 Operating System: Linux 2.6.31-17-generic x86_64 Distribution: Ubuntu 9.10 What I was doing when the application crashed: Activated Present Windows trigger on the edge of screen. The desktpo effect seemed extremely slow and then crashed. After kwin restarted, it disabled composing. -- Backtrace: Application: KWin (kwin), signal: Segmentation fault The current source language is "auto; currently c". [KCrash Handler] #5 KWin::WindowMotionManager::manage (this=<value optimized out>, w=0x0) at ../../../kwin/lib/kwineffects.cpp:1148 #6 0x00007f3f786da7f3 in KWin::PresentWindowsEffect::setActive (this=0x21f4440, active=<value optimized out>, closingTab=<value optimized out>) at ../../../kwin/effects/presentwindows/presentwindows.cpp:1234 #7 0x00007f3f786dba29 in KWin::PresentWindowsEffect::toggleActive (this=0x21f4440, border=KWin::ElectricBottomLeft) at ../../../kwin/effects/presentwindows/presentwindows.h:95 #8 KWin::PresentWindowsEffect::borderActivated (this=0x21f4440, border=KWin::ElectricBottomLeft) at ../../../kwin/effects/presentwindows/presentwindows.cpp:370 #9 0x00007f3f8ad2a076 in KWin::EffectsHandlerImpl::borderActivated (this=<value optimized out>, border=KWin::ElectricBottomLeft) at ../../kwin/effects.cpp:313 #10 0x00007f3f8acae959 in KWin::Workspace::checkElectricBorder (this=0x2073440, pos=..., now=<value optimized out>) at ../../kwin/workspace.cpp:2180 #11 0x00007f3f8acaedec in KWin::Workspace::electricBorderEvent (this=0x0, e=<value optimized out>) at ../../kwin/workspace.cpp:2248 #12 0x00007f3f8acd69d2 in KWin::Workspace::workspaceEvent (this=0x2073440, e=0x7ffffc475290) at ../../kwin/events.cpp:475 #13 0x00007f3f8acbfc08 in KWin::Application::x11EventFilter (this=0x7ffffc475680, e=0x7ffffc475290) at ../../kwin/main.cpp:357 #14 0x00007f3f874a1391 in qt_x11EventFilter (ev=0x7ffffc475290) at kernel/qapplication_x11.cpp:375 #15 0x00007f3f874b1a24 in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7ffffc475290) at kernel/qapplication_x11.cpp:3271 #16 0x00007f3f874dbd0c in x11EventSourceDispatch (s=<value optimized out>, callback=<value optimized out>, user_data=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:146 #17 0x00007f3f80800bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #18 0x00007f3f80804598 in ?? () from /lib/libglib-2.0.so.0 #19 0x00007f3f808046c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #20 0x00007f3f86d6b1a6 in QEventDispatcherGlib::processEvents (this=0x1d60e90, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #21 0x00007f3f874db4be in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #22 0x00007f3f86d41532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #23 0x00007f3f86d41904 in QEventLoop::exec (this=0x7ffffc4755c0, flags=) at kernel/qeventloop.cpp:201 #24 0x00007f3f86d43ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #25 0x00007f3f8acc21e4 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../kwin/main.cpp:522 #26 0x00007f3f8a92cabd 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=0x7ffffc475b68) at libc-start.c:220 #27 0x0000000000400679 in _start () at ../sysdeps/x86_64/elf/start.S:113 Reported using DrKonqi