Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On Fri, Jan 28, 2011 at 12:10 PM, Tom Davies <tomdavies04@yahoo.co.uk>wrote:

I think he is probably busy getting on with work and just hoping things
magically work soon.


Things often do seem to get fixed in OpenSource stuff so it's a legitimate
approach if time is frustratingly limited.  It can be annoying for people
that
want to trouble-shoot down to pinpoint the problem and fix it faster tho!

Regards from
Tom :)


Hello Tom,

Well, sort of. I went to Bugzilla, but didn't note the bug number,
because I didn't have too high hopes for an easy workaround. Sorry about
that.

A search last night indicated that it had been observed in some rc's
so maybe it is a regression and will soon be fixed. One can hope. :)

I removed LO3.3rc4 and reinstalled OOo3.2.1-11 from Debian repo, because I
had to send the file.

In my opinion LibO33 is a tremendous improvement but I do have to save to
*.doc from time to time.
I've been using OpenOffice since before it would print. I have hoped that I
would never need MSO,
and so far it has been successful in that 99.99% of the time.
I know it takes time to find the problem and fix it or develop a workaround,
especially when it seems
to only affect a few people.

Since quite a few said they had no problem, I'll try again. Maybe it was
that particular file,
but that really is not an excuse for freezing on a simple 2 page doc with
some numbering?

I run Debian Squeeze on a Pentium 4 clone with nothing out of the ordinary.
OOo3.2.1 has been the most glitch free for me. I've tried all the betas and
RCs of LibO but
have so far been unable to continue using it. My version 3.2.1 comes from
the Debian testing repository.
Granted it is based on the Go-OO version, but I understand that LibO is
also?

So no, I don't have much more to offer than that it freezes and cranks up
the CPU
when saving an *.odt to a *.doc.  I wish it didn't. I had dreamed that this
would be the
version that would work for me.

I'm going to remove OOo once again and reinstall LibO3.3 one more time on my
production desktop.
If I see an actual error message, I will visit Bugzulla again and file a
more substantial issue.
I will keep my fingers crossed,  throw salt over my shoulder, rub my lucky
rabbits foot and try once more.

Thanks for the commiseration.

regards,
Richard.


________________________________
From: Cor Nouws <oolst@nouenoff.nl>
To: users@libreoffice.org
Sent: Fri, 28 January, 2011 16:23:59
Subject: Re: [libreoffice-users] LibO3.3 hangs up when saving an *.odt as
*.doc

Luuk wrote (28-01-11 17:12)

And Richard could run into this 'special case'..... (we dont know,
because too less info)

And since he didn't answer -up until now- we basically know nothing :-)

Cor

--  - giving openoffice.org its foundation :: The Document Foundation -


-- Unsubscribe instructions: E-mail to users+help@libreoffice.org<users%2Bhelp@libreoffice.org>
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***



--
Unsubscribe instructions: E-mail to users+help@libreoffice.org<users%2Bhelp@libreoffice.org>
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***


-- 
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.