| Summary: | New Tab does not read ~/.bash_profile | ||
|---|---|---|---|
| Product: | [Applications] konsole | Reporter: | Andrzej <superandrzej> |
| Component: | general | Assignee: | Konsole Developer <konsole-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | adaptee |
| Priority: | NOR | ||
| Version: | 2.5 | ||
| Target Milestone: | --- | ||
| Platform: | Slackware | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
konsole - opened with icon
konsole - new tab opened with one click konsole - new tab opened with menu-1 konsole - new tab opened with menu-2 konsole - new tab opened with button pressed=>default profile selected-1 konsole - new tab opened with button pressed=>default profile selected-2 |
||
|
Description
Andrzej
2010-09-08 01:52:11 UTC
That is because ~/.bash_profile is for login bash only, and you did not tell konsole you want a login bash. To read ~/.bash_profile, you need to edit the profile and change the command to 'bash -l'. *** This bug has been marked as a duplicate of bug 215807 *** sorry about the wrong number in previous operation. *** This bug has been marked as a duplicate of bug 54663 *** still... konsole behavior is not consistent: if you: - open konsole (with one tab) by clicking on konsole icon or - open new tab with "New Tab" button clicked once .bash_profile IS read but if you: - open konsole with "File" -> "New Tab" and then select a default profile or - open new tab with "New Tab" button pressed and then select a default profile .bash_profile IS NOT read I use .bash_profile because inside it I can source ~/.bashrc but when I tried other way around I had problems. I failed to reproduce that inconsistent behavior. I created a new profile 'Bash' which runs 'bash -l' and set it as default profile, then whenever that profile was used to create a tab/session, ~/.bash_profile was read. How was konsole initially started? I mean, what did `ps aux| grep konsole` show? And what is the version of konsole you are using at the moment? Could you pleas provide clear and sure steps to reproduce that inconsistent behavior? the konsole was started by clicking on konsole icon. (the icon was not modified by me) the output of `ps aux| grep konsole` is: andy 1427 2.0 2.1 71116 21984 ? Sl 21:40 0:00 konsole -e /bin/bash -l the version of konsole is 2.7 I don't know how else can describe steps. I will attach some screen-shoots. first 2 screen-shots represents konsole with ~/.bash_profile was read Created attachment 63490 [details]
konsole - opened with icon
Created attachment 63491 [details]
konsole - new tab opened with one click
Created attachment 63492 [details]
konsole - new tab opened with menu-1
Created attachment 63493 [details]
konsole - new tab opened with menu-2
Created attachment 63494 [details]
konsole - new tab opened with button pressed=>default profile selected-1
Created attachment 63495 [details]
konsole - new tab opened with button pressed=>default profile selected-2
Thanks for your feedback, especially the result of 'ps aux| grep konsole'. I have a clue about that inconsistent behavior. Could you show me the command specified in your *default* profile(Powłoka in the screenshot)? I guess it is NOT 'bash -l'.If that is the case, changing it to 'bash -l' should eliminate the inconsistency . The tricky thing is: sometimes, the default profile is not used to create new session. A typical example is when konsole is started in the form of 'konsole -e cmd args'. In that case, a dynamic profile is created and used as the default to create new session when user does not explictly specify the profile. See bug #211933 for another example. the command is: /bin/bash and in my case with: konsole --new-tab or ctrl-shift-t or ctrl+shift+n ~/.bash_profile was also read adding '-l' eliminates inconsistency. (In reply to comment #14) > So my guess is correct :) I think the thing is explained clear enough, so I will close it. If you think that tricky thing is a bug and should be fixed, watch bug #211933. |