From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/2.99 (3.0 rc3); Linux)
Description of problem:
When you run rhn_register as a non-root user in X nothing happens. When you run it in a
console it asks for root password in order to procede, but you cannot see this console
password prompt if you run rhn_register from a menu.
Version-Release number of selected component (if applicable):
Red Hat Skipjack Beta1
Steps to Reproduce:
1. Login as non-root user.
2. Run rhn_register from KDE or Gnome menu.
3. Application feedback but no rhn_register.
Pop-up password dialogue to enter root password.
I need more info...
what happens when you run (from X, as a non-root user)
Interesting... 3 different behaviors
(logged into KDE as non-root user)
1. Running rhn_register from KDE menu.
KDE Application startup feedback. Nothing else.
2. Running "rhn_register" from KDE console.
Console prompt "Password:". If I type root password it works.
3. Running "/usr/sbin/rhn_register" from KDE console.
Console message "warning: can't access /etc/sysconfig/rhn/rhn_register"
Pop-up "Error" window saying "You must run the RHN Registration Client as root."
okay, #2 and #3 are basically working correctly (#2 is what the
typically user sees, since they are running /usr/bin/rhn_register
which invokes consolehelper, the app that actually asks for your
#3 is running it directly, and it telling you it needs to be root.
#1 is uhmm, dunno yet...
Can you try running, from a console:
Run /usr/share/rhn/rhn_icon_helper from the KDE console. It behaves just like
#2 rhn_register asking for a "Password:" at the console then runs up2date as root.
It appears that up2date has the exact same problem as rhn_register. This is
mainly a problem if people run rhn_register or up2date from the KDE menus.
Hmm, very odd. At the moment, I'm not sure what would be
causing the problem you describe. It should just be executing
the apps as described by the .desktop files, which look
to be okay.
I'll attempt to replicate this on a beta box and see if
I can track down whats going on.
This seems to be the same issue as bug #61842, it's
a consolehelper issue.
I'm going to close this as a dup of that bug since
it's actually a consolehelper bug.
*** This bug has been marked as a duplicate of 61842 ***