trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: March 2012

Latest Build - ALL window decoration GONE / now tde won't start??

From: "David C. Rankin" <drankinatty@...>
Date: Mon, 12 Mar 2012 13:45:57 -0500
Tim,

   After rebuilding late last night, I am checking packages today. I 
reinstalled all tde packages on my test maching and started tde. I noticed 2 
things immediately:

(1) there was only a black screen displayed behind the ksplash startup screen, 
not the background set in kcontol -> Login Manager; and

(2) ALL WINDOW DECORATION IS GONE - poof - missing??

   Here is a screenshot of the tips dialog:

http://nirvana.3111skyline.com/dl/dt/trinity/ss/tde-no-decor.jpg

   I went to kcontrol -> appearance -> window decoration and all window 
decorations are listed as being available, but selecting one and hitting 
'Apply" has no effect. No window decorations appear.

   I'm not sure where to begin troubleshooting this one. No .xsession-errors 
was ever created. IIRC, this is a tdelibs issue

   However, that is SMALL POTATOES - not starttrinity - doesn't start trinity :)

   The splash screen gets to the 'hard drive icon' (Initializing system 
services) chugs away for a while and then tde commands an xserver shutdown. 
Looking at the first shutdown, there was a complaint about no xset, xsetroot, 
and xprop. Here is the screenshot:

http://nirvana.3111skyline.com/dl/dt/trinity/ss/tde-starttrinity-crash.jpg

   So I installed xorg-xset, xorg-xsetroot and xorg-xprop (funny, it ran fine 
before without them). I then tried starttrinity again, and it failed with the 
same behavior. (However, this time I did get a blue background color behind 
the ksplash dialog on statup) It got stuck on "Initializing system services" 
and then crashed:

http://nirvana.3111skyline.com/dl/dt/trinity/ss/tde-starttrinity-crash1.jpg

   The main issue I see is the dcopserver already running error - but looking 
at /home/david -- there is no .DCOPserver_tdepv__0 file. So I don't know what 
the heck is going on.

   I'm pretty much stuck on this one. Is there some change over the past few 
days that could explain this behavior?? Is it a change in ksyscoca or 
something similar causing the read of the old sysconfig cache to cause the 
crash? I tried deleting /var/tmp/kdecache-david and it did not help.

   Anybody else seeing this with last night's builds?

   How to debug and get more info??

-- 
David C. Rankin, J.D.,P.E.