When I run any terminal emulator for the first time after a reboot,
it takes a long time for Bash to come up, the window is blank for
10-20 seconds. On a quad AMD X4 with 4G RAM. Started after
updates, don't know which ones. Anyone got a suggestion, or a good
way to diagnose?
I've had a similar problem in the past: after a reboot I'd try and log
in and the prompt would hang for 10-20 seconds. It ended up being
pulseaudio. I disabled autospawn in /etc/pulse/client.conf and it
fixed the issue. You might try that?
What's in your $TERM's config file? .bashrc, .zshrc, etc. Or, more
generally, /etc/profile?
Thanks for writing :-) I have turned off autospawn in
/etc/pulse/client.conf; I don't think it changed anything. (What does
that do, anyhow? pulse still runs...)
My .bashrc is:
alias ls='ls --color=auto'
[ ! "$UID" = "0" ] && archbey -c white
[ "$UID" = "0" ] && archbey -c red
#PS1="\[\e[01;31m\]??[\[\e[01;35m\u\e[01;31m\]]??[\[\e[00;37m\]${HOSTNAME%%.*}\[\e[01;32m\]]:\w$\[\e[01;31m\]\n\[\e[01;31m\]???\[\e[01;36m\]>>\[\e[0m\]"
export PATH=$PATH:/usr/bin/core_perl
my /etc/profile is similarly basic:
# /etc/profile
#Set our umask
umask 022
# Set our default path
PATH="/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/core_perl"
export PATH
# Load profiles from /etc/profile.d
if test -d /etc/profile.d/; then
for profile in /etc/profile.d/*.sh; do
test -r "$profile" && . "$profile"
done
unset profile
fi
# Source global bash config
if test "$PS1" && test "$BASH" && test -r /etc/bash.bashrc; then
. /etc/bash.bashrc
fi
# Termcap is outdated, old, and crusty, kill it.
unset TERMCAP
# Man is much better than us at figuring this out
unset MANPATH
I do have my own script in /etc/profile.d (along with the usuals), but
all it has is:
export EDITOR=nano
export BLOCKSIZE=1G
alias yaourt='TMPDIR=/HD2/tmp ; yaourt'
--
Jonathan E. Brickman
/Ponderworthy Music/ <http://ponderworthy.com>
805 SW Jewell Ave
Topeka KS 66606-1610
jeb@xxxxxxxxxxxxxxxx <mailto:jeb@xxxxxxxxxxxxxxxx>