Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 156694 - "su" freezes for a while in the odd situation
Summary: "su" freezes for a while in the odd situation
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: pam
Version: 3
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-05-03 13:53 UTC by SEKINE Tatsuo
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: pam-0.79-7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-05-03 14:30:32 UTC


Attachments (Terms of Use)

Description SEKINE Tatsuo 2005-05-03 13:53:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050328 Fedora/1.7.6-1.2.5

Description of problem:
When I use a terminal(e.g. xterm) on X, I have to wait about 20 seconds
after I input "su" in odd situation.

The "odd" situation means that executing su 3 times without ending each
sessions, i.e.:
  fooo@bar$ su
  (input pass)
  root@bar# su fooo
  fooo@bar$ su
  ** freeze for 20 seconds **

While the terminal was freezing, I could observe the following process via
another terminal:
  /usr/X11R6/bin/xauth -f /root/.xauthXXXXXX nlist :0.0

In the same situation without X, there is no freezing, so pam_xauth may
cause this problem. 

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. open terminal on X
2. type su by user foo
3. type su by user root
4. type su by user foo


Actual Results:  You have to wait for a while after password input.

Expected Results:  You don't need wait after that.

Additional info:

Actually, the extent of this bug is really small.


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