Registered Member
|
Hi All,
I've got a reliable plasma crash on startup. I've just upgraded my kubuntu desktop, and I'm getting a lot of messages in .xsession-errors like: plasma-desktop(3053)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability ...and those two things are making me guess that I've probably got some old plugins that aren't compatable with the latest version, which is breaking plasma. Can anyone please point me at where to look to determine which plugin(s) might be failing? I don't really want to start from a completely fresh config, so I'd prefer to just disable whats broke and leave the rest. I'm running kubuntu 13.04.
I've tried following advice from other posts which suggested clearing .xsession-errors, then enabling anything plasma-related in kdebugdialog. This results in (no surprise) lots of data, but its not clear to me what might be causing the plasma crash. (I could post the whole output here - and will, if anyone thinks its useful - but I'm really looking to learn how to figure this out myself, rather than have someone fix it for me...) |
Administrator
|
Do you have a backtrace (Developer Information) from your Plasma Desktop crash?
Also, have you tried moving the Plasma Desktop configuration files elsewhere temporarily, to see if a default configuration starts successfully? If it does not, it may be worth checking to see if all packages were fully updated in the upgrade (sometimes they get missed for various reasons - which can include the repository not yet being 100% up to date).
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Thanks for the reply.
I did have a stack trace from the KDE crash handler... but for some reason it is no longer running every time I restart, and I don't appear to have kept a copy. I'll see if I can get it to trigger again, but it didn't identify a specific plugin / element in any way that I could recognise. Plasma does start fine if I move the plasma config aside (sorry, should have mentioned that) which is part of why I'm convinced it must be some add-on or plugin I installed in previous versions causing the crash. My problem is that I'd rather not build my config back up from scratch, and I'm hoping there is some more efficient method of identifying the broken element than trial-and-error replacing bits of my old config until it starts successfully. I thought perhaps there might be a log file somewhere that showed individual UI elements starting up, but if its there, its in some file or some form that I'm not recognising. |
Administrator
|
Plasma Desktop might be starting up with the "--nocrashhandler" argument - designed to prevent repeated spawns of the crash assistant.
If it is, try restarting plasma-desktop by running the following in Konsole:
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Here's a backtrace.
If I start to try to report the crash, it flags it as a duplicate of an existing bug. And in any case, the fact that a clean config makes it run fine seemed to indicate that the problem is not with plasma itself, but with one or more of my plugins.
|
Administrator
|
Hm, unfortunately that trace does not indicate which applet is at fault. Do you have a link to the bug report which it is duplicated against?
The only hints I can offer is that it is written in QML - and is not part of the default set of applets.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]