It has been a month since I asked how to turn off the R14 update error dialog boxes, that appear on boot up, with no response--that I recieved anyway. The post was on Sept 30th.
Since the post did appear on the list, should I take no response to mean that no one knows how?
All I really need to know is where that file is being run from, which I haven't been able to find with grep. I can figure out the rest myself.
Keith
Hi Keith,
On Sunday 01 November 2015 21:26:42 Keith Daniels wrote:
It has been a month since I asked how to turn off the R14 update error dialog boxes, that appear on boot up, with no response--that I recieved anyway. The post was on Sept 30th.
Since the post did appear on the list, should I take no response to mean that no one knows how?
All I really need to know is where that file is being run from, which I haven't been able to find with grep. I can figure out the rest myself.
Keith
There is something very odd going on with the lists at the moment. There is at least a whole week missing from "devel" and now I haven't seen a copy of the post I made to both "users" and "devel" lists.
It's had spells of being odd for a long time. <grin>
I keep getting an occasional post saying mail can not be delivered but I never could figure out why.
Keith
On Sun, Nov 1, 2015 at 4:38 PM, Baron baron@linuxmaniac.net wrote:
Hi Keith,
On Sunday 01 November 2015 21:26:42 Keith Daniels wrote:
It has been a month since I asked how to turn off the R14 update error dialog boxes, that appear on boot up, with no response--that I recieved anyway. The post was on Sept 30th.
Since the post did appear on the list, should I take no response to mean that no one knows how?
All I really need to know is where that file is being run from, which I haven't been able to find with grep. I can figure out the rest myself.
Keith
There is something very odd going on with the lists at the moment. There is at least a whole week missing from "devel" and now I haven't seen a copy of the post I made to both "users" and "devel" lists.
-- Best Regards: Baron
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Sun, 1 Nov 2015 17:15:53 -0500 Keith Daniels keithwdaniels@gmail.com wrote:
It's had spells of being odd for a long time. <grin>
I keep getting an occasional post saying mail can not be delivered but I never could figure out why.
Most of those are due to incorrect DKIM headers. Gmail (and I think also Yahoo) are pickier about those than other email providers.
E. Liddell
Good Morning Keith,
On Sunday 01 November 2015 22:15:53 Keith Daniels wrote:
It's had spells of being odd for a long time. <grin>
I keep getting an occasional post saying mail can not be delivered but I never could figure out why.
Keith
There is something very odd going on with the lists at the moment. There is at least a whole week missing from "devel" and now I haven't seen a copy of the post I made to both "users" and "devel" lists.
-- Best Regards: Baron
Yes I get one of those every few weeks :-) I just ignore them. I have a feeling that its something to do with Google mail servers. Possibly making a connection and then timing out without sending/collecting anything
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 11/02/2015 05:26 AM, Keith Daniels wrote:
It has been a month since I asked how to turn off the R14 update error dialog boxes, that appear on boot up, with no response--that I recieved anyway. The post was on Sept 30th.
Since the post did appear on the list, should I take no response to mean that no one knows how?
All I really need to know is where that file is being run from, which I haven't been able to find with grep. I can figure out the rest myself.
Keith
Hi Keith, sorry, maybe your mail was not delivered or went unnoticed (and then forgotten...). I looked that up on the ML archive and I don't recall reading the original mail.
Can you provide some more info, for example are you able to run the script, capture the output and attach it as a file? I will try to help you, although you will probably need to bear with me for a while since I am under an extra heavy workload schedule and somedays I don't even time to read my emails :-( Also, where is the r14-xdg-update-validation-test9.txt coming from? I did a quick search in the tde repo and in my user folder and this file did not come up.
Cheers Michele
On Mon, Nov 2, 2015 at 9:58 AM, Michele Calgaro michele.calgaro@yahoo.it wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 11/02/2015 05:26 AM, Keith Daniels wrote:
It has been a month since I asked how to turn off the R14 update error
dialog boxes, that appear on boot up, with
no response--that I recieved anyway. The post was on Sept 30th.
Since the post did appear on the list, should I take no response to mean
that no one knows how?
All I really need to know is where that file is being run from, which I
haven't been able to find with grep. I
can figure out the rest myself.
Keith
Hi Keith, sorry, maybe your mail was not delivered or went unnoticed (and then forgotten...). I looked that up on the ML archive and I don't recall reading the original mail.
Can you provide some more info, for example are you able to run the script, capture the output and attach it as a file? I will try to help you, although you will probably need to bear with me for a while since I am under an extra heavy workload schedule and somedays I don't even time to read my emails :-( Also, where is the r14-xdg-update-validation-test9.txt coming from? I did a quick search in the tde repo and in my user folder and this file did not come up.
Cheers Michele -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQIcBAEBCgAGBQJWN3oiAAoJECp1t8qK3tXPbg8P/32Rd33Cucl/j8Ok609mcpJz RApv2KuToDOg1iqZ35AYRQ/FI/rtG2X/pMcpWrT6lootqxJyQ0v9edVn4mklAiD/ UXRIomG6J7XRsT94f5w7+suajXM5gZJiuIAVTWwvM3IBzcasqGvwFrOHlUuqiCGY ltr8jr1ZlqmnfYm2zfwBJqwRKpHIq0EW2cBVtWdcDzlmHn7rRFns5QIhOzy7+Vsq 9C/E9Eiig0tqOX+TEa6Gz9p57chPYxcv00n1pN/v2cR0KteAONSs5HzCC6uheVNk pDm7qyRlcRX6zOGeNdOau/8OahaGogbr8HUMbbsTxXti34BQpT7NPIwy3im+knNb bkWYrJAOP593DTbPuYW8LQpyUNOqT21PUpCErZkylDbpNLSIKQ8lpe5es4N5kwOZ sZmr89U6OcWIujWr2U0Al44MF7h0BbqaLWqHcwQwjkAD+gbgdiLuWe5WIPMzeE5l wi9q/0xPyT3FpB6NIW/FYbs5faAqRt7YeYoqdoi3y3oiQgWK/6WH1I3FWpymKvTH lJ2A92aWFgphzZBWzRDZu6aU2wUpzSwOq6FoIIqQgGnx/b2TKFfHsr5LEihb8+iM Pg+j1WDRBLnCfKBjtDB9OAJsO7MjnTJs5twvjpKPzE8MEk9l1/8fpOJ/n0gnzYIE t6i5BIRbfmmKTgQeQyZ9 =h/by -----END PGP SIGNATURE-----
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
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
<snip>
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
Keith, please bear with me. I will try to look into this during the weekend, I hope (sigh...) to finish work 1 or 2 hours earlier than usual those days. BTW, if you could write down those messages as you suggested, it might be helpful. Hopefully not too much extra work for your shaky 71 year old hands ;-) Cheers Michele
-----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
Thanks Michele
I've been sick since you last wrote me.
The info you gave was what I needed.
Right before I got sick I used the info to form a theory <grin>,,, I have "massively" customized my Trinity menu. I think that was what caused the errors.
In a few days I will continue working on the problem and get back to you with the results. If I can I want to fix the problem instead of just turning off the error messages.
Thanks for your help
Keith
On Sun, Nov 8, 2015 at 8:42 AM, Michele Calgaro michele.calgaro@yahoo.it wrote:
-----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-----
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
-
Baron -
E. Liddell -
Keith Daniels -
Michele Calgaro