Is there some documentation of exactly how KDE starts up? In particular which scripts get run and in which sequence - I'm sure it is all out there, but there is just too much information sometimes.

This looks like what you are looking for: http://docs.kde.org/stable/en/kdebase-r ... uence.html

bcooksley wrote:This looks like what you are looking for: http://docs.kde.org/stable/en/kdebase-r ... uence.html

Thatnks - that's just what I was looking for. There is such a lot to learn in KDE - is there anything like a comprehensive, technical manual/set of manuals? I used to be well into the X manuals years ago, before KDE; but a lot of new stuff must have been added since then.

There are efforts to aggregate all technical information on the TechBase Wiki http://techbase.kde.org/

Cheers,
_

janpla wrote:

bcooksley wrote:This looks like what you are looking for: http://docs.kde.org/stable/en/kdebase-r ... uence.html

Thatnks - that's just what I was looking for. There is such a lot to learn in KDE - is there anything like a comprehensive, technical manual/set of manuals? I used to be well into the X manuals years ago, before KDE; but a lot of new stuff must have been added since then.

Still, something doesn't go as expected. I am trying to install skim - it works if I put the environment settings in /etc/X11/Xsession, but then I get a message about dcopserver not being started. If i put them in ~/.xsession instead, it doesn't work, and the variables I tried to set aren't; so obviously ~/.xsession isn't the right file. Which one is it, then?

Try placing them in ~/.bashrc

OK, now skim starts up but I get the message about dcopserver:

DCOP communications error (SKIM)

Could not read network connection list.
/root/.DCOPserver_talentex__0

Please check that the "dcopserver" program is running!

Checking ps -ef shows that it is - apparently skim starts before dcopserver; where should I put the initialisation of skim, then? Or can I move the start of dcopserver somewhere before skim?

If you wish to add to KDE startup, then add your scripts in $KDEHOME/Autostart, which will start an application up upon KDE startup for your user. Please ensure to remove all other methods from ~/.bashrc, etc. before attempting again.

bcooksley wrote:If you wish to add to KDE startup, then add your scripts in $KDEHOME/Autostart, which will start an application up upon KDE startup for your user. Please ensure to remove all other methods from ~/.bashrc, etc. before attempting again.

Well, II'm not sure I wish to start things from Autostart; I tried to put a file with my environment settiings in there, but it just gets displayed in a text editor when I log on. When I found some docs for it, it looks as if Autostart simply runs whichever file is in there as if I had clicked it. What I need is to set a number of environment variables that are to be known to all KDE applications:

export XMODIFIERS=@im=SCIM
export LC_CTYPE="zh_CN.utf8"
export GTK_IM_MODULE=scim
export QT_IM_MODULE=scim

But for some reason, when it is included in eg. .profile, .bashrc or .xsession, it seems that scim (or skim) gets started before dcopserver is ready.

Try giving the file the *.sh extension, and making it executable ( "chmod +x " in Konsole )