From Bugzilla Helper:
User-Agent: Mozilla/4.76C-CCK-MCD Netscape [en] (X11; U; SunOS 5.8 sun4u)
Description of problem:
When running up2date as a user, and the '--nox' option, it still prompts
for the root password through an X window (as opposed to something in the
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. login as a user
2. up2date --nox (--list)
Actual Results: The system realizes that you are not root and prompts you
for the root password.. but it does so in an X window even though I
specifically said no X .
Expected Results: (right in the terminal window... something like this)
up2date must run as root.
Please enter the root password: _
This probably affects all versions of up2date, not just the roswell beta. A
simple workaround is su ing to root.. but nevertheless it is still a bug.
The way I have been reproducing it is ssh ing into my machine from work,
and let me tell you how long it takes for a little X window to fly through
a ssh tunnel all the way back here :)
That GUI box is actually being displayed by consolehelper and not by
rhn_register, so not sure how much control we really have on this one. In the
case that DISPLAY is unset (or set to a text console) then we do get the TUI
prompting for root password.
We (Red Hat) should try to fix this before next release.
This will require a change in usermode. See bug #52232
er, make that bug #52532
This is SEV LOW.. and the problem appears to not be up2date at all.. I am not
sure how to re-categorize it, but it also appears there is another bug about
this already. I just BUGGED it cause I was told to on the mailing list.
Well, it's really annoying when you're coming in over SSH and it shoves GTK down
bug 53417 (in rhn_register; bug accessible by beta only) is the same issue
type "unset DISPLAY" (for bash like shell)
then it wont have a DISPLAY to push it to :p
I can also just not use the -X option with ssh. That doesn't change the fact
that if an X app pops up after I use the --nox option, then there's a bug.
Again, this is the result of a bug in consolehelper . . . so, as soon as that
issue gets resolved, this one will not be a problem.
The next version of consolehelper will fix this.
Since this is a consolehelper bug and not an up2date bug,
and the bug is fixed in current code, I'm going to close this bug.