Bug#608732: a macro in an extension i'm working at crashes libreoffice
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/20/2011 06:17 PM, Rene Engelhard wrote:
> Hi,
>
> On Sun, Mar 20, 2011 at 05:50:38PM +0200, alex bodnaru wrote:
>> first, it has presumably to do with nfs. we should probably rework the lock
>> supressing on nfs based files.
>>
>> but maybe not: the deb distributed upstream seems to work fine, however lsof
>> shows nfs based locks. so locks are being handled despite our work to avoid it.
>>
>> the deb made by you works fine, but only when nfs is not involved.
>
> Aha. Why didn't you tell this in those months? I mean, root fs parts or $HOME
> on nfs is not *that* common anymore nowdays.. Of course noone ever will try
> on that unless specifically told.
in the tests i have done the same crash happened whether $HOME was local or nfs,
and no document has been loaded.
but still, nothing happen on a machine with no nfs mounts.
and, on the other hand, the upstream 6kb soffice.bin did perform ok even when
home is on nfs, and locks (.nfs0000000abc like files) are plenty and being open
by the soffice.bin process.
by the way, the same worked ok with your ooo-3.2.*
>
>> further, i have replaced soffice.bin installed by your deb, with the one
>> distributed upstream, and now my problem dissapears.
>> there was one difference so far between the files opened with an empty writer
>> window: /usr/lib/libreoffice/basis3.3/program/libucpchelp1.so is being open by
>> the upstream binary only.
>>
>> could you have a look at any possible reasons for this difference?
>
> Probably. libreoffice-build (formerly known as ooo-build) has some patches there.
could i help having these patches in debian?
>
> Grüße/Regards,
>
> René
- --
- --
best regards,
alex
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iJwEAQECAAYFAk2GotYACgkQ2nA3WyrfyeO3MQP+PbaR3otiXjfssjPsBMnaKe9x
dpbuF8dHbo6r+FHrvK+wJy2qQPUPEYh7InFUMPrZFjkg8pvxIoJwyiCFZdssI2tL
gdSjrsTnyCuLu7J4EV72vb5udk3TsorCCryC91gI2rITUqlGaWgGtJj5FE7R6i3A
0SLpIVMhNbN8SsZ29JA=
=SMOL
-----END PGP SIGNATURE-----
Reply to: