Version: 1.6.2 (using KDE 3.5.2, Debian Package 4:3.5.2-2+b1 (testing/unstable)) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.16-1-686 I understand that this is probably a feature but I don't see the rationale behind it. Is it to stop the user from accidentaly deleting all sessions or schemas ? I don't see the logic for it since using konqueror I can delete all my files and still the "delete" option in konqueror exists. I don't find use for most of the sessions in konsole but that is not the point that I'm making. I'd like to avoid having all of these sessions which I don't use in my session dropdown menu and have sessions that I want. To actually enable this a script feature which will be run at the start of the session should be added to the session attributes and then anyone can define whatever session he pleases. The same goes for schemas. Why cant I delete schemas ? Are they not part of my .rc file ? Are they hardcoded in konsole code ? Thanks
If you are unable to delete the session or schemas it is due to your lack of permissions to do so. Ask your system admin or if you can check the permissions on the files. You might ask on Debian mailing-list/website. % ls -l $KDEDIR/share/apps/konsole/*.schema % ls -l $KDEDIR/share/apps/konsole/*.desktop
Schemas are not hardcoded in the code, they can be found in share/apps/konsole/*.schema. If there are no sessions left, the button is greyed out.
I'm referring to #1 There is NO ACCESS to /usr/share/apps/konsole/*.schema and THERE WILL NEVER BE any. If that is the case then please do not put a "remove schema" or "add schema" buttons there because a simply rule of security in UNIX states that applications, and their shared data are owner by root while only the users home directory is owned by him. The data in $KDE/ whatever will never be user writable and any application that assumes that in any way is simply mistaken. The only directories accesible for writing for mortal users (meaning KDE users on a multi user machine) is /tmp and their home directory (and even /tmp is bad since it is shared between all users and created security problems). The schema data should be user specific and therefore reside IN THE USERS HOME DIRECTORY as preference data along with the rest of the preferences. It could be INITIALIZED from the files in /usr/share or what ever but not read or written there.