Bug#397073: Fwd: Bug#397073: konsole: not reading ~/.bashrc
Hi Carsten, Since you said I should forward this, I'm doing so. But I do have to wonder why you didn't mail either the bug report of Bruce Sass yourself. Kurt ---BeginMessage--- Hi Kurt, thanks for pointing out the obvious :/ The solution to the problem of not reading nor executing ~/.bashrc is that konsole is started in a way that makes it behave differently to what could have been expected by the users from experienced past behaviour, namely that konsole on start would execute the ~/.bashrc or ~/.bash_profile. The solution to the problem is actually to start konsole as a login shell, using the -ls option. After that, konsole will behave as expected. Please forward this information to the forum a/o bug report comments, so that Bruce Sass will have his way, with all the other users also waiting eagerly for a solution to the problem. Thanks in advance and keep up the good work and remedy new bugs ;-). Regards Carsten ___ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de ---End Message---
Bug#397073: Fwd: Bug#397073: konsole: not reading ~/.bashrc
And forwarding this one too... Kurt ---BeginMessage--- In reply to my previous mail I must also state that in order to make konsole execute the /etc/profile script, you will have to start konsole using the -ls option. Additionally, if you want to also customize your shell using .bashrc, you will have to add an additional script to /etc/profile.d/, for example bashrc.sh which then will start ~/.bashrc. This, however, breaks su when being used from inside konsole. Konsole will somehow return to the original shell of the original user and will not invoke a new shell running in the context of the super user root. At least under my system configuration which is more or less a vanilla fedora core 6 configuration. su will take a lot of time and, if you terminate it using ctrl-c, it will enter the super user shell process, otherwise it will terminate and will return to the original user's shell process. quite mysterious this is, as it worked for me in the past up until fedora core 5. Regards, Carsten ___ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de ---End Message---
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 [EMAIL PROTECTED] To: Carsten Klein [EMAIL PROTECTED] 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)? --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
On Mon, Nov 13, 2006 at 03:38:34PM -0700, Bruce Sass wrote:
Kurt, please have a look at:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397073
Dear Mr. Sass,
Thank you for bringing this to my attention. But I don't see why you
need to contact me for this.
The package is group maintained, and alot of other people should already
be receiving your emails. And those people probably know alot more
about this than I do.
I would also like to point out that Sune works on KDE in general, and not
on konsole in specific. KDE is rather big, and you can't know
everything.
You should also be happy that Sune does put alot of time into Debian,
reading bug reports, trying to reproduce it, making suggestions on how
you can solve your problem and so on.
As part of the NM process I will be reviewing how he deals with bug
reports. The only thing I can say is that he's working hard on
making things better.
You seem to be confused to what interactive means. Basicly the shell
is interactive if you as user can type commands in it. This has nothing
to do with wether the program (or shell script) that is started by the
shell interacts with the user or not. In case a shell is started
with the -c option, it's non-interactive since it will start the
program, and when the program exits so will the shell. You can't type
new commands in the shell after the programs exited.
Anyway, you say it used to work, but it doesn't work anymore. I can see
a few reasons for this:
- Something in konsole changed;
- Something external to konsole changed;
- The way you use it has changed;
- Something else?
In any case it would be useful if you could describe what changed
between the point it worked and the point it stopped working.
Did you do a major upgrade of Debian or KDE? Do you know from what
version to what version? Since this seems to be the latest version, I
assume you have a recent installation, and you can probably use
/var/log/dpkg.log to find the version numbers.
Or you changed window manager, as you seem to mention in a later mail?
And this might be a bug (or feature) of a different WM that you see.
So, after looking a little, I found this code in
kdelibs/kdecore/kprocess.cpp:
if (d-useShell)
{
[...]
arglist[0] = d-shell.data();
arglist[1] = (char *) -c;
arglist[2] = shellCmd.data();
arglist[3] = 0;
When I start a session, I also see a process with bash -c
my command with as child a my command.
But I have no idea how it determises to use a shell or
not, but with the case I tried it atleast seems to be
using one. In your case it's probably also using bash,
and that should be easy enough to find out.
It's already been pointed out that starting bash with
-c won't read the .bashrc, so if you want those
environment variables you'll need some other way to set them.
Anyway, I think you misunderstand how things are supposed to work,
and the documentation probably needs to be worded better to avoid
confusion. But you don't seem to be happy about that.
If none of the suggestions work for you, I suggest you
file a (wishlist) bug for the option you like to see. (Or
change this bug to the wishlist bug.)
There might also be a bug in some software, but I'm currently not
conviced this is in konsole or KDE.
With kind regards,
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
On Tuesday 14 November 2006 02:10, Bruce Sass wrote: help:/konsole/sessions.html, point 4. clearly states: Enter a command just as you normally would if you opened a new shell and were going to issue that command. However, that is not what is happening as the attached diff of GIT started from a Konsole commandline and as a KonsoleApplication shows. I think this is an unfortunate wording. It should very likely just serve as a hint, i.e. that you do not need any special syntax. The command is obviously not part of an interactive shell: I tried htop as the command. When I quit it, it also closes the session. An interactive shell would just return to the shell prompt. If anyone wants to file a bug upstream, file one for the documentation. Since there are shells with different behavior depending on interactiveness, it should explicitly mention that sessions without command are running a shell, i.e. become interactive, sessions having a command will run this command and then close, i.e. are non interactive Cheers, Kevin -- Kevin Krammer, KDE developer, xdg-utils developer KDE user support, developer mentoring pgpW8FoZSrF02.pgp Description: PGP signature
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 03:11, Sune Vuorela wrote: On Monday 13 November 2006 05:33, Bruce Sass wrote: Is it something for konsole to run _instead_ of bash? or? hmmm, ya, sure... hmm... so you expect konsole to read conffiles for bash when it is actually running another shell/program. That makes little sense to me---Konsole is a fancy x-terminal and should be doing the equivalent of bash -c someprogram with session programs. It is not konsole that reads your .bashrc, it is bash that reads it. Have another look at the output from env I sent, it contains: SHELL=/bin/bash So, ~/.bashrc should have been read, and it used to work correctly... If I remember correct, kde sources entire .kde/env/* when it boots, so if you adds a file containing #! /bin/bash if [ -e ~/.bashrc ] then .bashrc fi you will have your environment vars set in your .bashrc in entire kde. Alternatively just set the ones you like GITPAGER=foo SOMEVAR=bar and add it to a file in .kde/env/ (If you don't have .kde/env/, you can just create it) ...without polluting the environment for all of KDE, or needing to configure the same thing in multiple places. Your solution is also not good if one wanted a different environment for sh, bash, etc., where the same variable may need to take on different values. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 14:50, Sune Vuorela wrote: #first step on unversioned close: tag 397073 +wontfix thanks On Monday 13 November 2006 13:20, Bruce Sass wrote: That makes little sense to me---Konsole is a fancy x-terminal and should be doing the equivalent of bash -c someprogram with session programs. I guess that this is what konsole does - or sh -c someprogram. You seem to be doing a lot of guessing... :-/ which is why I am sending a copy to your Application Manager. Kurt, please have a look at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397073 If you read the bash manpage, it says that bash only read .bashrc when invoked interactively. Since when is a Konsole session not interactive? and this is how bash is supposed to work - so this is not a bug neither in konsole or in bash. You are wrong. ...without polluting the environment for all of KDE, or needing to configure the same thing in multiple places. Your solution is also not good if one wanted a different environment for sh, bash, etc., where the same variable may need to take on different values. if you want _konsole_ to read your .bashrc before spawning random programs, how should konsole be able to differ it you wanted a different environment or not. Konsole should not read random configuration files before invoking a program - wether the program is zsh, bash or mc or - the programs should read the configuration files it need itself. .bashrc is not some random configuration file, and a program should not be required to read a shell's profile or runtime configuration files! You can however create wrappescripts for your own cat __EOF__ ~/bin/commandwrapper #! /bin/bash if [ -e ~/.bashrc ] then . .bashrc fi /usr/bin/realcommand __EOF__ and then have your session invoking bash ~/bin/commandwrapper That is not an acceptable solution, it is a hack-around. I think you should remove the wontfix tags and get some help from a knowledgeable DD, or send it upstream. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 16:13, Sune Vuorela wrote: On Monday 13 November 2006 23:38, Bruce Sass wrote: You seem to be doing a lot of guessing... :-/ which is why I am sending a copy to your Application Manager. Thank you. You are most welcome to show my application manager that I do a hard work on the kde bugs. Or how you tackle reports about programs for which you have limited knowledge---sessions are a key feature of konsole, they get their own tab in the config dialog, yet you were unaware of them and blindly went ahead tagging the report as unreproducible. Kurt, please have a look at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397073 If you read the bash manpage, it says that bash only read .bashrc when invoked interactively. Since when is a Konsole session not interactive? bash is not interactive when not connected to a terminal. This is bash behaviour, not konsole behaviour. From the bash manpage: An interactive shell is one started without non-option arguments and without the -c option whose standard input and error are both connected to terminals (as determined by isatty(3)), or one started with the -i option. PS1 is set and $- includes i if bash is interactive, allowing a shell script or a startup file to test this state. Perhaps the underlying bug is that konsole is not properly identifying itself as a terminal. and this is how bash is supposed to work - so this is not a bug neither in konsole or in bash. You are wrong. Please point me where. Konsole should behave like any other x-terminal (which are interactive), sessions are like bash -c somecommand (you have admitted as much)... both point to .bashrc being read. .bashrc is not some random configuration file, and a program should not be required to read a shell's profile or runtime configuration files! .bashrc is just a random canfiguration file. Just try ask any zsh user. What does zsh have to do with Konsole putting SHELL=/bin/bash in the environment? I think you should remove the wontfix tags and get some help from a knowledgeable DD, or send it upstream. I actually have discussed this with several knowledgeable DDs and they agree with me. Then you should send it upstream because sessions are crippled... it should not matter if one starts a shell session then types in a command vs. uses a pre-defined session to start the command. Please stop being abusive. How have I been abusive? - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
An interactive shell is one started without non-option arguments and without the -c option whose standard input and error are both connected to terminals (as determined by isatty(3)), or one started with the -i option. PS1 is set and $- includes i if bash is interactive, allowing a shell script or a startup file to test this state. Perhaps the underlying bug is that konsole is not properly identifying itself as a terminal. The underlying bug is either that you want konsole to exec 'bash -i -c whatever' or that you expect bash to behave differently can it does. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 17:27, Clint Adams wrote: An interactive shell is one started without non-option arguments and without the -c option whose standard input and error are both connected to terminals (as determined by isatty(3)), or one started with the -i option. PS1 is set and $- includes i if bash is interactive, allowing a shell script or a startup file to test this state. Perhaps the underlying bug is that konsole is not properly identifying itself as a terminal. The underlying bug is either that you want konsole to exec 'bash -i -c whatever' or that you expect bash to behave differently can it does. That is not correct; Konsole is for interactive use so -i should not be necessary. Furthermore... help:/konsole/sessions.html, point 4. clearly states: Enter a command just as you normally would if you opened a new shell and were going to issue that command. However, that is not what is happening as the attached diff of GIT started from a Konsole commandline and as a KonsoleApplication shows. help:/konsole/menubar.html has a note which says... See the file README.linux.console in the Konsole source package for detailed information on how the Linux® console differs from a typical UNIX® console. ...and help:/konsole/introduction.html contains... Konsole is what is known as an X terminal emulator, often referred to as a terminal or a shell. It gives you the equivalent of an old-fashioned text screen on your desktop, but one which can easily share the screen with your graphical applications. ...yet there is nothing in README.linux.console which indicates such a significant departure from standard x-terminal behaviour, and the README simply states: Konsole is an X terminal emulation. Clearly, it would be a bug if bash was used on an old-fashioned text screen and it didn't read .bashrc... so why is it OK for Konsole to not make sure bash is started in a like manner? - Bruce --- env.cmdline 2006-11-13 17:43:57.691322496 -0700 +++ env.session 2006-11-13 17:43:28.446396194 -0700 @@ -1,22 +1,18 @@ -LESSOPEN=| /usr/bin/lesspipe %s KDE_FULL_SESSION=true -MINICOM=-c on GS_LIB=/home/bsass/.fonts DM_CONTROL=/var/run/xdmctl GIT_SHELL=/bin/bash LANGUAGE=en_CA:en_US:en_GB:en -KONSOLE_DCOP_SESSION=DCOPRef(konsole-28686,session-1) +KONSOLE_DCOP_SESSION=DCOPRef(konsole-28686,session-2) USER=bsass -GIT_EDITOR=jed +GIT_EDITOR=sensible-editor SSH_AGENT_PID=1821 SHLVL=1 HOME=/home/bsass XDM_MANAGED=/var/run/xdmctl/xdmctl-:0,maysd,mayfn,sched,rsvd,method=classic DESKTOP_SESSION=kde -PAGER=less GTK_RC_FILES=/etc/gtk/gtkrc:/home/bsass/.gtkrc:/home/bsass/.kde/share/config/gtkrc DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-K3fvdVLN8B,guid=673558459f7175b0e4354a51639d5400 -VISUAL=kate COLORTERM= LOGNAME=bsass _=/usr/bin/gitfm @@ -30,15 +26,11 @@ XCURSOR_THEME=Chameleon-DarkSkyBlue-Regular KONSOLE_DCOP=DCOPRef(konsole-28686,konsole) DISPLAY=:0.0 -LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.flac=01;35:*.mp3=01;35:*.mpc=01;35:*.ogg=01;35:*.wav=01;35: SSH_AUTH_SOCK=/tmp/ssh-jsYQNr1776/agent.1776 GIT_VMSTAT=free SHELL=/bin/bash -LESSCLOSE=/usr/bin/lesspipe %s %s KDE_MULTIHEAD=false -GIT_PAGER=less -PWD=/home/bsass -PRINTER=lj5n +GIT_PAGER=sensible-pager +PWD=/usr/src/kdebase-3.5.5a.dfsg.1/konsole LINES=49 GIT_RMAIL=mail -EDITOR=jed
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 17:35, Sune Vuorela wrote: On Tuesday 14 November 2006 00:55, Bruce Sass wrote: Perhaps the underlying bug is that konsole is not properly identifying itself as a terminal. Maybe. xterm behaves same way. [EMAIL PROTECTED]:~$ echo TESTVAR=brucesass .bashrc ###press alt-f2 - type env kdeenv [EMAIL PROTECTED]:~$ grep TESTVAR kdeenv ###press alt-f2 - type xterm -e env xtermenv [EMAIL PROTECTED]:~$ grep TESTVAR xtermenv [EMAIL PROTECTED]:~$ grep SHELL xtermenv SHELL=/bin/bash XTERM_SHELL=/bin/bash [EMAIL PROTECTED]:~$ so when having xterm invoke another program instead of bash also not read .bashrc - I find it correct for konsole to behave like xterm here. Good point, but I am not doing `konsole -e gitfm' and that is not how sessions are supposed to work according to the Konsole docs. ... this says that .bashrc is _not_ read when doing bash -c It turns out this is not relevent because sessions are supposed to work as if you opened a new shell and were going to issue that command. That is clearly not what is happenning (see my response to Clint's message... for that reason alone this report should be forwarded upstream so they can determine if Konsole sessions are broken or behaviour has changed and the docs need to be updated. I have been using Konsole sessions for years and the lack of behaviour I am describing is recent. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
That is not correct; Konsole is for interactive use so -i should not be necessary. Furthermore... You are misunderstanding the bash man page. The '-c' makes bash non-interactive. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 18:02, Sune Vuorela wrote: On Tuesday 14 November 2006 01:35, Sune Vuorela wrote: [EMAIL PROTECTED]:~$ echo TESTVAR=brucesass .bashrc woops. Typo here - it should have been echo export TESTVAR=brucesass shrug So, does that change the outcome? I don't see it as relevent since Konsole is an x-terminal and I'm not doing konsole -e ... which would have been the equivalent of your experiment. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 18:34, you wrote: That is not correct; Konsole is for interactive use so -i should not be necessary. Furthermore... You are misunderstanding the bash man page. The '-c' makes bash non-interactive. I understand that, it turns out I was wrong in assuming a Konsole session is like a bash -c ..., it is supposed to be like starting a shell then typing a command---which results in an interactive session. So, ya, a red herring but it doesn't change the buggy behaviour I am seeing. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
On Tuesday 14 November 2006 02:10, Bruce Sass wrote: help:/konsole/sessions.html, point 4. clearly states: Enter a command just as you normally would if you opened a new shell and were going to issue that command. Maybe this line has been thru the sales department, but I can also open new shells that don't read my .bashrc The line maybe could say Enter a command as you normally would if you opened a new shell and were to issue that command. The command will be invoked with sh -c /command/ or maybe: Enter a command as you normally would in a shell. This command will be executed instead of your shell [snip irrellevant stuff describing konsoles use as a terminal, not as a program-runner] Clearly, it would be a bug if bash was used on an old-fashioned text screen and it didn't read .bashrc... so why is it OK for Konsole to not make sure bash is started in a like manner? I have looked more into it. I cannot find any evidence that konsole actually invokes bash -c yourcommand, but instead I seem to suggest uses sh -c yourcommand (not that it changes anything in the big picture - exept /bin/sh never reads .bashrc) I would actually consider it a bug if I used a old fashioned text screen with sh and it read .bashrc [EMAIL PROTECTED]:~$ grep TESTV .bashrc export TESTVAR=brucesass [EMAIL PROTECTED]:~$ env | grep TESTV [EMAIL PROTECTED]:~$ sh $ env | grep TESTV $ /Sune -- How to open the firewall? You must get access on a laser head, so that from Excel you neither can ever disable the connection over the system to a sendmail to a space bar on the laser display, nor can debug a BIOS clock and from the control preferences menu within Photoshop NT you must save the clock and you cannot connect a level-7 TCP/IP directory of a folder on a USB front-end to load the pointer. pgp2NRG4ogprs.pgp Description: PGP signature
Bug#397073: konsole: not reading ~/.bashrc
On Mon November 13 2006 20:00, Sune Vuorela wrote: On Tuesday 14 November 2006 02:10, Bruce Sass wrote: help:/konsole/sessions.html, point 4. clearly states: Enter a command just as you normally would if you opened a new shell and were going to issue that command. Maybe this line has been thru the sales department, but I can also open new shells that don't read my .bashrc The line maybe could say Enter a command as you normally would if you opened a new shell and were to issue that command. The command will be invoked with sh -c /command/ or maybe: Enter a command as you normally would in a shell. This command will be executed instead of your shell But that is not what it says, maybe you should stop guessing and making things up. Why not take the docs for what they say, or ask upstream. I have looked more into it. I cannot find any evidence that konsole actually invokes bash -c yourcommand, but instead I seem to suggest ... Yes, bash -c ... was an error on my part, and I do have a .profile with the relevent bits just in case Konsole was lying by using sh instead of the indicated SHELL=/bin/bash... as it turns out that is not relevent to this bug. Debian's Konsole behaviour differs from both documented and past behaviour in a way that cripples the use of sessions. Either Debian's Konsole is broken, Konsole is broken, or the behaviour changed and the documentation didn't... any of those situations warrants a bug report and no amount of maybes, guesses, or attempts to remember on your part is going to change that. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
Hi, A konsole shell is fine, but session programs are not. I have a session which starts GNU Interactive Tools (apt-get install git) using the command gitfm. The output of env from within that session is... - KDE_FULL_SESSION=true GS_LIB=/home/bsass/.fonts DM_CONTROL=/var/run/xdmctl GIT_SHELL=/bin/bash LANGUAGE=en_CA:en_US:en_GB:en KONSOLE_DCOP_SESSION=DCOPRef(konsole-22261,session-3) USER=bsass GIT_EDITOR=sensible-editor SSH_AGENT_PID=1820 SHLVL=1 HOME=/home/bsass XDM_MANAGED=/var/run/xdmctl/xdmctl-:0,maysd,mayfn,sched,rsvd,method=classic DESKTOP_SESSION=kde GTK_RC_FILES=/etc/gtk/gtkrc:/home/bsass/.gtkrc:/home/bsass/.kde/share/config/gtkrc DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-r6t9xCKC71,guid=444e5045b49d499aec2c0e679a125000 COLORTERM= LOGNAME=bsass _=/usr/bin/gitfm WINDOWID=48234503 COLUMNS=88 GIT_BROWSER=sensible-browser TERM=xterm GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/bsass/.gtkrc-2.0:/home/bsass/.kde/share/config/gtkrc-2.0 SESSION_MANAGER=local/onegee:/tmp/.ICE-unix/1876 PATH=/home/bsass/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/usr/bin XCURSOR_THEME=Chameleon-DarkSkyBlue-Regular KONSOLE_DCOP=DCOPRef(konsole-22261,konsole) DISPLAY=:0.0 SSH_AUTH_SOCK=/tmp/ssh-EFGVug1775/agent.1775 GIT_VMSTAT=free SHELL=/bin/bash KDE_MULTIHEAD=false GIT_PAGER=sensible-pager PWD=/home/bsass LINES=49 GIT_RMAIL=mail Press almost any key to continue - ...but GIT_PAGER should be =less and there should be the results of eval `lesspipe` (LESSOPEN=| /usr/bin/lesspipe %s and LESSCLOSE=/usr/bin/lesspipe %s %s) in the environment. - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
hmm.. What is a session program? A program started via the Session menu, maybe I should be calling them Konsole Applications. How do I set up a session program? - start konsole - select Configure Konsole from the Settings menu - select the Session tab - put a descriptive name in the Name field - put a text mode command in the Execute field - put a path to cd to in the Directory field - choose an appropriate Icon, Schema, etc. - hit the Save Session button You'll end up with a .desktop file in ~/.kde/share/apps/konsole, e.g: --- ssh to bms.desktop --- [Desktop Entry] Cwd= Exec=ssh -X bms Font= Icon=konsole KeyTab= Name=ssh to bms Schema= Term=xterm Type=KonsoleApplication -- which shows up in the Session menu as New ssh to bms and starts a SSH login with X-forwarding on the host named bms. Is it something for konsole to run _instead_ of bash? or? hmmm, ya, sure... - Bruce -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397073: konsole: not reading ~/.bashrc
Package: konsole Version: 4:3.5.5a.dfsg.1-1 Severity: important When starting session programs ~/.bashrc is not being read, which results in some programs not operating as configured. For example... My ~/.bashrc contains: eval `lesspipe` export GIT_PAGER=less which tells gitfm to use less as its pager and less to automatically uncompress files for viewing. However, because .bashrc is not read the ^xv key command results in a may be a binary file. See it anyway? message and forces me to type (and often escape) a zless ... command. This is a minor annoyance with short filenames, but with long names it requires cutting back to one pane to see the entire name, and with very long names it requires that plus widening the Konsole window to full width and greatly reducing the font size before the entire name is visible for cut'n'pasting onto the command line... effectively rendering GIT's ^xv command useless. This is a regression from the v3.4.x behaviour (afaict), and I think it is important because it can have a major affect on the useability of programs run in Konsole. - Bruce -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-onegee Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages konsole depends on: ii kdelibs4c2a4:3.5.5a.dfsg.1-3 core libraries and binaries for al ii libc6 2.3.6.ds1-7 GNU C Library: Shared libraries ii libgcc11:4.1.1-19GCC support library ii libstdc++6 4.1.1-19 The GNU Standard C++ Library v3 ii libxrender11:0.9.1-3 X Rendering Extension client libra ii libxtst6 1:1.0.1-5 X11 Testing -- Resource extension konsole recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
