Bug 226531 - Decorator crash at Xorg startup
Summary: Decorator crash at Xorg startup
Status: RESOLVED DUPLICATE of bug 220902
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-12 13:38 UTC by paun
Modified: 2010-02-12 14:43 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 paun 2010-02-12 13:38:35 UTC
Application: kde4-window-decorator (0.0.1)
KDE Platform Version: 4.4.00 (KDE 4.4.0)
Qt Version: 4.6.1
Operating System: Linux 2.6.31-14-generic i686
Distribution: Ubuntu 9.10

-- Information about the crash:
Desktop, widgets and panel are not loading. I just get a brown desktop with all files being shown.

The crash can be reproduced every time.

 -- Backtrace:
Application: KDE Window Decorator (kde4-window-decorator), signal: Segmentation fault
[KCrash Handler]
#6  0x776f646e in ?? ()
#7  0x0050e651 in KCommonDecorationUnstable::clientGroupItems (this=0x9fbdcd8) at ../../../kwin/lib/kcommondecoration.cpp:1295
#8  0x06673f67 in Oxygen::OxygenClient::updateItemBoundingRects (this=0x9fbdcd8, alsoUpdate=false) at ../../../../kwin/clients/oxygen/oxygenclient.cpp:467
#9  0x066753cb in Oxygen::OxygenClient::paintEvent (this=0x9fbdcd8, event=0xbfcb2b64) at ../../../../kwin/clients/oxygen/oxygenclient.cpp:1386
#10 0x0050eb94 in KCommonDecoration::eventFilter (this=0x9fbdcd8, o=0x9fb32e8, e=0xbfcb2b64) at ../../../kwin/lib/kcommondecoration.cpp:886
#11 0x0050ec0b in KCommonDecorationUnstable::eventFilter (this=0x9fbdcd8, o=0x9fb32e8, e=0xbfcb2b64) at ../../../kwin/lib/kcommondecoration.cpp:1350
#12 0x0666b5bf in Oxygen::OxygenClient::eventFilter (this=0x9fbdcd8, object=0x9fb32e8, event=0xbfcb2b64) at ../../../../kwin/clients/oxygen/oxygenclient.cpp:1290
#13 0x003e5f9a in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x9e83e40, receiver=0x9fb32e8, event=0xbfcb2b64) at kernel/qcoreapplication.cpp:819
#14 0x01078259 in QApplicationPrivate::notify_helper (this=0x9e83e40, receiver=0x9fb32e8, e=0xbfcb2b64) at kernel/qapplication.cpp:4294
#15 0x0107ef79 in QApplication::notify (this=0x9e70948, receiver=0x9fb32e8, e=0xbfcb2b64) at kernel/qapplication.cpp:4263
#16 0x09aee1fa in KApplication::notify (this=0x9e70948, receiver=0x9fb32e8, event=0xbfcb2b64) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x003e6cfb in QCoreApplication::notifyInternal (this=0x9e70948, receiver=0x9fb32e8, event=0xbfcb2b64) at kernel/qcoreapplication.cpp:704
#18 0x010df666 in QCoreApplication::sendSpontaneousEvent (this=0x9fbfa68, pdev=0xbfcb2fdc, rgn=..., offset=..., flags=<value optimized out>, sharedPainter=0x0, backingStore=0x0)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#19 QWidgetPrivate::drawWidget (this=0x9fbfa68, pdev=0xbfcb2fdc, rgn=..., offset=..., flags=<value optimized out>, sharedPainter=0x0, backingStore=0x0) at kernel/qwidget.cpp:5321
#20 0x010e0710 in QWidget::render (this=0x9fb32e8, target=0xbfcb2fdc, targetOffset=..., sourceRegion=..., renderFlags=...) at kernel/qwidget.cpp:4920
#21 0x080650c3 in ?? ()
#22 0x0805e8cf in ?? ()
#23 0x08065b95 in ?? ()
#24 0x003ebf6a in QMetaObject::metacall (object=0x9fbe620, cl=167501016, idx=8, argv=0xbfcb30fc) at kernel/qmetaobject.cpp:237
#25 0x003fa705 in QMetaObject::activate (sender=0x9fc1628, m=0x8068460, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3275
#26 0x08065cd9 in ?? ()
#27 0x08065d23 in ?? ()
#28 0x003ebf6a in QMetaObject::metacall (object=0x9fc1628, cl=167501016, idx=4, argv=0xbfcb320c) at kernel/qmetaobject.cpp:237
#29 0x003fa705 in QMetaObject::activate (sender=0x9fc163c, m=0x4fb5a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3275
#30 0x0044bec7 in QTimer::timeout (this=0x9fc163c) at .moc/release-shared/moc_qtimer.cpp:134
#31 0x0040283e in QTimer::timerEvent (this=0x9fc163c, e=0xbfcb3740) at kernel/qtimer.cpp:271
#32 0x003f75a4 in QObject::event (this=0x9fc163c, e=0x806836c) at kernel/qobject.cpp:1212
#33 0x0107827c in QApplicationPrivate::notify_helper (this=0x9e83e40, receiver=0x9fc163c, e=0xbfcb3740) at kernel/qapplication.cpp:4298
#34 0x0107eede in QApplication::notify (this=0x9e70948, receiver=0x9fc163c, e=0xbfcb3740) at kernel/qapplication.cpp:3702
#35 0x09aee1fa in KApplication::notify (this=0x9e70948, receiver=0x9fc163c, event=0xbfcb3740) at ../../kdeui/kernel/kapplication.cpp:302
#36 0x003e6cfb in QCoreApplication::notifyInternal (this=0x9e70948, receiver=0x9fc163c, event=0xbfcb3740) at kernel/qcoreapplication.cpp:704
#37 0x00415f96 in QCoreApplication::sendEvent (this=0x9e86f34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#38 QTimerInfoList::activateTimers (this=0x9e86f34) at kernel/qeventdispatcher_unix.cpp:603
#39 0x00412bf4 in timerSourceDispatch (source=0x9e86f00) at kernel/qeventdispatcher_glib.cpp:184
#40 0x00eb1e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#41 0x00eb5730 in ?? () from /lib/libglib-2.0.so.0
#42 0x00eb5863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#43 0x004128e5 in QEventDispatcherGlib::processEvents (this=0x9e6dcd8, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#44 0x01137485 in QGuiEventDispatcherGlib::processEvents (this=0x9e6dcd8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#45 0x003e5319 in QEventLoop::processEvents (this=0xbfcb3a04, flags=) at kernel/qeventloop.cpp:149
#46 0x003e576a in QEventLoop::exec (this=0xbfcb3a04, flags=...) at kernel/qeventloop.cpp:201
#47 0x003e995f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#48 0x01078317 in QApplication::exec () at kernel/qapplication.cpp:3577
#49 0x08050432 in ?? ()
#50 0x00b72b56 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#51 0x0804fb81 in ?? ()

This bug may be a duplicate of or related to bug 143419.

Possible duplicates by query: bug 226359, bug 220902.

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-12 14:43:33 UTC
This is a Compiz bug  (as explained in bug 226359 comment 1)
Thanks

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