Bug#397073: Fwd: Re: Bug#397073: konsole: not reading ~/.bashrc
---------- Forwarded Message ----------
Subject: Re: Bug#397073: konsole: not reading ~/.bashrc
Date: Wed November 29 2006 15:56
From: Bruce Sass <bmsass@shaw.ca>
To: Carsten Klein <carstenklein@yahoo.de>
Hello,
On Wed November 29 2006 13:14, you wrote:
> Sorry for spamming you, Bruce,
You've nothing to be sorry about.
> however, I forgot to mention that if
> you start konsole using the -ls option and also using a
I don't want every konsole session to be login session; there is stuff
in my .bash_profile which is useless or inappropriate for non-login
sessions.
> profile.d/bashrc.sh script, you will have to also alias "su" as "su
> -" in order to make it work. Otherwise, su will always stall and
> return to the originally invoking shell and by that also will take a
> lot of time.
/etc/profile.d is for system wide stuff, I wouldn't want to impose my
configs on every account. I'm not sure what "su" has to do with it.
> Regards
>
> Carsten
>
> PS: the same with xterm, so it is not necessarily a malfunction of
> konsole alone, perhaps it is with the overall system configuration of
> fedora core 6?
FC6?, I'm using Debian, maybe some KDE silliness though. Xterm can't be
the same because it doesn't offer pre-defined "sessions" like konsole
does; starting konsole or xterm provides the proper environment
(.bashrc is read), starting a konsole session does not. Most of my
sessions are started via the "Terminal Sessions" menu in Kicker.
It is possible to work around the problem by defining a session to
execute "bash -i -c someprg" instead of "someprg", but that results in
an extra bash process (bash->bash->someprg instead of bash->someprg)
which is just as silly as Konsole session programs behaving differently
depending on whether KDE is started via kdm or startx, imo.
Everything works as it is supposed to when I do "startx startkde ...",
so I've disabled kdm from starting at boot and have the following in
my .bash_profile:
alias kde='startx /usr/bin/startkde -- :1 -dpi 100 &>temp/kde-log &'
Great for the local box, doesn't help when logging in to KDE via xdmcp
though.
- Bruce
p.s. - what URL did you read the report from (I'm a little surprised to
see a response from a FC user)?
-------------------------------------------------------
Reply to: