trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: November 2015

Re: [trinity-devel] R14 update error dialog boxes on boot

From: Michele Calgaro <michele.calgaro@...>
Date: Sun, 8 Nov 2015 21:42:35 +0800
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

> Re: previous email
> 
> Such is life in the fast lane... <grin>
> 
> 
> I think all of  the output of the script (error messages) is sent to this file:
> 
> /var/tmp/tdecache-$USER/r14-xdg-update-validation-test9.txt
> 
> There are three dialog boxes that sequentially popup with three different messages.  Because they are hard wired
> to prohibit copy operations (given where they appear in the boot sequence copy might not work anyway) I would have
> to write them out from reading the screen.  I can do that if you need it.  Basically they say; the update did not
> work, contact the nearest administrator, and where to find the  above mentioned error file.
> 
> The errors were all in updating *.desktop files--since I don't use those desktop files I don't care.  What I do
> care about is having to click on three different itty bitty buttons that appear in three different locations on the
> screen, one after another, with my shaky 71 year old hands...  If it keeps up much longer I am going to turn into a
> grumpy old man... <grin>
> 
> If I just knew where the script was, I could fix the popup dialog problem.  It is possible that just creating
> empty *.desktop files could solve the update problem, but the script does not tell where it expects to find the
> files--so I don't know where to put them.  My first post has lots of details about the *.desktop files that
> failed.
> 
> I attached the daily error message file, mentioned above.
> 
> Thanks
> 
> Keith
> 

Hi Keith,
the file r14-xdg-update is in /opt/trinity/bin. At lines 1067-1078 (at least on the R14.1.x version) there is a
section about "test9", which creates the mentioned 'r14-xdg-update-validation-test9.txt' file if something went wrong
when updating the tdemenu part.I guess this is a consequence of the 3 dialogs that appears during your login process.
Check the lines 849-883: probably the errors originated there (it's difficult to say from here without further
details). Even more likely it could be section 901-927.
If you need more support let us know and possibly posts more details as well.
Cheers
  Michele
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJWP1FLAAoJECp1t8qK3tXPJK4QALohKbylWd768oaYrmzR8qPg
hkvp4wyirjfGAcQcBkQjZYMEVs8AvkNtNvkO8hquzp7MlOneoi4cBOqXfZ2bFbtt
Yyq2XFUj03nm4zaUe4u+TbUHXxyqVL42/0xSbOtVElp/xYiaNrsB0kmj17egsJVP
wEjy0fCLNUJ7cnDBYKpHnR/VfbNa1sxbGMGrjtreL/a068bHQdmvkgRms0cFO8xR
P2upGTZdGACHJH5MjPzyMcnvlu9IHIzhAunp+5B3mOt2BLBN0RODfdsVZvXd8nkN
GtJ9vG4WTHmByQgJKwDVMWa7iE1orswTABZYrq5o6089xva2BOoauTHRrLAuRULH
ogN4SX3kYidclQp+GXIoVM9Pyc7hTikrfLxEyCHbB8P0e11kwZL4JztOOXLyyYNd
cMbkiBwItKUHw1fNf+VFWwTMjcX++hLIJ4InqPQOdTLWPnqoQZzV0IKAOYLHIwH/
nbkGzl/7dMOKs1AI+jNsrh6A09oSLKyhR9R8x/tNOnfLMzgipi0F5NvhwA/W4wtC
Cc7khmCb1LmwjKqbwIT6Qagqrk4LmBv2mjr9PPRqycwbcabQqyErQaY3JBxc7J9L
5tmNMSN52QVfX1jDunKylskF1LNidUyXscHJKq3z0T/BDskB7kloCRpHUMKBkrFp
2SxUox5kd+LlQV4fPzKP
=PKfa
-----END PGP SIGNATURE-----