Fixing KDE paths after doing an emerge

I’ve decided to upgrade my Gentoo OS. I hadn’t done it before, because I’m using computer on a daily basis and I don’t want have computer frozen for about a day just to have KDE 3.5.5 instead of KDE 3.5.2. So I have to download and compile more than 1.3GB. It is too much for my computer to do it in a single shoot. So I decided to upgrade it within few steps (e.g. one night for X, …). Each evening, I used command (xyz is a package like xorg-server):

[code lang="bash"]
emerge -uN deep xyz; poweroff
[/code]

After one of that nights my kdm doesn’t appear after booting. Instead of it I saw an ugly xdm. Quick lookup to display 1 (Ctrl+Alt+F1) show an error:

[code]
which: no kdm in (/usr/local/bin:/usr/bin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.4.6:/opt/sun-jdk-1.4.2.12/bin:/opt/sun-jdk-1.4.2.12/jre/bin:/opt/sun-jdk-1.4.2.12/jre/javaws:/usr/qt/3/bin:/usr/games/bin)
[/code]

As I noticed there was no KDE paths in it. I guessed correctly that something with /etc/env.d/* has happened. I found on net that there should exist two files related to KDE in this directory:

• 45kdepaths-3.5
• 99kde-env

In my file system a file /etc/env.d/*kdepaths* didn’t exist. So I created it.

Content of “/etc/env.d/45kdepaths-3.5″:
[code]
PATH=/usr/kde/3.5/bin
ROOTPATH=/usr/kde/3.5/sbin:/usr/kde/3.5/bin
LDPATH=/usr/kde/3.5/lib
CONFIG_PROTECT="/usr/kde/3.5/share/config /usr/kde/3.5/env /usr/kde/3.5/shutdown"
[/code]

Than I ran:
[code]
env-update
[/code]

And after that everything work as usual.

Leave a Comment

Name:
E-mail:
URI:
Enter this code: