From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003
Description of problem:
Under the most up2date KDE from RH8.0, one does not seem to have
the ability to launch programs with arguments at login time.
One can save a current KDE desktop environment but that is
not sufficient. Consider the konsole. KDE will preserve
the location of a konsole window, but one does not have
the ability to supply an -e command as well.
We need to launch a number of windows at login time where
the application needs additional arguments. For example:
konsole -e /usr/bin/ssh remote.host
konsole -e /usr/bin/tail --retry --follow=name \
/usr/local/bin/some-x11-app args ...
Unless I have missed something somewhere, the current KDE
bluecurve setup does not give one the ability to launch
any program with args at login time.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.try to launch a konsole with the arguments:
konsole -e /usr/bin/tail --retry --follow=name /tmp/foobar
Actual Results: KDE does not give you the ability
Expected Results: Something under Preferences will allow you to enter commands
for KDE to execute on login.
Had this ability been in place, then a work-a-round for
bug #86278 would have been possible.
One could have simply added /usr/bin/rhn-applet-gui to
the startup command list ...
I'm not sure how to open this from the GUI though.
Thanks Miloslav, for your clarification.
The issue with this enhancement request IS the GUI.
"Power users" can create files under ~/.kde/Autostart by hand, but
not by means of the GUI.
Hey, I didn't say it is not in the GUI. I just honestly
don't remember where it is because I'm not using KDE
nowadays. I'm *sure* that there was a GUI way to open this
folder at some point in the past though.
I suppose if you need to write shell scripts to be ran on login time, you can
probably open the Autostart folder too. However, i leave this on upstream
decision. Closing as UPSTREAM. (Note: for konsole, you can probably fix this
by saving sessions that have ssh as their command and open those sessions and
log out, you should get them back on login via session restoration).