Bug 202572 - KWin Crash from moving a window while applying new window button settings
Summary: KWin Crash from moving a window while applying new window button settings
Status: RESOLVED DUPLICATE of bug 200213
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-05 06:55 UTC by Spencer Clark
Modified: 2009-09-06 15:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Spencer Clark 2009-08-05 06:55:23 UTC
Application that crashed: kwin
Version of the application: 4.3.00 (KDE 4.3.0)
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-ARCH i686

What I was doing when the application crashed:
I reordered the window buttons in System Settings. I pressed apply. While it was applying the settings I tried to move a window. KWin crashed, but restarted immediately.

I'm running with compositing enabled using the closed-source nvidia driver.

 -- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
[KCrash Handler]
#6  0xb7f598ce in QVector<KWin::StrutRect>::realloc () from /usr/lib/libkdeinit4_kwin.so
#7  0xb7fa7ab1 in KWin::Workspace::previousRestrictedMoveArea () from /usr/lib/libkdeinit4_kwin.so
#8  0xb7fb1570 in KWin::Client::checkWorkspacePosition () from /usr/lib/libkdeinit4_kwin.so
#9  0xb7f602ef in KWin::Client::updateDecoration () from /usr/lib/libkdeinit4_kwin.so
#10 0xb7f542fd in KWin::Workspace::slotReconfigure () from /usr/lib/libkdeinit4_kwin.so
#11 0xb7f552fc in KWin::Workspace::qt_metacall () from /usr/lib/libkdeinit4_kwin.so
#12 0xb688998c in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb688a5c2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb68c3a67 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#15 0xb688f03e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#16 0xb6883b3f in QObject::event () from /usr/lib/libQtCore.so.4
#17 0xb6af56c4 in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#18 0xb6afcdac in QApplication::notify () from /usr/lib/libQtGui.so.4
#19 0xb7c02faa in KApplication::notify () from /usr/lib/libkdeui.so.5
#20 0xb7f6b05f in KWin::Application::notify () from /usr/lib/libkdeinit4_kwin.so
#21 0xb6873fab in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#22 0xb68a177e in ?? () from /usr/lib/libQtCore.so.4
#23 0xb689e760 in ?? () from /usr/lib/libQtCore.so.4
#24 0xb3ff0d98 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#25 0xb3ff43e0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#26 0xb3ff4513 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#27 0xb689e6ac in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#28 0xb6b93355 in ?? () from /usr/lib/libQtGui.so.4
#29 0xb6872559 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#30 0xb68729aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#31 0xb6874e1f in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#32 0xb6af5547 in QApplication::exec () from /usr/lib/libQtGui.so.4
#33 0xb7f6d9d4 in kdemain () from /usr/lib/libkdeinit4_kwin.so
#34 0x0804857b in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-08-05 15:19:03 UTC
This looks mostly the same as bug 200213.
As you are using Arch, debugsymbols are hard to get.
- Which window decoration are you usign ?
Thanks
Comment 2 Spencer Clark 2009-08-07 18:38:38 UTC
(In reply to comment #1)
> This looks mostly the same as bug 200213.
> As you are using Arch, debugsymbols are hard to get.
> - Which window decoration are you usign ?
> Thanks

Ozone. I neglected to mention I'm running on two monitors (NVidia TwinView). Don't know if that is relevant or not, but thought I'd mention it.

-Spencer
Comment 3 Martin Flöser 2009-09-06 15:42:23 UTC

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