Ooops sorry actually I hadn't seen those last 2 messages !!!

As you already know from my emails, i had already decided to downgrade to 6.12.35 (unclean way, without the uninstall...) and lost WUs in the process (but it was not a problem, and 100% my fault), and I also stopped T4T and didn't run the script after the 6.12.35 reinstall, and so far it has not crashed anymore... (except for a strange thing that happened today but was actually not a crash and boinc is still running fine now, I just sent you the logs).

But as I can read here you may have wanted me to do more testing to give you more accurate logs... on the other hand, if you confirm T4T dev are working on a "clean way" to run the VM without changing boinc permissions, it may be just worth to wait for it and don't bother to debug such a tedious bug most probably caused by this unwanted way to run boinc... (with side effect on other projects, just read here what I found out with Constellation after I stopped to run T4T).

I had mentioned the issue on the T4T forum, but it was back in the time I was beta testing it and I had more "serious" issues with T4T at the time, and I didn't completely related the current issue with T4T and didn't insist much... then I decided to give it a try here in this forum / thread.

But again, knowing it is in the todo list of T4T devs I'm pretty confident that they'll come up with a clean solution for that.

Besides I have received quite a good attention and support at both sides so I can't complain :)

So? Still stable without the T4T script?
You can also test 6.13.10 (available here), which contains a fix in the Mac installer for the creation of the projects/virtualbox/ directory.

Try running that with T4T.

---

Yep running fine and smoothly so far :)

Do you mean that the 6.13.10 allows to run a T4T WU without running their script ? so the solution is not coming from their project but from boinc ?

Do you mean that the 6.13.10 allows to run a T4T WU without running their script ? so the solution is not coming from their project but from boinc ?

No, as far as I know that script still has to be used at this time. Although you better ask at the T4T forums, I don't keep up with what they have done lately.
The fix in the Mac installer will just make sure that there is a VirtualBox directory made in, what I assume is the /Library/Application Support/BOINC Data/Projects/ directory.

---

I'm having a similar issue, as is a friend (though in both cases not with T4T):

after some period of apparently normal operations, boinc will no longer launch on startup, reporting instead a permissions error (-1202). [boinc 6.8.35; macOS 10.6]

reinstall resolves the issue temporarily, but it soon recurrs.

any suggestions?

Watch out with that advice, for as far as I can see, he is using the latest Progress Thru Processors (PtP) version of BOINC. PtP is an Intel sponsored BOINC version (the 6.8s) that is available through Facebook.

It is still being updated. PtP BOINC version 6.8.36 (which I assume Matt means he's using) was released December 20th 2011.

@Matt, I have forwarded your question to the developers. Do know that the Mac developer is still on vacation, but I do expect something back from him in due time.

---

Hi Matt,

This error indicates that a file or directory in a subdirectory under the slots or projects directory has the wrong owner. This could be caused by a project downloading or creating files incorrectly, or it could be a bug in PtP / BOINC. What projects are you running?

---