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


Hi :)
Is it possible to find a bug-report about this issue and upload the straces to 
there?  That might help  developers to see the strace.  There are few devs on 
the Users List.
Regards from
Tom :)





________________________________
From: Nuno J. Silva <nunojsilva@ist.utl.pt>
To: users@global.libreoffice.org
Sent: Sat, 2 July, 2011 11:13:02
Subject: Re: [libreoffice-users] Re: Random crashes with Libre Office Writer 
(strace included)

On 2011-07-02, Eric wrote:

Le 30/06/2011 01:44, planas wrote:

A possible work around is to save the file in odt, then open and edit
it. Then save as docx or doc. Doc files are better understood and easier
to handle. Also, doc files can be opened by the current version of MS
Word. Unless the files contain Word 2007/2010 specific features, this
could work.

Hi, that's what i did, unfortunately it doesn't prevent lowriter from 
crashing.

Here are 2 another strace logs :

1- http://dl.free.fr/b6M830KIY (crash right from the beginning)
2- http://dl.free.fr/ai9UYfNXm (random crash while i was working on the 
document)

The one that crashed in the beggining, it looks like it was loading some
UNO stuff, the other two (the second you linked now and the other you
linked in an earlier message) crash after trying to load autocorrection
data (that does not exist):

,----
| 2906  00:48:33.378073 
access("/home/rm/.libreoffice/3/user/autocorr/acor_.dat", F_OK) = -1 ENOENT (No 
such file or directory)
| 2906  00:48:33.395609 
access("/home/rm/.libreoffice/3/user/autocorr/acor_.dat", F_OK) = -1 ENOENT (No 
such file or directory)
| 2906  00:48:33.439753 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
`----

Is anyone here who can read them and understand what is the problem
(which really prevents me from working with LibreOffice) ?

Maybe more experienced people (developers?) can tell what's wrong from
the straces.

But as straces just show system calls, they don't show *exactly* where
did the problem occur (or, more correctly, where did it explode).

If you can try getting a backtrace, it'll probably be useful too. The
problem is that for a complete, human-readable backtrace you need LibO
debug packages. See:

http://wiki.documentfoundation.org/BugReport#How_to_get_backtrace_.28on_Linux.29

-- 
Nuno J. Silva (aka njsg)
gopher://sdf-eu.org/1/users/njsg

-- 
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
-- 
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.