> [tdeinit] Got EXT_EXEC 'kword' from launcher.
> 
> The Trinity ltdl loader was unable to dlopen() the shared
> library '/opt/trinity/lib/trinity/libkwordpart.so' :
> '/opt/trinity/lib/libkwordprivate.so.4: undefined
> symbol:
> _ZN7KSpell212ConfigWidget32setBackgroundCheckingButtonShownEb'
> 
> 
> The Trinity ltdl loader was unable to dlopen() the shared
> library '/opt/trinity/lib/trinity/libkwordpart.so' :
> '/opt/trinity/lib/libkwordprivate.so.4: undefined
> symbol:
> _ZN7KSpell212ConfigWidget32setBackgroundCheckingButtonShownEb'
> 
> 
> [tdeinit] Got EXT_EXEC 'kpresenter' from launcher.
> 
> The Trinity ltdl loader was unable to dlopen() the shared
> library
> '/opt/trinity/lib/trinity/libkpresenterpart.so' :
> '/opt/trinity/lib/libkpresenterprivate.so.4: undefined
> symbol:
> _ZN7KSpell212ConfigWidget32setBackgroundCheckingButtonShownEb'
> 
> 
> The Trinity ltdl loader was unable to dlopen() the shared
> library
> '/opt/trinity/lib/trinity/libkpresenterpart.so' :
> '/opt/trinity/lib/libkpresenterprivate.so.4: undefined
> symbol:
> _ZN7KSpell212ConfigWidget32setBackgroundCheckingButtonShownEb'

> Try running ldconfig against /opt/trinity/lib/trinity and then retry opening it to see if
> you still get the message.

Ok. I did that. Same error messages. I suspect kword and kpresenter are not linking correctly during my builds. As the undefined symbol message is "KSpell" for both then I'm guessing neither is linking correctly to that app.

The reason neither app starts when launched from the menu is the above failure. I don't know why, but I can launch both when I use the full path of either app and the undefined symbol messages do not appear.

Darrell