Why!? Why did SuSE do such a nasty thing, I wonder? :-/
Well, it's inevitable that a company and dev team that's been KDE-centric for so long would make the error in terms of coding SuSE* to only interact with KDE correctly, plus, they're both so tied to KDE [did you know that when you login to GNOME on SuSE 9.3 all the KDE services are also started because the SuSE apps need them?] that it makes sense for that reason. As for hard-coding them, beats me, a simple check for a touched file in ~/.skel, which if it didn't exist adds them to ~/.gnome2/session-manual would do the job - that way people can easily remove them using the GNOME sessions GUI. Anyway, keep an eye out for a new gnome-session package, since it seems to be a hot issue at the moment, I'll try to do it on Saturday once I've got my next essay out of the way.
Therefore, my "trick" of renaming the binaries, or uninstalling them, is the "proper" thing to do.
I wouldn't say it's the proper thing to do - it mis-represents what is presently installed as far as your RPM database is concerned, but certainly for the time being it will have the desired effect, and once gnome-session is updated, you can rename them back. -- James Ogley james@usr-local-bin.org GNOME for SuSE: http://usr-local-bin.org/rpms