REPOSTING, THE PREVIOUS MAIL WAS INCOMPLETE, SORRY..

Hello,

I am happily using Trinity since a couple of years, and never had any insolvable issues with it. However, currently I am standing before a "blocker" confguration issue, and would highly appreciate some useful hint/help from the community.

This is what happens:

- I've installed a remote Centos 7 host equipped with a complete Trinity 14.0.3-1.el7.x86_64 desktop. The desktop is being accessed via Freenx and, as this machine will also be used by people with French and German keyboards, the working keyboard switcher apllet present in the 14.03 distro seems to become a really indispensable feature.

- Everyrthing seemingly works well, the desktop looks beautiful, but very soon I discovered that there is a couple off issues. In particular, I cannot start emacs on this machine, it ends up with this error: [ Undefined color: "WINDOW_FOREGROUND" ]. Atfter a bit of googling, it came out that this is a known problem, and it has to do with KDE configuration. People then stated the the issue was essentially solved by simply migrating to the updated version of KDE and no other clues were provided.

- After quite some time spent on searches, I decided to replace "dot.trinity" and "dot.tderc" with their well-customized versions taken from one of my working Centos 6 machines with Trinity 3.5.13-15.1 (which in turn, inherited them from Centos 5 with KDE 3.5.4-1). Surprise: emacs worked like a charm, and also some other issues like remote app submission not working before were gone!

- The old "dot.trinity" configuration, however, has an outdated K-menu, and it does not allow me to add the Keyboard Switcher applet. Thus I have a sort of a "blocker" situation. On one hand, I am almost done with an old "dot.trinity" and may dig in further and try to replace the K-menu under dot.trinity/share/config (this would hopefully give me a chance to add the switcher). Or I have to dig more into the issue of the brand-new install (no good ideas of where to begin, though..)

The funny thing is, there is in fact an almost-working solution. Thus it is only a TDE configuration issue: something is present, or missing, or set up in a wrong way..

Thanks a lot ahead for any there or a useful hint on how to proceed!

Andy.