Bug 9311 - consolehelper/userhelper are broken
Summary: consolehelper/userhelper are broken
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: usermode   
(Show other bugs)
Version: 6.2
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-02-10 17:15 UTC by Brian Ryner
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-28 22:23:20 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Strace of gnorpm-auth session (35.78 KB, text/plain)
2000-02-10 19:05 UTC, Brian Ryner
no flags Details

Description Brian Ryner 2000-02-10 17:15:03 UTC
If I select GnoRPM from the Gnome menu (or run gnorpm-auth from a
terminal), I'm prompted for the root password; I enter it, but then gnorpm
never comes up.  gnorpm-auth does not crash, it terminates normally, just
without starting gnorpm.

Comment 1 Brian Ryner 2000-02-10 17:19:59 UTC
Changing component and description, because this also happens with other
programs that use consolehelper/userhelper, such as up2date.

Comment 2 Brian Ryner 2000-02-10 19:05:59 UTC
Created attachment 111 [details]
Strace of gnorpm-auth session

Comment 3 Nalin Dahyabhai 2000-02-10 19:54:59 UTC
I'm unable to reproduce this here with the versions from Piglet.  Which
versions of the usermode and gnorpm packages do you have installed?  What are
the contents of the /etc/security/console.apps/gnorpm-auth and
/etc/pam.d/gnorpm-auth files?  Have they been modified at all?

Comment 4 Brian Ryner 2000-02-10 21:16:59 UTC
I'm also using the piglet versions:



auth       sufficient	/lib/security/pam_rootok.so
auth       required	/lib/security/pam_pwdb.so
session    optional	/lib/security/pam_xauth.so
account    required	/lib/security/pam_permit.so



Comment 5 Brian Ryner 2000-02-10 21:23:59 UTC
Reassigning to nalin@redhat.com.

Comment 6 Jeremy Katz 2000-02-13 05:00:59 UTC
Are you trying to run the app locally or over a remote connection with an
exported DISPLAY, either via ssh or telnet?  I am able to perfectly replicate
what you describe when running something using userhelper over an ssh session
with exported DISPLAY, but it works fine when running to :0.  This behavior also
exists in Red Hat Linux 6.0

Comment 7 Brian Ryner 2000-02-13 05:01:59 UTC
Nope, this is local, DISPLAY=:0.

Comment 8 Brian Ryner 2000-02-13 19:42:59 UTC
I just found this out-- the userhelper program is exiting with error 1.  In the
manpage, it says that this means "The authentication password was incorrect",
but this doesn't make that much sense in this case.  If I enter the wrong
password, the dialog pops up again.  It's only after I enter the correct
password that it exits with this error code.

Comment 9 Brian Ryner 2000-02-13 19:58:59 UTC
Furthermore, the call which appears to be failing is:

retval = pam_open_session(pamh, 0);

at userhelper.c, line 611.

Comment 10 Brian Ryner 2000-02-15 06:17:59 UTC
Ok, I just completely rebooted and now (viola!) this works.  But I don't know
whether it should be marked WORKSFORME, considering that it was doing this
consistently for me for quite awhile.

Note You need to log in before you can comment on or make changes to this bug.