From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126
Description of problem:
According to the man-page the --nox option should cause up2date not to attempt
to launch a graphical interface. Using this option should mean that up2date does
not need a valid DISPLAY.
[root@chalfont dan_chambers]# up2date --nox
The application 'up2date' lost its connection to the display localhost:10.0;
most likely the X server was shut down or you killed/destroyed
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Take PUTTY (a windows SSH client) and enable X tunneling.
2. SSH into a Redhat box from a windows machine that is not running X.
3. Try to start up2date in text only mode with the --nox option.
4. Get angry because you have to clear out the DISPLAY environment variable to
make it work in text mode.
Actual Results: up2date complains that it cannot find an X-server
Expected Results: Normal up2date operation... in this case grabing some RH fixes.
run /usr/sbin/up2date as root instead. What your seeing is userhelper (the
dialog that asks you for a root password) attempting to run in
X. up2date itself respects --nox, the userhelper dialog does not.
This has been fixed in later releases.
>1. Take PUTTY (a windows SSH client) and enable X tunneling.
>2. SSH into a Redhat box from a windows machine that is not running X.
Thats somewhat of a broken case. up2date itself knows how to
handle this case (even sans --nox). It will attempt to talk to
the bogus DISPLAY, and when that fails, fall back to nox mode.
userhelper, on the other hand, does not. This is fixed in 8.0.
so closing as "currentrelease"