Hide Forgot
Description of problem: When using su (usually from my normal user account to gain root), it takes a long time (about 20 seconds) to get the new prompt when working within lxterminal. Version-Release number of selected component (if applicable): coreutils-8.5-7.fc14 (x86_64) How reproducible: Consistently Steps to Reproduce: 1. Open new terminal Actual results: Expected results: Additional info:
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Confirmed that tty2-6 does not exhibit the problem, only lxterminal; editing component accordingly. Bug was submitted by form before I had finished typing: expected results were "instant prompt for new user", actual results are "20 second delay before prompt appears".
It looks like some kind of timeout and it probably has nothing to do with coreutils itself. You may try to find out on which library or system call actually su hangs with strace/ltrace ... Moving assignee to lxterminal owner anyway ...
Works fine here. Are you sure DNS resolution for localhost works correctly? Is it i /etc/hosts?
BTW: The 'technical notes' field is for changelog entries or for the update description. All comments regarding the bug itself should be added as comments.
Deleted Technical Notes Contents. Old Contents: Confirmed that tty2-6 does not exhibit the problem, only lxterminal; editing component accordingly. Bug was submitted by form before I had finished typing: expected results were "instant prompt for new user", actual results are "20 second delay before prompt appears".
/etc/hosts is as follows: 127.0.0.1 SaturnSeven localhost.localdomain localhost ::1 SaturnSeven localhost6.localdomain6 localhost6 It's correct as far as I can tell.
I think localhost should be the first one, but that doesn't really matter I guess. Can you try with another terminal, say xterm, roxterm or sakura?
xterm appears to suffer the same issue... so it appears to be a problem with terminal emulators, but not the actual ttys. Strangely, I'm getting SELinux alerts when I login on those ttys, even if the speed is better.
Have you tried the ltrace/strace I mentioned to figure out on which call is the su actually hanging? I remember this kind of reports in the past and once it was in pam, other one kernel (at least if I remember correctly)... so it could help a lot - especially if we are not able to reproduce this. Could you please also post these SELinux alerts? TIA.
Sorry for the wait; school got in the way. I logged in again on my Fedora installation and I can no longer duplicate the issue; no changes had occurred in the system in the meanwhile. I'm attaching the ltrace and strace as the system produces them now. The SELinux alert is still present.
Created attachment 486401 [details] ltrace of "su -" from lxterminal
Created attachment 486402 [details] strace of "su -" from lxterminal
Created attachment 486403 [details] SELinux alert Seems like it doesn't like /bin/login touching my home directory. At one point terminals would default the working directory to / instead of /home/mars; I'm not sure if this is related to either that or my original su - problem.
So what is the context of /home/mars? Did you try to relabel it?
Any news here?
I wound up having to lose the partition entirely due to school reasons; I never did get any further info on the SELinux thing before it occurred.
Too bad, this means we'll not find what it was. But I am convinced it was not in lxterminal as it appreaded in xterm, too.