KDE 3.4

merchtemeagle · 04-24-2005, 03:59 PM

I just compiled and installed kdelibs and kdebase 3.4.0.
When I start a Konsole or xterm, my ~/.bashrc is not being read. I worked fine under KDE 3.2.
Ideas anyone?

reddazz · 04-24-2005, 05:07 PM

Try this one, it seems to work fine with kde 3.4

Code:

# .bashrc

# User specific aliases and functions

# Source global definitions
if [ -f /etc/profile ]; then
        . /etc/profile
fi

You have to have a .bash_profile thats similar to below,

Code:

# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
        . ~/.bashrc
fi

# User specific environment and startup programs

PATH=$PATH:$HOME/bin

export PATH
unset USERNAME

merchtemeagle · 04-24-2005, 05:18 PM

Quote:

Try this one, it seems to work fine with kde 3.4

code:

# .bashrc

# User specific aliases and functions

# Source global definitions
if [ -f /etc/profile ]; then
. /etc/profile
fi

You have to have a .bash_profile thats similar to below,

Shouldn't /etc/profile be loaded in ~/.profile ? (or .bash_profile)

I didn't yet try the examples you've given, but the problem seems that the shell doesn't load .bashrc . No matter what is in it.
If I put a test in it like: echo 'test' , the test is not displayed when I open Konsole.

freakyg · 04-24-2005, 06:40 PM

Quote:

Originally posted by merchtemeagle
Shouldn't /etc/profile be loaded in ~/.profile ? (or .bash_profile)

I didn't yet try the examples you've given, but the problem seems that the shell doesn't load .bashrc . No matter what is in it.
If I put a test in it like: echo 'test' , the test is not displayed when I open Konsole.

/etc/profile is for global (system wide) configuration..............

while--- ~/home/<user>/.bash_profile
~/root/.bash_profile

is for personal configuration by root or users......

here is another example...........

Code:

# ~/.bash_profile: executed by bash(1) for login shells.
# I keep this file simple and put everything in ~/.bashrc

# Sets the default permissions for files. 755 for directories and 644 for files.
umask 022

# include the configurations from ~/.bashrc 
if [ -f ~/.bashrc ]; then
    source ~/.bashrc
fi

export PATH=$PATH:/usr/X11R6/bin  
export PKG_CONFIG_PATH=/usr/X11R6/lib/pkgconfig 
export PATH=$PATH:/opt/kde/bin

reddazz · 04-24-2005, 11:48 PM

Bash reads .bash* files first before .profile, so creating a .bashrc and .bash_profile will stop bash from reading the .profile. Our .bashrc is reading global config from /etc/profile, so a .profile doesn't matter because it does a similar thing to .bash_profile. My explanation is not very good, but hopefully you get the gist of what I am trying to put across to you.

Nobber · 04-25-2005, 04:17 AM

My .bash_profile is a symlink to .bashrc, where I put all the important stuff. Also, why the need to read stuff in from /etc/profile? /etc/profile should already have exported the crucial system-wide stuff that any subshells need.

reddazz · 04-25-2005, 05:42 AM

Thats why I said my explanation is not very good. If you can put it in better terms you are welcome. Anyway to correct myself, the .bashrc in the example I gave, is just checking to see if /etc/profile exists.

bigfez · 04-27-2005, 12:01 PM

I've encountered the same problem. After upgrading to kde 3.4 konsole (bash) does not seem to source the /etc/profile or ~/.bashrc anymore. I have placed a symlink from /etc/bashrc to /etc/profile just to see if that works. I have the exact same /etc/profile ~/.bashrc ~/.bash_profile that I had before upgrade, and they work fine after being sourced. I'm just tired of typing

Code:

source /etc/profile
source ~/.bashrc

every time i open a shell.

Anyone have any ideas what's up with this?