On my 4.1 setup I had a simple bash script in Autostart which called xmodmap to load a file to load some customisations I had done to my keyboard layout (it's an Apple keyboard, so it swapped the tilde and other keys).

Autostarting the script in 4.2 doesn't work anymore unfortunately. I don't know why, because everything is still in place. Everything is like the 4.1 situation only in 4.2 it doesn't get autostarted. I believe the behaviour is consistent with other custom made scripts I want autostarted. I also have a command to autostart the freepops daemon which doesn't work, but I have to verify that.

I haven't had any problems with my Autostart scripts in 4.2, so it may be something else.

What I do in situations like this is put loads of debugging in the script and dump it to a log file, so I can look at that and work out what's going wrong.

For example:

Code: Select all

#!/bin/ksh
$log=/tmp/script.log
echo starting > $log
/path/to/some/command >> /tmp/$log 2>&1
echo $? >> $log


...might help tracking the fault.

I've noticed that sometimes it takes a minute or so for the session to completely restore and have the autorun items executed. Still trying to work out why that is the case.

My situation has changed a bit since I accidentally chowned half of my root directory to a non-root user and was unable to become root again or perform any advanced operations.

So I reinstalled Debian and KDE 4.2 and a fresh reinstall seems to have cleared the issues I had with Autostart. The xmodmap.sh is immediately triggered on startup. I noticed a delay in the startup KDE services which might be related to Zarin's issue on my old setup, but that has gone as well. My guess the problems stemmed from migrating from 4.1 to 4.2.

If something misbehaves again I'll be sure to remember the tip beermad!