Bug 222736

Summary: Present windows has crashed KWin (after tweaking his settings)
Product: [Plasma] kwin Reporter: Jakub 'Livio' Rusinek <kontakt>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jakub 'Livio' Rusinek 2010-01-14 17:59:57 UTC
Application that crashed: kwin
Version of the application: 4.3.4 (KDE 4.3.4) "release 2"
KDE Version: 4.3.4 (KDE 4.3.4) "release 2"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.5-0.1-desktop i686
Distribution: "openSUSE 11.2 (i586)"

What I was doing when the application crashed:
What details can I give you?

I've been turning plugins on and off, tweaking cube's settings, but didn't touch present windows at all, but it crashed KWin.

Installed kwin-debuginfo and here's a detailed report :) .

 -- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
[KCrash Handler]
#6  0xb6ecfa66 in KWin::WindowMotionManager::manage (this=0x81cc084, w=0x60) at /usr/src/debug/kdebase-workspace-4.3.4/kwin/lib/kwineffects.cpp:1148
#7  0xb044f8f1 in KWin::PresentWindowsEffect::setActive (this=0x81cc040, active=true, closingTab=false) at /usr/src/debug/kdebase-workspace-4.3.4/kwin/effects/presentwindows/presentwindows.cpp:1234
#8  0xb0450b97 in toggleActiveAllDesktops (this=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.3.4/kwin/effects/presentwindows/presentwindows.h:96
#9  KWin::PresentWindowsEffect::borderActivated (this=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.3.4/kwin/effects/presentwindows/presentwindows.cpp:372
#10 0xb77439ed in KWin::EffectsHandlerImpl::borderActivated (this=0x8245c78, border=ElectricTopRight) at /usr/src/debug/kdebase-workspace-4.3.4/kwin/effects.cpp:313
#11 0xb76b60a5 in KWin::Workspace::checkElectricBorder (this=0x824c4e0, pos=..., now=7165681) at /usr/src/debug/kdebase-workspace-4.3.4/kwin/workspace.cpp:2180
#12 0xb76b6575 in KWin::Workspace::electricBorderEvent (this=0x824c4e0, e=0xbf85d03c) at /usr/src/debug/kdebase-workspace-4.3.4/kwin/workspace.cpp:2248
#13 0xb76e37e9 in KWin::Workspace::workspaceEvent (this=0x824c4e0, e=0xbf85d03c) at /usr/src/debug/kdebase-workspace-4.3.4/kwin/events.cpp:475
#14 0xb76c96e2 in KWin::Application::x11EventFilter (this=0xbf85d3a8, e=0xbf85d03c) at /usr/src/debug/kdebase-workspace-4.3.4/kwin/main.cpp:357
#15 0xb61d4be1 in qt_x11EventFilter (ev=0xbf85d03c) at kernel/qapplication_x11.cpp:377
#16 0xb61e668f in QApplication::x11ProcessEvent (this=0xbf85d3a8, event=0xbf85d03c) at kernel/qapplication_x11.cpp:3271
#17 0xb6212b68 in x11EventSourceDispatch (s=0x8081b00, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#18 0xb2f164c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0xb2f19d98 in ?? () from /usr/lib/libglib-2.0.so.0
#20 0xb2f19ebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#21 0xb5f19011 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#22 0xb621229a in QGuiEventDispatcherGlib::processEvents (this=0x804fdd0, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#23 0xb5eeb98d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#24 0xb5eebdd9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#25 0xb5eee270 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#26 0xb6170774 in QApplication::exec () at kernel/qapplication.cpp:3525
#27 0xb76cc1ec in kdemain (argc=1, argv=0xbf85d594) at /usr/src/debug/kdebase-workspace-4.3.4/kwin/main.cpp:522
#28 0x080485fb in main (argc=1, argv=0xbf85d594) at /usr/src/debug/kdebase-workspace-4.3.4/build/kwin/kwin_dummy.cpp:3

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-15 00:32:22 UTC
This could be related to bug 222193.
Comment 2 Martin Flöser 2010-01-15 19:52:06 UTC

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