On Wed, 2014-03-05 at 13:55 -0800, edo1 wrote:
> LO 4.2.0 is showing a memory problem that's making it unusable. When I open a
> file in it, the RAM usage starts to climb until LO locks up. I get "Fatal
> Error osl:Thread:create failed."
I am sorry that you are having problems. I presume that it
On 05/03/2014 22:55, edo1 wrote:
LO 4.2.0 is showing a memory problem that's making it unusable. When I open a
file in it, the RAM usage starts to climb until LO locks up. I get "Fatal
Error osl:Thread:create failed."
After LO has pushed the RAM use to 3.9GB & frozen I must close it
completely
LO 4.2.0 is showing a memory problem that's making it unusable. When I open a
file in it, the RAM usage starts to climb until LO locks up. I get "Fatal
Error osl:Thread:create failed."
After LO has pushed the RAM use to 3.9GB & frozen I must close it
completely, i.e., kill the processes swriter.
edo1 wrote (05-03-14 19:25)
> You're quite right, the best solution would be to use the same program.
> Still, I'm curious to know if the compatibility is good enough to allow us
> to work in both LO and WORD. From your reply I gather that it's not.
For your workflow it's simple to write first wi
marcpare4 wrote
> Le 01/03/14 08:25 PM, edo1 a écrit :
>> This question has been touched upon for previous versions of LO but I'd
>> like
>> to double check for ver. 4.2.0.4 I'm using. I'm planning to do a book
>> layout, using styles, collaboratively with a distant colleague. The
>> problem
>> is
Hi Mike,
On Wed, 2014-03-05 at 11:44 +, Mike Hall wrote:
> I'm not sure whether this is the right list, but it will do for a start.
>
> I would like to understand what process is in place for handling
> security issues.
The issue should be reported to secur...@freedesktop.org this sh
I'm not sure whether this is the right list, but it will do for a start.
I would like to understand what process is in place for handling
security issues. The question has arisen because of bug 51819, a serious
security issue which was reported more than 18 months ago.
Getting that bug resolv