trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2012

Re: [trinity-devel] Anyone building and running on X.Org server 1.12?

From: Darrell Anderson <humanreadable@...>
Date: Tue, 20 Mar 2012 15:25:57 -0700 (PDT)
> Interesting note: I can run 'konsole' and other tde apps
> from withing fluxbox,
> so the error seems to be in the initialization of the
> desktop. Here is a
> screenshot for the interested:
> 
> http://www.3111skyline.com/dl/dt/trinity/ss/konsole-in-flux.jpg
> 
> On konsole startup, I did get a couple of messages that may
> hint at the issue
> (may not as well):
> 
> [lnusertemp] Error: "/home/david/.trinity/tmp-valkyrie"
> points to "/tmp/kde-david" instead of "/tmp/tde-david".
> [tdeinit] Launched DCOPServer, pid = 761 result = 0
> [tdeinit] Launched KLauncher, pid = 765 result = 0
> [tdeinit] opened connection to :0.0
> [tdeinit] Launched KDED, pid = 766 result = 0
> [tdeinit] Got EXT_EXEC 'kbuildsycoca' from launcher.
> [kbuildsycoca] kbuildsycoca running...
> [kbuildsycoca] Reusing existing ksycoca.
> [tdeinit] PID 768 terminated.
> [tdeinit] Got EXEC_NEW 'kconf_update' from launcher.
> [tdeinit] PID 769 terminated.
> [tdeinit] PID 766 terminated.
> undecodable token: \001b(hex)[?1034h

The lnuser message is normal. You probably recently updated from GIT. The temporary storage directories had their names changed to avoid potential conflicts with KDE4. You should not see that message again.

The remaining messages all are normal except the last one. I don't think the last message is from TDE.

Darrell