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


Sigrid Carrera wrote:

Hi Stephan,

On Mon, 4 Jul 2011 11:32:26 +0200
Stephan Zietsman <sziets@gmail.com> wrote:

Hi all,
I have a file (saved in the xls format) that crashes LibO 3.3.2.  It's
a fairly straightforward file, only has 4 data points and a chart.  MS
Office 2007 opens it just fine.  Could anyone comment whether they can
open this file or not?  I'm curious to find out whether the issue
causing this crash has been resolved in the 3.4.x branch (or maybe
3.3.3).  I've uploaded the file, it's available here:
http://www.2shared.com/document/3WwWglyX/Non_contiguous.html

I can open it with:
LibreOffice 3.3.2
OOO330m19 (Build:202)
Ver: 3.3.2.2-14.mga1

whereas
LibreOffice 3.3.3
OOO330m19 (Build:301)
tag libreoffice-3.3.2.2
crashes repeatedly.

Does this help you in any way?

Sigrid

Hi Stephan.

I just tried and found no problem opening the file.

I run openSUSE 11.4 64 bit with:
LibreOffice 3.3.3 
OOO330m19 (Build:301)
tag libreoffice-3.3.3.1

Best regards
Dave



-- 
Unsubscribe instructions: E-mail to users+help@global.libreoffice.org
In case of problems unsubscribing, write to postmaster@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

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.