The Modular X ebuilds do not, as yet, provide an env.d entry to set up the
environment (including LDPATH), which can cause issues when another package
provides an alternate version of the X libraries, and that package (for example
NX) provides an env.d entry with it's own LDPATH.
This causes the alternate libraries to take priority over X.Org's own libraries,
which causes symptoms such as disappearing tray icons (for aMSN) or GDK
complaining about unsupported locales.
This can be solved by simply installing an env.d file such as the one provided
by the monolithic x11 ebuilds and running env-update
Steps to Reproduce:
1. Emerge nx-x11
2. Emerge modular X (can be done before step 1 with the same results)
3. Run aMSN and try enabling the FreeDesktop tray docking
4. Run any GTK or GDK based application
aMSN refuses to enable FreeDesktop tray docking, failing silently
Running any GTK or GDK application results in a warning message at the console,
complaining about missing locales
aMSN would enable FreeDesktop tray docking
The GTK or GDK application would not print the aforementioned warning.
*** Bug 113998 has been marked as a duplicate of this bug. ***
shouldn't the nx and xorg libs just block each other then?
That would be rather convenient, yes, but it won't fly because lots of people
want to run NX on their desktops / machines with X installed.
It's not an actual installation to the same location type of conflict, it's
preference of NX's broken Xlib over Xorg's.
What we've done in the past is hack up env.d so that /usr/lib gets priority over
/usr/NX/lib or whatever. I'm not happy with it at all, but it's the best
solution I can come up with.
In response to #2, that could cause problems, as even the NX client requires the
NX X libraries.
I've thought a little, and libX11 should probably provide this environment file.
Fixed in libX11-1.0.0-r1.