You are not logged in.
Over the last couple of days my terminal prompt has been taking longer and longer to appear.
I start a terminal (urxvt or xterm, it doesn't matter which) and there is a cursor in the top right hand corner that just sits there. After 15-20 seconds, the prompt appears and then it works fine. The problem repeats if I open another instance.
I am starting urxvtd from .xinitrc. I have dialled back the bash history to 200, but the problem persists.
Anyone else seen this sort of thing? Any pointers as to where I should look?
Last edited by jasonwryan (2009-12-13 22:40:22)
Offline
Weird. What happens when you try to login to a VT? Also, does "strace bash" pause for a long time on any one call?
Offline
Same thing in a VT - marginally quicker, probably only 10-12 seconds...
strace chokes at:
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
read(0,
/edit
I've rolled back to a vanilla prompt and that has fixed the problem. I'll mark the thread solved when I work out what the problematic prompt was breaking...
Last edited by jasonwryan (2009-12-13 04:04:41)
Offline
have you tried another terminal shell ?
instead of bash try zsh or another one to check if it is bash.
maybe it's something in the ~/.bashrc
you can check the pacman.log to see if something has changed.
Last edited by quarkup (2009-12-13 16:15:21)
If people do not believe that mathematics is simple, it is only because they do not realize how complicated life is.
Simplicity is the ultimate sophistication.
Offline
I think it was something to do with the PS1 - I haven't been able to isolate the problem, but using the standard one fixed it.
I'll reintroduce bits of it at a time to see where it breaks...
Offline
Could you post the problematic PS1? It'll be interesting to see, also, enabling bash completion can slow things down some too.
/etc/rc.d/ is where daemons reside. Beware.
Offline
Sure:
PS1="┌─[\[\e[36m\]\h\[\e[0m\]][\[\e[32m\]\w\[\e[0m\]]\n└─╼ "
It has worked fine for months, but I copied and pasted it into an email for someone and I may have messed up the formatting around that first character - that's my current theory anyway...
Offline
Copied and pasted exactly as your have into my .bashrc, and have no problems. FWIW in gnome-terminal.
/etc/rc.d/ is where daemons reside. Beware.
Offline
you would just need to change temporarily your PS1 variable then
i guess you could give it a try (im not sure if you need to reboot)
probably you just need to change the PS1 variable and then source ~/.bashrc or open another shell (by executing bash or xterm)
anyway, i use this one and it is fast although it has no symbols
PS1="\[\e[1;01m\]\#)\[\e[0;00m\] \u\[\e[0;36m\]@\[\e[0;00m\]\h \[\e[1;31m\]\W\[\e[1;36m\e[0;00m\] \$ ";
If people do not believe that mathematics is simple, it is only because they do not realize how complicated life is.
Simplicity is the ultimate sophistication.
Offline
Thanks for the pointers.
@Kitty the version I posted wasn't the broken one - it was a backup.
@ quarkup I had rolled back to a vanilla PS1 - and that fixed the problem.
I'll mark it solved as it seems it was related to that first character getting munged.
Offline