Version: SVN Yesterday (using Devel) Installed from: Compiled sources Compiler: g++ (GCC) 4.2.3 (Ubuntu 4.2.3-2ubuntu7) OS: Linux Plasma crashes at startup. From looking at the BT it appears to be due to an un-initialized instance of KConfig. See BT below. Application: Plasma Workspace (plasma), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb572f940 (LWP 22867)] [KCrash handler] #6 0xb6d6b270 in KConfig::d_func (this=0x0) at /home/jackrabbit/kde/src/KDE/kdelibs/kdecore/config/kconfig.h:274 #7 0xb6d66aa5 in KConfig::name (this=0x0) at /home/jackrabbit/kde/src/KDE/kdelibs/kdecore/config/kconfig.cpp:396 #8 0xb7e95b01 in Plasma::Applet::saveState (this=0x814c2f8, group=@0x814c300) at /home/jackrabbit/kde/src/KDE/kdebase/workspace/libs/plasma/applet.cpp:261 #9 0xb7ec6e46 in Plasma::Corona::loadLayout (this=0x811b6b0, configName=@0xbff81c00) at /home/jackrabbit/kde/src/KDE/kdebase/workspace/libs/plasma/corona.cpp:273 #10 0xb7ec7360 in Plasma::Corona::initializeLayout (this=0x811b6b0, configName=@0xbff81c00) at /home/jackrabbit/kde/src/KDE/kdebase/workspace/libs/plasma/corona.cpp:228 #11 0xb7f8da97 in PlasmaApp::corona (this=0x80771d8) at /home/jackrabbit/kde/src/KDE/kdebase/workspace/plasma/plasma/plasmaapp.cpp:383 #12 0xb7f8f343 in PlasmaApp (this=0x80771d8, display=0x805a9e8, visual=0, colormap=0) at /home/jackrabbit/kde/src/KDE/kdebase/workspace/plasma/plasma/plasmaapp.cpp:213 #13 0xb7f8fd12 in PlasmaApp::self () at /home/jackrabbit/kde/src/KDE/kdebase/workspace/plasma/plasma/plasmaapp.cpp:109 #14 0xb7f8d2ad in kdemain (argc=1, argv=0xbff81e74) at /home/jackrabbit/kde/src/KDE/kdebase/workspace/plasma/plasma/main.cpp:51 #15 0x080487a6 in main (argc=1994412, argv=0xb72bf848) at /home/jackrabbit/kde/build/KDE/kdebase/workspace/plasma/plasma/plasma-qgv_dummy.cpp:3 #0 0xb7fa9410 in __kernel_vsyscall ()
If you restart it, does it crash again?
Yes. With the same backtrace.
And what if you use a clean user account?
A clean user account works. I'm going to see if I can find more details on what's broken in my configuration.
Just great. Same configuration and set of binaries as yesterday, and now it works fine. So that makes it hard to find anything useful. All I can think of now is that the position of the stars are different than yesterday.
I had a very similar backtrace to this one, the issue turned out to be that I had compiled a few plasmoids from outside of kdebase. Plasma was fine, but when it tried to load the settings for either the comic or the twitter plasmoid, there was some form of bc issue, bringing all of plasma down.
yes, this is a BC issue. note how corona.cpp:273 is a call to init() but instead saveState() is being called.
*** Bug 165184 has been marked as a duplicate of this bug. ***
*** Bug 165299 has been marked as a duplicate of this bug. ***
how to resolve this ?????????? i am facing pretty much the same situation ! :( :( every time i login this crash handler pops out ! wats the soltion ????
@Abhinav: you could: 1) install the latest software version 2) use a clean user account It should be enough.