Re: Problem with Konsole

["Stephen P. Molnar" <s.molnar@sbcglobal.net>]

On Fri, 2013-05-03 at 10:56 +0200, "Morel Bérenger" wrote:
> Le Ven 3 mai 2013 10:20, Lisi Reisz a écrit :
> > On Friday 03 May 2013 09:16:32 Lisi Reisz wrote:
> >
> >> On Friday 03 May 2013 09:02:56 Morel Bérenger wrote:
> >>
> >>> Le Jeu 2 mai 2013 21:03, Stephen P. Molnar a écrit :
> >>>
> >>>> 64 bit Debian Testing/XFCE.
> >>>>
> >>>>
> >>>>
> >>>> When I open a console an untitled X File Window opens.  This just
> >>>> started today and I don't have a clue as to what is going on.
> >>>>
> >>>> It is rather annoying because I don't get a prompt in the console
> >>>> until I close this unwanted app.
> >>>>
> >>>>
> >>>>
> >>>> Does anyone have an idea as to what is going on here and how I can
> >>>> fix the problem?
> >>>>
> >>>> Thanks in advance.
> >>>>
> >>
> >> [snip]
> >>
> >>
> >>> I also noticed that you speak about using Konsole on XFCE.
> >>>
> >>
> >> He didn't!!  There is no mention of Konsole.  He talks about "a
> >> console". The generic term, not the KDE version of it.
> >>
> >
> > Sorry.  It is in the subject line.  I just read the post.  Mea culpa. :-(
> >  Perhaps the K in the subject line was a slip of the "tongue".
> >
> >
> > Lisi
> 
> No problem :)
> 
> And since the 'K' is not a 'k' I really think he is using the KDE's console.
> 
> 
Thanks for the replies and sorry for the confusion.  I have narrowed the
problem down to xfe. One of the xfe dependencies is libfox which seems
to be causing the problem.

I normally use Konsole, but the problem is there with any of the
consoles that I've checked.

Also, I get a .bash error when the when I close the X File Viewer.  I've
looked at .bashrc and don't see anything that seems unusual.  I've
attached the file and would appreciate more sets of eyes.

I solved the problem by removing xfe from the system, but that's a
rather draconian.  I would like to continue to use xfe, but need a
solution to the problem.

Thanks in advance.

-- 
Stephen P. Molnar, Ph.D.                Life is a fuzzy set
Foundation for Chemistry                Stochastic and multivariate
www.FoundationForChemistry.com
(614)312-7528 (c)
Skype:  smolnar1

# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
case $- in
    *i*) ;;
      *) return;;
esac

# don't put duplicate lines or lines starting with space in the history.
# See bash(1) for more options
HISTCONTROL=ignoreboth

# append to the history file, don't overwrite it
shopt -s histappend

# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# If set, the pattern "**" used in a pathname expansion context will
# match all files and zero or more directories and subdirectories.
#shopt -s globstar

# make less more friendly for non-text input files, see lesspipe(1)
#[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then
    debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
    xterm-color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
    if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
	# We have color support; assume it's compliant with Ecma-48
	# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
	# a case would tend to support setf rather than setaf.)
	color_prompt=yes
    else
	color_prompt=
    fi
fi

if [ "$color_prompt" = yes ]; then
    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
    PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt

# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
    PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
    ;;
*)
    ;;
esac

# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
    test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
    alias ls='ls --color=auto'
    #alias dir='dir --color=auto'
    #alias vdir='vdir --color=auto'

    #alias grep='grep --color=auto'
    #alias fgrep='fgrep --color=auto'
    #alias egrep='egrep --color=auto'
fi

# some more ls aliases
#alias ll='ls -l'
#alias la='ls -A'
#alias l='ls -CF'

# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
xfview
if [ -f ~/.bash_aliases ]; then
    . ~/.bash_aliases
fi

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if ! shopt -oq posix; then
  if [ -f /usr/share/bash-completion/bash_completion ]; then
    . /usr/share/bash-completion/bash_completion
  elif [ -f /etc/bash_completion ]; then
    . /etc/bash_completion
  fi
fi


alias l='ls -l --color'


if [ -e /sdb2/Apps/ecce-v6.4/apps/scripts/runtime_setup.sh ]; then
       . /sdb2/Apps/ecce-v6.4/apps/scripts/runtime_setup.sh
     fi


alias mopac='/opt/mopac/MOPAC2012.exe'


source /opt/intel/composer_xe_2013.3.163/bin/compilervars.sh intel64