Red Hat Bugzilla – Bug 149872
term locks on tab completion of ~<dirname>
Last modified: 2007-11-30 17:11:00 EST
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Description of problem: Term locks on tab completion of ~ directories. I have tried this in bash, tcsh, and zsh. it locks every time. Version-Release number of selected component (if applicable): xterm-192-1 How reproducible: Always Steps to Reproduce: 1.open terminal window 2.type in ls ~rcar<tab> 3.it will not complete the dir name, if you hit tab again the term locks for 3-5 minutes. Actual Results: Locks terminal Expected Results: It should complete the <HOMEDIR> name of the person Additional info:
Is the directory you're doing this in within an NFS mount? Does your system use LDAP or NIS for username lookups? Does this problem happen in other directories as well, including both local and remote filesystems? Please provide an strace of both xterm and the shell you're using as gzipped file attachments.
Setting status to "NEEDINFO", awaiting response to above questions, and strace of shell and xterm leading up to the problem.
Yes the home directories are over an NFS mount. Yes our system uses LDAP for authentication No, it does not do it on other directories either local or remote. I can tab complete the home directories if I do the full directory.. for example "ls -la /people/rca<TAB> will get me /people/rcarver I have not used strace before. all I need to do is run strace xterm >filename? if not please provide more info on strace.
This is most likely an NFS issue then, and unlikely to be a bug in xterm. I strongly suspected an NFS timout issue or similar because nobody else has reported such an issue, and I'm unable to reproduce it locally. I suggest that you troubleshoot your NFS/LDAP setup, because it is most likely the cause of the problem. You can use tcpdump and strace/ltrace to troubleshoot the issue. If you require assistance, you can subscribe to the fedora-list@redhat.com mailing list and post a message about the problem. For information on using tcpdump, strace, and ltrace, please consult the manual pages and other documentation included with the OS.
Setting status to NOTABUG (configuration or local technical problem, not a bug.)