Bug 217944 - plasma-desktop crashes on no schedule or regular activity
Summary: plasma-desktop crashes on no schedule or regular activity
Status: RESOLVED DUPLICATE of bug 209773
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-12-09 01:28 UTC by josh.chessman
Modified: 2010-02-04 09:17 UTC (History)
1 user (show)

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 josh.chessman 2009-12-09 01:28:06 UTC
Application that crashed: kwin
Version of the application: 4.3.2 (KDE 4.3.2)
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-16-generic x86_64
Distribution: Ubuntu 9.10

 -- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  KWin::CoverSwitchEffect::calculateItemSizes (this=0x20048f0) at ../../../kwin/effects/coverswitch/coverswitch.cpp:1063
#6  0x00007fa4fa954d31 in KWin::CoverSwitchEffect::tabBoxUpdated (this=0x20048f0) at ../../../kwin/effects/coverswitch/coverswitch.cpp:678
#7  0x00007fa50990c35d in KWin::EffectsHandlerImpl::tabBoxUpdated (this=<value optimized out>) at ../../kwin/effects.cpp:295
#8  0x00007fa5098aae50 in KWin::TabBox::setCurrentClient (this=0x200a150, newClient=0x2289cc0) at ../../kwin/tabbox.cpp:538
#9  0x00007fa5098ab086 in KWin::TabBox::nextPrev (this=0x200a150, next=true) at ../../kwin/tabbox.cpp:438
#10 0x00007fa50988cdd0 in KWin::Workspace::removeClient (this=0x1e52450, c=0x4407c20) at ../../kwin/workspace.cpp:627
#11 0x00007fa5098992fe in KWin::Client::releaseWindow (this=0x4407c20, on_shutdown=false) at ../../kwin/client.cpp:239
#12 0x00007fa5098b8f4b in KWin::Client::windowEvent (this=0x4407c20, e=0x7fff0cddd0c0) at ../../kwin/events.cpp:642
#13 0x00007fa5098b9558 in KWin::Workspace::workspaceEvent (this=0x1e52450, e=0x7fff0cddd0c0) at ../../kwin/events.cpp:319
#14 0x00007fa5098a2ab8 in KWin::Application::x11EventFilter (this=0x7fff0cddd4b0, e=0x7fff0cddd0c0) at ../../kwin/main.cpp:357
#15 0x00007fa506088391 in qt_x11EventFilter (ev=0x7fff0cddd0c0) at kernel/qapplication_x11.cpp:375
#16 0x00007fa506098a24 in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7fff0cddd0c0) at kernel/qapplication_x11.cpp:3271
#17 0x00007fa5060c2d0c in x11EventSourceDispatch (s=<value optimized out>, callback=<value optimized out>, user_data=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:146
#18 0x00007fa4ff3e7bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#19 0x00007fa4ff3eb588 in ?? () from /lib/libglib-2.0.so.0
#20 0x00007fa4ff3eb6b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#21 0x00007fa5059521a6 in QEventDispatcherGlib::processEvents (this=0x1bc3e90, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#22 0x00007fa5060c24be in QGuiEventDispatcherGlib::processEvents (this=0x7fff0cddb350, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007fa505928532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#24 0x00007fa505928904 in QEventLoop::exec (this=0x7fff0cddd3f0, flags=) at kernel/qeventloop.cpp:201
#25 0x00007fa50592aab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0x00007fa5098a5094 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../kwin/main.cpp:522
#27 0x00007fa50950fabd 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=0x7fff0cddd998) at libc-start.c:220
#28 0x0000000000400679 in _start () at ../sysdeps/x86_64/elf/start.S:113

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-04 02:20:24 UTC
This could be related to bug 209773. Regards
Comment 2 Martin Flöser 2010-02-04 09:17:17 UTC
*** This bug has been marked as a duplicate of bug 209773 ***