Bug 250297

Summary: Kde4-windows-manager didn't start after doing a nvidia-xconfig and a restart of the x server.
Product: [I don't know] kde Reporter: Aaron Verhoeven <bzchickin>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Aaron Verhoeven 2010-09-05 18:59:47 UTC
Application: kde4-window-decorator (0.0.1)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-22-generic i686
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
I, after having trouble getting onto my desktop, got onto my desktop, and the first window I was greeted with was a kde window decorator crashed message, hence my writing of this bug report. I do have compiz running, and it's running fine, except for the menu bars.

The crash can be reproduced every time.

 -- Backtrace:
Application: KDE Window Decorator (kde4-window-decorator), signal: Segmentation fault
[KCrash Handler]
#6  0x574b334e in ?? ()
#7  0x00f8d947 in KDecorationUnstable::compositingActive (this=0x98da710) at ../../../kwin/lib/kdecoration.cpp:406
#8  0x00f93705 in KCommonDecorationUnstable::compositingActive (this=0x98d3d20) at ../../../kwin/lib/kcommondecoration.cpp:1283
#9  0x00fa35dd in Aurorae::AuroraeClient::updateWindowShape (this=0x98d3d20) at ../../../../../kwin/clients/aurorae/src/aurorae.cpp:913
#10 0x00f95866 in KCommonDecoration::resizeEvent (this=0x98d3d20) at ../../../kwin/lib/kcommondecoration.cpp:739
#11 0x00f93bbf in KCommonDecoration::eventFilter (this=0x98d3d20, o=0x98d40d0, e=0xbf98bcd8) at ../../../kwin/lib/kcommondecoration.cpp:883
#12 0x00f93c4b in KCommonDecorationUnstable::eventFilter (this=0x98d3d20, o=0x98d40d0, e=0xbf98bcd8) at ../../../kwin/lib/kcommondecoration.cpp:1350
#13 0x003e8cda in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x9722200, receiver=0x98d40d0, event=0xbf98bcd8) at kernel/qcoreapplication.cpp:819
#14 0x010f74b9 in QApplicationPrivate::notify_helper (this=0x9722200, receiver=0x98d40d0, e=0xbf98bcd8) at kernel/qapplication.cpp:4296
#15 0x010fe0f9 in QApplication::notify (this=0x970ed08, receiver=0x98d40d0, e=0xbf98bcd8) at kernel/qapplication.cpp:4265
#16 0x079bef2a in KApplication::notify (this=0x970ed08, receiver=0x98d40d0, event=0xbf98bcd8) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x003e9a3b in QCoreApplication::notifyInternal (this=0x970ed08, receiver=0x98d40d0, event=0xbf98bcd8) at kernel/qcoreapplication.cpp:704
#18 0x01154719 in QCoreApplication::sendEvent (this=0x98f9b90, recursive=false, disableUpdates=false) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QWidgetPrivate::sendPendingMoveAndResizeEvents (this=0x98f9b90, recursive=false, disableUpdates=false) at kernel/qwidget.cpp:7086
#20 0x0115b379 in QWidgetPrivate::show_helper (this=0x98f9b90) at kernel/qwidget.cpp:7137
#21 0x0115d99b in QWidget::setVisible (this=0x98d40d0, visible=true) at kernel/qwidget.cpp:7418
#22 0x08059c0f in QWidget::show (this=0x98d3c18, force=true) at /usr/include/qt4/QtGui/qwidget.h:485
#23 KWD::Window::resizeDecoration (this=0x98d3c18, force=true) at ../../../kde/window-decorator-kde4/window.cpp:867
#24 0x0805a3ab in KWD::Window::createDecoration (this=0x98d3c18) at ../../../kde/window-decorator-kde4/window.cpp:794
#25 0x0805deae in Window (this=0x98d3c18, parentId=50333051, clientId=346, frame=0, type=KWD::Window::Default, x=0, y=0, w=1, h=1) at ../../../kde/window-decorator-kde4/window.cpp:152
#26 0x08057146 in KWD::Decorator::enableDecorations (this=0x970ed08, timestamp=397589) at ../../../kde/window-decorator-kde4/decorator.cpp:212
#27 0x0805066d in main (argc=1, argv=0xbf98c214) at ../../../kde/window-decorator-kde4/main.cpp:113

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

Possible duplicates by query: bug 235975.

Reported using DrKonqi
Comment 1 Christoph Feck 2010-09-06 00:18:32 UTC

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