What is the option I need to generate proper full backtrace again?

The full backtrace is provided on the Developer Information tab of the KDE Crash Assistant, which should automatically open when Plasma Desktop (or any other KDE application) crashes.

Interesting thing:
when this scripted "Konsole widget ", is not on the desktop I can

Code: Select all

kquitapp plasma-destkop
plasma-desktop&

When it is on the desktop it produces a crash when I

Code: Select all

kquitapp plasma-destkop

https://bugs.kde.org/show_bug.cgi?id=323145

It looks to me that the scripted widget is causing an exception, which in turns call in the Python garbage collection mechanism, which deletes stuff from memory that it shouldn't, causing the crash.

If your distribution has it, please install "plasmoidviewer", open a terminal, get the name of the plasmoid with "plasmoidviwer --list | grep -i konsole" then run the plasmoid in the console with "plasmoidviewer <name of the plasmoid you got earlier>". Please paste the output here and see if it crashes (it won't affect your running plasma session).

It raises a Kcrash windows when I click the cross of the plasmoidivewer windows that holds it
I updated the bug report with the backtrace and output https://bugs.kde.org/show_bug.cgi?id=323145

Code: Select all

max@inspiron:~$ plasmoidviewer KonsoleWidget
plasmoidviewer(5920)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from "/var/tmp/kdecache-max/ksycoca4"
plasmoidviewer(5920)/libplasma Plasma::Corona::Corona: !!{} STARTUP TIME 25573533 Corona ctor start
plasmoidviewer(5920)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "" not found
plasmoidviewer(5920)/libplasma Plasma::AppletPrivate::init: Check your constructor!  You probably want to be passing in a Service::Ptr  or a QVariantList with a valid storageid as arg[0].
plasmoidviewer(5920)/libplasma Plasma::PluginLoader::loadApplet: we have a script using the "python" API
plasmoidviewer(5920)/python (plugin) KPythonPluginFactory::KPythonPluginFactory: KPythonPluginFactory::KPythonPluginFactory()
plasmoidviewer(5920)/python (plugin) KPythonPluginFactory::initialize: Initializing Python interpreter.
plasmoidviewer(5920)/python (plugin) KPythonPluginFactory::initialize: Succesfully initialized Python interpreter.
plasmoidviewer(5920)/python (plugin) KPythonPluginFactory::create: KPythonPluginFactory::create iface:  Plasma::AppletScript
plasmoidviewer(5920)/python (plugin) KPythonPluginFactory::create: keyword to be used for finding the plugin code:  "plasma_scriptengine_python/pyappletscript.py"
plasmoidviewer(5920)/python (plugin) KPythonPluginFactory::create: Path to plugin code is:  "/usr/share/kde4/apps/plasma_scriptengine_python/pyappletscript.py"
plasmoidviewer(5920)/python (plugin) KPythonPluginFactory::create: Returning result qobject
plasmoidviewer(5920)/libplasma Plasma::AppletPrivate::setupScriptSupport: setting up script support, package is in "/home/max/.kde/share/apps/plasma/plasmoids/KonsoleWidget/" which is a "Plasmoid" package , main script is "/home/max/.kde/share/apps/plasma/plasmoids/KonsoleWidget/contents/code/main.py"
plasmoidviewer(5920)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "" not found
plasmoidviewer(5920)/libplasma Plasma::AppletPrivate::init: Check your constructor!  You probably want to be passing in a Service::Ptr  or a QVariantList with a valid storageid as arg[0].
0 Test
0 plasmoidviewer(5920)/kdecore (KLibrary) findLibraryInternal: plugins should not have a 'lib' prefix: "libkonsolepart.so"
0 plasmoidviewer(5920)/konsole Konsole::Session::run: Attempted to re-run an already running session.
0 plasmoidviewer(5920)/kparts KParts::Part::slotWidgetDestroyed: deleting part ""
KCrash: Application 'plasmoidviewer' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/max/.kde/socket-inspiron/kdeinit4__0


This is definitely a Python related crash. Unfortunately there is not much you can do here to fix it other than remove the applet from Plasma Desktop i'm afraid.

Right but that does not explain why, when I create a new user I can not login with it.
Or is it unrelated?

Sorry, didn't see that being mentioned before. Please provide the contents of ~/.xsession-errors from a user which cannot login.

There is now such file in my case

Code: Select all

max@inspiron:/home/invite$ ll
insgesamt 28
drwxr-xr-x 3 invite invite 4096 Aug 23 16:14 ./
drwxr-xr-x 9 root   root   4096 Aug 22 22:07 ../
-rw-r--r-- 1 invite invite  220 Mai 18  2011 .bash_logout
-rw-r--r-- 1 invite invite 3486 Apr  3  2012 .bashrc
drwx------ 2 invite invite 4096 Aug 23 16:14 .cache/
-rw-r--r-- 1 invite invite   27 Aug 22 22:08 .dmrc
-rw-r--r-- 1 invite invite  675 Mai 18  2011 .profile


Unusual, I was pretty sure Kubuntu had that file as well. It seems that the user in question has very little in terms of configuration, not even a ~/.kde* so it is likely KDE startup isn't even commencing.

Are you able to use a failsafe option to get it to start a basic XTerm at the bare minimum?