Application that crashed: plasma-desktop Version of the application: 0.3 KDE Version: 4.3.00 (KDE 4.3.0) Qt Version: 4.5.2 Operating System: Linux 2.6.28-14-generic x86_64 Distribution: Ubuntu 9.04 What I was doing when the application crashed: This bug is totally preventing me from using kde-4.3.0, no matter how I start up kde. Worse the restart button does not work, so I am traped on what is now (I cleared out my .kde* stuff) blank black screen. I have to network in and kill the xserver manually. I am using a 64bit Os, and it did start out as ubuntu and not kubuntu, but kde-4.2.3 was working JUST fine a few hours ago. Contact me as needed. -- Backtrace: Application: Plasma Workspace (kdeinit4), signal: Segmentation fault [KCrash Handler] #5 QGraphicsLayoutItem::geometry (this=0x20) at graphicsview/qgraphicslayoutitem.cpp:664 #6 0x00007f35fd327145 in QGraphicsWidget::size (this=<value optimized out>) at graphicsview/qgraphicswidget.cpp:336 #7 0x00007f35f37ac019 in DesktopCorona::loadDefaultLayout (this=0x1f96910) at /build/buildd/kdebase-workspace-4.3.0/plasma/shells/desktop/desktopcorona.cpp:234 #8 0x00007f35f70b1dc5 in Plasma::Corona::initializeLayout (this=0x1f96910, configName=@0x7fff07c7c150) at /build/buildd/kde4libs-4.3.0/plasma/corona.cpp:327 #9 0x00007f35f37c5bfd in PlasmaApp::corona (this=0x1e67a10) at /build/buildd/kdebase-workspace-4.3.0/plasma/shells/desktop/plasmaapp.cpp:574 #10 0x00007f35f37c5d88 in PlasmaApp::setupDesktop (this=0x1e67a10) at /build/buildd/kdebase-workspace-4.3.0/plasma/shells/desktop/plasmaapp.cpp:252 #11 0x00007f35f37c9db5 in PlasmaApp::qt_metacall (this=0x1e67a10, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff07c7c3f0) at /build/buildd/kdebase-workspace-4.3.0/obj-x86_64-linux-gnu/plasma/shells/desktop/plasmaapp.moc:115 #12 0x00007f35ff77fea2 in QMetaObject::activate (sender=0x1f867e0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113 #13 0x00007f35ff78514f in QSingleShotTimer::timerEvent (this=0x1f867e0) at kernel/qtimer.cpp:298 #14 0x00007f35ff77a263 in QObject::event (this=0x1f867e0, e=0x20) at kernel/qobject.cpp:1075 #15 0x00007f35fcd35f4d in QApplicationPrivate::notify_helper (this=0x1e73280, receiver=0x1f867e0, e=0x7fff07c7cab0) at kernel/qapplication.cpp:4056 #16 0x00007f35fcd3e18a in QApplication::notify (this=0x1e67a10, receiver=0x1f867e0, e=0x7fff07c7cab0) at kernel/qapplication.cpp:4021 #17 0x00007f35fde4871b in KApplication::notify (this=0x1e67a10, receiver=0x1f867e0, event=0x7fff07c7cab0) at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302 #18 0x00007f35ff76a6ac in QCoreApplication::notifyInternal (this=0x1e67a10, receiver=0x1f867e0, event=0x7fff07c7cab0) at kernel/qcoreapplication.cpp:610 #19 0x00007f35ff797516 in QTimerInfoList::activateTimers (this=0x1e76840) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #20 0x00007f35ff793b2d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165 #21 0x00007f35fb7c920a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #22 0x00007f35fb7cc8e0 in ?? () from /usr/lib/libglib-2.0.so.0 #23 0x00007f35fb7cca7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #24 0x00007f35ff793a8f in QEventDispatcherGlib::processEvents (this=0x1e68470, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #25 0x00007f35fcdcebdf in QGuiEventDispatcherGlib::processEvents (this=0x7fff07c7ba30, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #26 0x00007f35ff768f42 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 130534688}) at kernel/qeventloop.cpp:149 #27 0x00007f35ff769314 in QEventLoop::exec (this=0x7fff07c7cd60, flags={i = 130534768}) at kernel/qeventloop.cpp:201 #28 0x00007f35ff76b5e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #29 0x00007f35f37b06bb in kdemain (argc=1, argv=0x1e4d110) at /build/buildd/kdebase-workspace-4.3.0/plasma/shells/desktop/main.cpp:50 #30 0x0000000000407215 in launch (argc=1, _name=0x1e47828 "/usr/bin/plasma-desktop", args=<value optimized out>, cwd=0x0, envc=0, envs=0x1e47848 "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40a3a1 "0") at /build/buildd/kde4libs-4.3.0/kinit/kinit.cpp:676 #31 0x0000000000407a38 in handle_launcher_request (sock=7, who=<value optimized out>) at /build/buildd/kde4libs-4.3.0/kinit/kinit.cpp:1168 #32 0x0000000000407fe5 in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.3.0/kinit/kinit.cpp:1361 #33 0x0000000000408b26 in main (argc=2, argv=0x7fff07c7dc08, envp=0x7fff07c7dc20) at /build/buildd/kde4libs-4.3.0/kinit/kinit.cpp:1788 This bug may be a duplicate of or related to bug 202003 Reported using DrKonqi
can you update your packages one more time? there was apparently a bug in the first set of ubuntu packages that would cause the desktop to crash instantly on log in, but which has been fixed in the next set of ubuntu packages.
P.S: probably this is a dup of bug #202558 ?
Confirmed fixed downstream in kdebase-workspace (4:4.3.0-0ubuntu1~jaunty1~ppa4).
*** Bug 202558 has been marked as a duplicate of this bug. ***
I can confirm that the bug is gone with the update that mesirs Cerneels references (kdebase-workspace 4:4.3.0-0ubuntu1~jaunty1~ppa4 and related updates).
hi, I have fixed the problem too with a apt-get dist-upgrade command... Kde 4.3 is really great!!
*** Bug 202603 has been marked as a duplicate of this bug. ***
Hi, I have this issue with SuSE RPMS. If I clean out ~/.kde4 then plasma crashes on startup, however if I press Alt+F2 (krunner works, yeahh!) and execute plasma-desktop it starts up and everything is ok.
Created attachment 36836 [details] kcrash-report Kcrash report I got when plasma crashed directly after system login ...
I have this problem again after todays (10.09.09) update of KDE 4.3.1 (V163) on Opensuse 11.1. Plasma desktop crashes directly after login to user account (root account still works, though!!) attemps to restart plasma-desktop via krunner (which still works, bring up the same result: recrash of desktop with kcrash-report that I did attach. I don't know if this helps much because I don't have enough room for devel-packages on my laptop. But since I can't access most my work-files now, I would be gratefull for a fast solution ... Thanks a lot, Jay
@Jay: please open new reports when you get a crash, and paste the backtrace inline into your comment rather than upload it as a file. that said, it's crashing in the google gadgets library. so you can either try another update or you can open ~/.kde/share/config/plasma-desktop-appletsrc and remove by hand the offending ggl widget or if that's beyond reach then remove the appletsrc file completely. this is, however, not a crash in plasma itself but in google gadgets