@dr-p @sotsir What about upvote?
Thanks a lot. Worked like a charm! Macbook Air early 2014, OSX 10.10.5. LO 5.2.1.2
I question why I need to do this on every new version of LibreOffice I install, but I’m very happy this works. Thanks!
Thank you very much, this works
Thanks so much. Sorry that I cannot upvote your answer, since >5 points are required.
thx ! the terminal command worked very well for a macOS 10.10.5 and LO 5.2.5
This helped me too, thanks !
Works great on OS X 10.10.5.
it works on El Capitan OS X 10.11.6 and with other applications too!!
Worked, ty (cannot upvote since I got less then 5 points, else I would) Ty again, saved my b*hind <3
It solved the issue for me after lots of frustration. Yosemite 10.10.5 with L0 6.0.2.1. Thanks a lot!
don’t have enough credits to up-vote! works on 10.10.5
Works Great on Os x Yosemite version 10.10.5
Worked for me too on OSX10.10.5. I wonder if the my problem was that I had OpenOffice running when I tried to initiate LibreOffice. When I eventually managed to open LibreOffice, I realised it was designed to pick up where OpenOffice had left off.
This trick with the terminal unfortunately didn’t work with OS 10.10.5 + LO 6.2.8. Still hung up.
This trick with the terminal unfortunately didn’t work with OS 10.10.5 + LO 6.2.8. Still hung up.
Found the work around!
Read this article, worked like a charm! http://www.italovignoli.org/2012/08/libreoffice-and-mountain-lion-macos-x-10-8/
This worked forme as well. Pleased!
Thanks a lot, it is successful. First time I got such problems with LibreOffice…
I guess you mean LO 5.1.0.3.
I had the same problem
The verification took a long time and my computer got almost completely unresponsive.
Activity Monitor indicated that kernel_task had grown to more than 6.3GB (real memory). My machine has 8GM memory. It did not take very much CPU time, but everything came virtually to a halt. Even the clock sometimes lagged minutes behind. The verification process took more than 2 hours and 15 minutes, after which I had to leave. When I returned it had finished, so I know it took less than 5 hours. Ater confirming that I wanted to run the application downloaded from the internet, LO continued, but it took at least 10 minutes before it appeared. In the meantime the kernel_task memory footprint still was high, but later it dropped back to more reasonable values.
I did this twice, with a reboot in between. The reboot didn’t solve the problem.
I also tried LO 5.0.5, and its verification took about 5 minutes (still quite long I think), with kernel_task going up to about 4GB. But at least the system continued to work normally.
So it seems there is something fishy with LO 5.1.0.3