Well, under standard user, dolphin run fine. But not as root. But saving plasma doesn't work using any user. Sometimes I need root akses for dolphin or filezilla. Dolphin run fine with root before upgrading.

I can not suggest to run a GUI FM as root, but did you simply try "kdesu dolphin"?

This is however a completely different issue, please try to keep such in different threads.

I realized an old shell script still been included in kde startup. and as been mentioned above, I can set readonly for file ~/.kde4/share/config/plasma-desktop-appletsrc . One way, I can think to way-around this problem is to load file ~/.kde4/share/config/plasma-desktop-appletsrc inside the shell script when kde startup?

At which stage of KDE startup is that script included? Is it in ~/.kde4/env/ or is it a regular Autostart script?

It is in Autostart - System Settings, script file. In there, I have no problem check or uncheck. KDE will save it properly. But, I can not remove or add new item

There's "pre-startup" and "startup" (both can -usually- be handled in "kcmshell4 autostart"), mapping to script files in ~/.kde/env and ~/.kde/Autostart respectively.

I however doubt that this will work, as iirc you said the file would be propery stored on logout, so the issue will be different.

It's however megaweird that you cannot add scripts there - what kind of filesystem is you $HOME on? Is this maybe some overlay FS (unionfs etc.) because you boot from a ro medium?

this is interesting. I boot from SCSI HD, formatted as UFS.
Your clue is interesting .
I just checked ~/.kde4/Autostart, and my script is there, but link to myhome. and I can add a new scripts in that directory . What I meant by can't add and remove item, was from KDE system settings -> startup and shutdown ->autostart user interface.
At least, I can add new item now, by adding link in directory rather than using the user interface.

But how can I load the plasma file from the sript, it might worth a try ? and the plasma-workspace in the autostart UI, is important?

UFS is the standard BSD filesystem, the "unix file system", it should not be a limiting factor.
The plasma-desktop entry is "important" in that it starts the desktop process.

You could replace it by a desktop service ("program") or script that first copies the config backup and then starts plasma-desktop.
If this works, sth. else in the login process might erase config data, but given the immutability chattr fail i doubt so.
It also still seems fishy that you're not able to add scripts via the GUI (what's the error message?) but link them by hand (so it's apparently not a permission issue?) and can see the in the kcm (so it's not a path issue either)

No Error message. If I add it from GUI, it is just gone the next time I log in. Only on and off work fines (the check marks).
How I replace it by a by a desktop service ("program") ?
How to launch it from shell scripts ? (script that first copies the config backup and then starts plasma-desktop.)
BTW, I have been using KDE for 7 days now (24 hrs on), with a lot of activities. Saving plasma seems the only problem I have after upgrading from 4.10

If I add it from GUI, it is just gone the next time I log in.

Is it present when restarting the kcm?

Code: Select all

kcmshell4 autostart
# add a script, click apply & ok etc. -> dialog closed
kcmshell4 autostart
# -> still there?


I added kcmshell4 autostart, there is no apply button, so I just close the autostart dialog box, and return to it, it is still there. Should apply button be there? looks like I am missing something
But I just logoff, and login, again... kcmshell4 is still there
But it seems, kcmshell4 does not do anything?

=)

If you run "kcmshell4 autostart" from eg. krunner or konsole, you'll get the autostart config GUI in a dialog and there should really be an apply button.

What I meant is:
can you add a script or program via the GUI, then completely close the GUI (the dialog or all systemsettings, the process shall be quit), re-open it and the added script is still there? (Until you logout and login again, of course)

In case, I suspect something is rolling back your $HOME at some point and then all efforts to copy around plasma configs and adding scripts and whatnot are pretty much pointless
You've to stop the rollback.

Yes, it is still there. Even my all applications, that I forgot to close before I log off been launched back by KDE. But my All plasma customization,such as Folder widget, my background image are gone.

I meant "before logging out", since you claimed, you could not add autostart scripts via the gui =)

But as you mentioned that even session storing apparently works and just the plasma-desktop configuration is
a) read from some default
b) even written back (unless the file is immutable)

There'll be a different issue.

Since you also assured that the config is intact after logout, it has to happen on restart.
If it happens on restart during the session, it's (hopefully) sufficient to check

Code: Select all

kauitapp plasma-desktop
ktruss plasma-desktop | grep open


This will hopefully show what files plasma-desktop reads on startup - anything that looks like a plasma config file is worth to be inspected.
a) your ~/.kde/share/config/plasma-desktop* stuf should show up in the list
b) BSD might place a pre-config for plasma-desktop somewhere else (/usr/share/config/plasma-desktop*) and it may "accidentally" have set that config immutable. See http://techbase.kde.org/KDE_System_Admi ... _Hierarchy

If it does not happen during sessions (bun only on re-login), that would pretty much rule out the immutable config idea. ktracing would also be a bit more tricky:

a) determine the plasma-desktop path:

Code: Select all

which plasma-desktop

b) add an executable ("chmod +x") "plasma-desktop" script somewhere up in the $PATH hierarchy (eg. /usr/local/bin or ~/bin - inspect "echo $PATH")

Code: Select all

#!/bin/sh
ktruss /full/path/to/real/plasma-desktop | grep open >> /tmp/plasma-desktop.ktrace


/tmp/plasma-desktop.ktrace will then hopefully hint from where the config is read.

Code: Select all

[irfan@~/scripts]$ kquitapp(3281): "Application plasma-desktop could not be found using service org.kde.plasma-desktop and path /MainApplication."
bash: syntax error near unexpected token `3281'
[irfan@~/scripts]$ which plasma-desktop
/usr/local/bin/plasma-desktop
[irfan@~/scripts]$ echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/home/irfan/bin


kquitapp can't find plasma-desktop even /usr/local/bin in the $PATH