Issue 111685

Created attachment 69519 [details]
This file, with four sheets, loads and runs

Created attachment 69520 [details]
This file with five sheets crashes Calc before loading, consistently on both computers.

the file doesn't crash my OOo 3.2.1rc1 (tested on Solaris x86)

I am not surprised that it worked on Solaris. You will observe that I said that
it worked on Windows. The issue is that it does not work on two very different
computers, both with Ubuntu 10.04.

this worksforme with the Debian version of OpenOffice.org 3.2.1 RC1.

You use the Ubuntu version of OpenOffice.org?

@ ccheney please have a look

Yes, as bundled with Ubuntu 10.04 discs.

Works for me on Ubuntu 10.04 with openoffice.org 1:3.2.0-7ubuntu4 on amd64 (64bit).

so set to worksforme

-> closed

Sorry, still does not work for me on freshly installed, not upgraded, Ubuntu
10.04LTS -i386, updated.

Nobody can reproduce thei probllem here so nobody can get an idea what is wrong an can be fixed

I reassign 

Maybe more people can have a look to reproduce it. But I doubt someone can reproduce it

I cannot reproduce it with go-oo 3.2.0 or 3.2.1 too.
Closing it as invalid once again.

As nobody here is able to reproduce, can you please try to create a backtrace 
of the crash for us?  Please see these instructions:

http://en.opensuse.org/Bugs:OOo#How_to_get_backtrace

They are for openSUSE, but should work very similarly for Ubuntu too.

I have copied the uploaded files to the same location on my server as the
original and I agree that the files attached to this Issue do run correctly,
however, the original file still crashes. Can anyone explain why the same file,
uploaded, runs o.k. whilst the original does not? Is it possible that something
in the file has been modified by the process of uploading, so that it is now
recognised by OOo?

You can use md5sum to check that the files are identical.  Either way, without 
the failing document & the backtrace, we cannot help much :-(

Thank you Kendy for your suggestions. md5sum is identical for both files, so
that seems to rule out file changes.

I have also installed OOo 3.2.1.rc1 and get the same result of failure to load
the original file, but the uploaded/downloaded file is o.k.

I have downloaded the openoffice.org-calc-debuginfo rpm file from opensuse, but
cannot convert it to deb. The log of alien is attached.

Does anyone know of a debug that would work with Ubuntu (deb)?

Created attachment 69556 [details]
Log of attempt to convert OpenOffice_org-calc-debuginfo-3.1.1.4-1.1.4.x86_64.rpm to deb

maxcel: That won't work; you'd have to install the appropriate debuginfo from
your distro.  Please try to do the backtrace without the debuginfo packges.

One thing totally confuses me - you say that the files are identical.  What do
you mean then that 'the downloaded does not work, and the orignal does'?  What
are the exact locations of those files?  Also strace might be useful here, see
http://en.opensuse.org/Bugs:OOo#How_to_get_strace_log (and actually easier than
getting the backtrace).

Created attachment 69560 [details]
Strace of failed load of the original copy of Test-OOo3.2-5sheet.ods

maxcel,

Unfortunately the Ubuntu 10.04 debug debs for 3.2.0 got lost somehow, but once I
do an upload of 3.2.1 for 10.04.1 in a few weeks those should be available.

After a lot more testing, it looks as if this is a network related problem,
possibly timing.

All my files are stored on a NAS file server.

Working exclusively with OOo3.2.0 and OOo3.2.1.rc1. When .ods spreadsheets are
called up directly from the server, they invariably crash. If the same files are
copied to the local drive, or a USB stick, they run properly. If they are
modified and saved back to the local drive they will load again properly, but if
they are saved back to the NAS, they will again crash on loading. This behavior
is consistent and repeatable over many different files.

A clue here is that the crash happens very soon after the splash screen and
before OOo displays the normal working screen.

I have used the built-in bug reporting feature on OOo3.2.1.rc1 to log the
crashes which are occurring on that version.

Just a reminder that this behavior only started with OOo3.2.0. I still have some
computers with OOo3.1 and earlier and can confirm that the crashes do not happen
with them.

The same problem is occurring with OOo-3.2.1.rc1-Writer when trying to open
files stored on the NAS, so this problem isn't confined to Calc.

The crash on NAS is a known issue, which is apparently related to locking. If
you use nobrl for the cifs mount it should work. I have updated ooo-build to not
use locking for cifs mounts and will be adding the patch to Ubuntu 10.04.1
openoffice.org build.

There are 11 other cifs bugs in the issue tracker at the moment, and I wouldn't
be surprised if they are all related to the locking issue.

Adding nobrl to the cifs mount has solved the problem. Many thanks to all who
have helped, especially ccheney. I am happy to close this issue now.

-> closed

Am I wrong here or isn't the fact that you have to turn on 'nobrl' to make OOo
work with cifs still a bug in OOo.

What 'nobrl' does is the following:

nobrl
    Do not send byte range lock requests to the server. This is
    necessary for certain applications that break with cifs style
    mandatory byte range locks (and most cifs servers do not yet
    support requesting advisory byte range locks).

This is now worked around by ooo-build but as far as I know this wouldn't this
still affect the official version?

ccheney: Can you please attach here the patch?

kendy,

My patch would not apply cleanly to official OOo 3.2 as it simply extends the
check to see if it is on smb or nfs and to disable locking entirely. I'm not
sure who originally wrote the patch but perhaps they can contribute it back to
upstream? I hereby authorize my simple addition of 'cifs' to the patch to be
contributed upstream. :-)

Its in ooo-build's version of:

/usr/lib/openoffice/program/soffice

And that really that is more of a workaround for OOo's broken locking handling
at least from what I understand of 'nobrl' being able to fix the situation.

@kendy, I think Chris' question was for us. :)

.

worksforme in OOO330 go-oo bug only

don't know how to change the status