(*** This bug was imported into bugs.kde.org ***)

Package:           kdevelop
Version:           2.0 (using KDE 2.2.0 )
Severity:          normal
Installed from:    SuSE
Compiler:          gcc version 2.95.2 19991024 (release)
OS:                Linux (i686) release 2.2.14
OS/Compiler notes: 

When I attempted to generate a plain c++ console project kdevelop spat out
this upon clicking create:"
shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory
can not open file "entries.82A4B88" in your local app-data-dir:
  No such file or directory at /usr/opt/kde2/share/apps/kdevelop/tools/processes.pl line 24.
shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory
can not open file "entries.82A4B88" in your local app-data-dir:
  No such file or directory at /usr/opt/kde2/share/apps/kdevelop/tools/processesend.pl line 12.
"
turned out that the scripts search for the entry file in ~/.kde/share/apps/kdevelop/ while kdevelop being a 2.2 app puts the entry file into ~/.kde2/share/apps/kdevelop/
and that effectivly stops project generation!

It might be a SuSE modification that kde2.2 is defaulting to using ~/.kde2 instead of the other directory.

ps: if I set KDEHOME=~/.kde2 all runs like a charm

I think the scripts should use the same system as kdevelop to determin where these files should go.

Im using: KDE2.2 SuSE-RPM from the ftp.kde.org binary install On an upgraded suse6.4 system

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)