[SOLVED] Konsole does not close when pressing Crtl+D / defunct bash ?

Question

Dear all,
Since a few days, when I type exit or Crtl+D in a KDE konsole to close the bash session, konsole often does not close itself anymore automatically. I tried to close it manually using the GUI (File>Close tab), but then I have the following message:
The program '/usr/bin/bash' is in this session would not die. Are you sure you want to kill it by force?
It seems bash is the culprit since ps reveals many [bash] <defunct> lines, probably one for each frozen konsole:
XXXXXX 2002 0.0 0.0 0 0 ? Zs Nov26 0:00 [bash] <defunct>
XXXXXX 2220 0.0 0.0 0 0 ? Zs Nov26 0:00 [bash] <defunct>
XXXXXX 2841 0.0 0.0 0 0 ? Zs Nov26 0:00 [bash] <defunct>
XXXXXX 2874 0.0 0.0 0 0 ? Zs Nov26 0:00 [bash] <defunct>
XXXXXX 3525 0.0 0.0 0 0 ? Zs Nov27 0:00 [bash] <defunct>
XXXXXX 3704 0.0 0.0 0 0 ? Zs Nov27 0:00 [bash] <defunct>
XXXXXX 3719 0.0 0.0 0 0 ? Zs Nov27 0:00 [bash] <defunct>
XXXXXX 3827 0.0 0.0 0 0 ? Zs Nov27 0:00 [bash] <defunct>
XXXXXX 4365 0.0 0.0 0 0 ? Zs Nov27 0:00 [bash] <defunct>
XXXXXX 4462 0.0 0.0 0 0 ? Zs Nov27 0:00 [bash] <defunct>
XXXXXX 4475 0.0 0.0 0 0 ? Zs Nov27 0:00 [bash] <defunct>
XXXXXX 4559 0.0 0.0 0 0 ? Zs Nov27 0:00 [bash] <defunct>
Any idea of what could be causing this problem?
Thanks a lot!
Aurel.
Last edited by aurelieng (2013-11-29 08:11:06)

Answer 1

my .bashrc:
#!/usr/bin/bash
export LANG=en_US.UTF-8
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
if [ -f /etc/bash.bashrc ]; then
. /etc/bash.bashrc
fi
# Environment variables
if [ -f ${HOME}/.environment ];
then
source ${HOME}/.environment
fi
# Path
if [ -f ${HOME}/.path ];
then
unset TMPPATH;
for i in `grep -v "^#" ${HOME}/.path `;
do
TMPPATH=$TMPPATH:$i;
done
export PATH=$TMPPATH:$PATH
fi
# Alias
if [ -f ${HOME}/.alias ];
then
source ${HOME}/.alias
fi
ulimit -s unlimited
# Turn off system bell
setterm -blength 0
#xset -b
You can notice i use 3 external files: one containing the paths I want to add to $PATH, one for aliases, and a third one for environment variables. The bash session is initialized as expected, hence I don't think it's worth posting them. Moreover, the fact the bash can't be killed and remains a zombie make me think it might not be related to config files.
My .bash_profile:
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH
unset USERNAME
# Lines added by tex4moz on: Mon May 12 14:12:58 CEST 2003
PATH=$PATH:/home/XXXXXXXX/temp/tex4ht.dir ; export PATH
TEXINPUTS=$TEXINPUTS:/home/XXXXXXXX/temp/tex4ht.dir ; export TEXINPUTS
Last edited by aurelieng (2013-11-28 06:16:27)