I first emerged my system, including KDE, with a "x86" keyword. Then, I changed to ~x86 keywords, and after updating baselayout, new konsole shells don't read /etc/profile when starting up (instead of "c500 pete$" I see "bash-2.05b$". Please tell if you need more details or informations, I feel the infos are pretty thin but don't know what else to add.
This is a problem with the init scripts, NOT with kde. I have the problem on one computer too. Basically at the moment that startkde gets called profile should allready have been run. It has not. I don't know what is the problem. I'll try to find out later today (I'm at work and it is my home computer).
For me, a newer baselayout seems to work. As an aside, you can change the konsole link to call "konsole --ls" to have it start with a login shell.
You need to run konsole as a login shell if you want it to source /etc/profile. Not my problem, as not baselayout related.
No there is/was a problem that profile was not sourced anywhere. The new baselayout seems to fix it though.
New baselayout seems to fix it, according to above comments.
Hmm, this is actually a biger problem than just that. When starting up an xterm, the same problem occurs. Haven't tested aterm or any of the other terms but I suspect that somewhere along the line something has changed in the last 2 months that causes this problem. Also, It happens in both icewm and kde, so as far as I can determine the only common between all these is the startup scripts and kdm (which I do use). I'm currently compiling gdm to see whether the problem persists. All this work as expected on the two machines in the office, but it doesn't work on my machine, nor my co-workers's machine at home (which was both installed in the last month). My machine in the office was installed end of August/beginning of September - and it works correctly. btw, gdm has the same problem. The question now becomes, what has changed? What is common between all these? As for common, the only thing I can see that is deffinately common is bash. I have no idea what has changed. I'm running stable on an pentium3. Could someone with the required access please reopen this bug as it is deffinately not resolved yet.
