Bug 190001 - bad bash command in default profile - trivial to fix
Summary: bad bash command in default profile - trivial to fix
Status: RESOLVED DUPLICATE of bug 54663
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.2.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-18 22:18 UTC by Zbigniew Luszpinski
Modified: 2009-04-19 18:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Zbigniew Luszpinski 2009-04-18 22:18:51 UTC
Version:           2.2.2 (using 4.2.2 (KDE 4.2.2), compiled sources)
Compiler:          gcc
OS:                Linux (i686) release 2.6.28.8

Settings->Edit Current Profile->General tab->Command:
Please change:
/bin/bash
to
/bin/bash -ls

Why:
By default konsole in kde3 or kde4 uses bash in wrong way by just executing /bin/bash. Executing bash this way does not initialize user account settings. This is bad because every user has its own personal settings for bash or they are set by administrator. If you change /bin/bash to /bin/bash -ls in "Command:" field the konsole will be initialized correctly and per user account settings will be used. I use this fix in kde3 and kde4.
Comment 1 Robert Knight 2009-04-19 18:37:13 UTC
> Executing bash this way does not initialize user account setting

What do you mean by 'user account setting'?  On startup bash reads the script ~/.bashrc and if the -l option is passed to bash it will also read ~/.bash_profile.  Which settings go in which file depends on who set up your system.  With Ubuntu, a set of default settings to make bash usable are put in ~/.bashrc and there is no ~/.bash_profile.  I presume your setup is different.

What are you adding the -s option for, that doesn't seem to be related?

If you are a sysadmin and you want to change Konsole's default settings for many users, please see #163750

*** This bug has been marked as a duplicate of bug 54663 ***