trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2012

Re: [trinity-devel] Need help troubleshooting

From: Darrell Anderson <humanreadable@...>
Date: Wed, 7 Mar 2012 13:11:17 -0800 (PST)
> Have you looked through the CMake files?  There are a
> few places where
> CMake variables are written into TDE via autogenerated
> #defines.
> 
> Other than that the class name you are probably looking for
> is
> KStandardDirs, as it stores all search directories. 
> See
> http://trinitydesktop.org/docs/trinity/current/kdelibs/kdecore/html/classKStandardDirs.html
> for documentation.

Thanks. I've run through kstandarddirs.cpp several times. I'm running new builds now with and without the change. I'm hoping I will notice a difference in the build logs and cmake cache files.

I have two test environments, one with and one without KDE3 concurrently installed. In the one with KDE3 installed, I renamed /usr/share/share/applications/kde to kde3 and Konqueror would not display all of the setting modules. When I restored that directory name back to kde and restarted the session, Konqueror again displayed the setting modules.

Therefore something in Konqueror or the base system will use /usr/share/applications/kde despite being built to use /opt/trinity/share/applications/trinity.

As I mentioned, when I create a sym link from /opt/trinity/share/applications/trinity -> kde then Konqueror finds all of the modules.

This is true even after editing starttde and my environment to limit XDG_CONFIG_DIRS=/etc/xdg:/etc/trinity/xdg and XDG_DATA_DIRS=/opt/trinity/share and unsetting TDEDIRS. Thus I don't thinks those variables are the cause.

Is there a way I can trace opening the Konqueror settings menu?

Darrell