KDE-Forum.org

Try removing/renaming the file
~/.kde/share/config/konsolerc

Rinse

Quoted

Original von Twiggy794

So Konsole was working fine for one minute, and then all of a sudden changing the schema doesn't do anything, my text colors have disappeared, and rather than showing the localhose@localdomain junk at the cursor, it shows bash-2.05b.

What went wrong? Anybody know how to fix this?

Hmmm.
The bash-2.05b prompt is the default, and you'll get this
if it's not set (typically in the start scripts)
by a command like
export PS1='\u@\h:\w > '

It seems to me that the start scripts don't
get executed any more or that their content
has been changed...

Did you change anything with respect to
any of these files:
/etc/profile
~/.profile
~/.bashrc
?

Quoted

Original von Twiggy794

Didn't change a thing. It was literally just night and day in a matter of seconds. I shut konsole, and when I opened it a minute or two later it was colorless and the bash thing showed up.

If you close konsole and open it "a minute or two later" then it's
a completely new one using the current configuration.
The configuration may have changed at any point while the
first konsole has been running. Changes to config files are
not picked up by a running bash. Maybe you installed
some packages or did something else that modified
the startup scripts.

Quoted

Original von Twiggy794


That export line worked but temporarily...It's a start though. Should I edit anything within those files?

Of course it's only temporary, that's why it must be
in the startup scripts so it's set every time ;-)

There's nothing I can recommend right now.
There are a few things you might want to check:

- If any of the files is truncated (zero bytes long)
ls -l /etc/profile* ~/.profile ~/.bashrc

- If any of the files contains errors. You could
open a konsole, "source" the files and watch out
for error messages:
. /etc/profile
. ~/.profile
. ~/.bashrc
(note the dot and the space in front of each file,
that's for executing them inside your current bash)

- If there have been no errors in the previous step,
did your prompt and your colors return? Again,
that would be only temporary, but it would show
that your startup scripts are ok and just don't get
executed any more...