You are not logged in.

1

Monday, January 12th 2009, 3:20am

[RESOLVED] Where is plasma started?

Hi all,
while using KDE 4 (installed with kubuntu 8.19), plasma still tends to crash from time to time, especially in combination with compiz (but also without it, albeit less frequently).


As plasma is thankfully restarted automatically, I do not find the crash handler's message window very helpful or productive - on the contrary: the system I'm setting up is for (ex-windows ;o) end users, who will likely not want to know about stuff like the crash handler as long as plasma continues to run.

The problem I'm having is this: I'd like to add "--nocrashhandler" to plasma's startup, but so far I did not succeed in finding out where the plasma executable is run on KDE startup. I've already searched through the user's configuration (and rigth now a background process is grep'ing the whole system ;o) but could not find anything.
Anyone who happens to know this?
BTW, when googling this issue I came across a bug report where someone complained about plasma being restarted (after a crash) WITH "--nocrashhandler" - people, this is actually a good thing! At least for apps which restart themselves...

Now I just have to find out how to pass this parameter on first startup... and BTW, if any KDE core devs should be reading this: such info/configuration should be accessible more easily or the defaults should be more sensible (i.e. no crash handler for auto-restarting apps in the first place).

Greetings

This post has been edited 1 times, last edit by "wolfgangh" (Jan 13th 2009, 3:15am)


2

Tuesday, January 13th 2009, 1:41am

[RESOLVED] RE: Where is plasma started?

OK, I found it - it's in the systemwide autostart directory (could've sworn that I did look there... nevermind):

/usr/share/autostart/plasma.desktop

Changing the line

Exec=plasma

to

Exec=plasma --nocrashhandler

has the desired effect - plasma still crashes from time to time, but silently. A short dis- and reappearance of the panel together with a few seconds of non-responsiveness is all, afterwards erverything keeps running like before.

One more problem arose: I had the wicd network management applet in the systray. Contrary to the native applets this one (written in python) does not survive a plasma crash. The process is still running, but the icon does not reappear.
For the time being I have reverted to network-manager-kde until I've resolved this.
Anyone with similar problems?

This post has been edited 1 times, last edit by "wolfgangh" (Jan 13th 2009, 3:15am)