I found that i have defined KDEDIR=/usr/kde/3.2 and KDEDIRS=/usr. All kde applications, but kopete work with this. Is kopete using the correct behaviour or is this a bug?

KDEDIR is an outdated env var from KDE 2.x, KDEDIRS is the one you should set.
Kopete itself does not use these vars directly, it's kdelibs which does.
Gong to close this bug as invalid because it's a configuration-problem.

Maybe kdelibs folks should check if we still honor KDEDIR, it might be better to remove support for that.

$KDEDIR is still (unfortunately) supported in KDE 3.x, hopefully it will be gone in KDE 4.

Anyway, this is indeed a setup problem, and I *highly* doubt other apps work correctly as the submitter claims. The reason is that it is absolutely impossible to find resources like icons, XMLGUI or plugins with incorrect KDEDIRS settings.

Depending on the app it is of course possible that old-version icons or .rc files are being picked from the old dir, but that's still asking for trouble and means any new functionality is also lost.

Please fix your setup.

Martijn

I'll fix it, but everything is working fine, kmail, knode, konqueror ... kopete can also find it's icons etc.

Subject: Re: [Kopete-devel]  Impossible to load plugin

On Sunday 09 November 2003 17:30, Heinrich Wendel wrote:
> I'll fix it, but everything is working fine, kmail, knode,
> konqueror ... kopete can also find it's icons etc.

Did you change something in $KDEDIRS after logging in to KDE or did you start 
Kopete _really_ fast after make install finished?

In that case run 'kbuildsycoca' manually and restart Kopete.

(The plugins are loaded from KDE's system configuration cache, it may have 
become outdated during your install. Logging in again should fix it as well. 
Other apps that use ksycoca should exhibit the same problem, basically any 
application that starts other apps based on the mime type and any app that 
implements plugins through KTrader.)

I just compiled kde from the gentoo packages, everything but kopete worked fine, I even restarted the computer, no change.

how did you compile it? did you unmask the beta packages from portage or did you use the cvs ebuilds?

i unmasked the beta packages

ok, i'll do the same and try it and report back.

Matt, any word on this yet? I'm having the exact same problem also using the Gentoo -beta1 packages. I'm rather frightened by how quickly the developers dismissed this.

Someone on the mailing list reported the same problem, too. http://lists.kde.org/?l=kopete-devel&m=106639742209508&w=2

yeah, i couldn't reproduce it. However, I installed to a clean directory. you might want to do "find /usr | grep kopete", see what it comes up with and paste the result here. There's more than likely stale files laying around that shouldn't be there. (That's usually what it is). 

btw, sorry for taking awhile with this, life became very busy.

I think you aren't supposed to define both KDEDIRS and KDEDIR.  Do things work better if you unset KDEDIR and set KDEDIRS to /usr/kde/3.2?

Subject: Re: [Kopete-devel]  Impossible to load plugin

On Sunday 23 November 2003 10:21, Will Stephenson wrote:
> I think you aren't supposed to define both KDEDIRS
> and KDEDIR.  Do things work better if you unset KDEDIR and set KDEDIRS to
> /usr/kde/3.2?

Won't matter actually.

Quoting from the API documentation of KStandardDirs:

   "KStandardDirs supports the following environment variables:

    * KDEDIRS: This may set an additional number of directory prefixes to
      search for resources. The directories should be separated by ':'.
      The directories are searched in the order they are specified.
    * KDEDIR: Used for backwards compatibility. As KDEDIRS but only a
      single directory may be specified. If KDEDIRS is set KDEDIR is
      ignored."

This says it all: the value of KDEDIR won't be used at all. If you want to 
search in both locations you should instead set KDEDIRS to both:

    export KDEDIRS=/usr:/usr/kde/3.2

Order is important here.

However, I doubt this would fix it. I'm more interested in the output of the 
find command that Matt mentioned.

I had the same problem and it now works for me if I set KDEDIRS to '/usr/kde/3.2'.

*** Bug 84748 has been marked as a duplicate of this bug. ***

From kstandarddirs.cpp:

    QString kdedirs = readEnvPath("KDEDIRS");
    if (!kdedirs.isEmpty())
    {
        tokenize(kdedirList, kdedirs, ":");
    }
    else
    {
        QString kdedir = readEnvPath("KDEDIR");
        if (!kdedir.isEmpty())
        {
           kdedir = KShell::tildeExpand(kdedir);
           kdedirList.append(kdedir);
        }
    }
    kdedirList.append(KDEDIR);

the "kdedirList.append(KDEDIR)" (KDEDIR is defined in kdelibs/config.h as what was passed to configure in --prefix) is what makes gentoo systems work.