Dear Dev Team,
since I have upgraded LibreOffice to:
I expirience constant crashes especially using impress.
Sometimes the application crashes while editing a slide, sometimes is dies simply running in the back.
The version before was much more stable,
I am using Libre Office on MacOS 10.7
Let me know if I can run some tests for you or please tell me how to produce debug information.
I hope the next release will be more stable, again and available soon.
Can you help?
Thank you very much for your bug report!
I'm very sorry that LibreOffice 3.5.4 causes so much pain to you. It's a pity but it is not easy to help, because the situation is difficult: on many MacOS computers, LibreOffice 3.5.4 runs fine (e.g. on my own ;-), so we have to find out what makes the difference -- why does it crash for you so often (and not, e.g., for me).
To find out about the difference I have some questions for you. It would be very helpful if you could answer to them.
1) The first question is near to completely answered: you use LibreOffice on MacOS X 10.7 (I use MacOS X 10.6.8, and this may make a difference -- we will see). Which user interface languages do you use for MacOS and LibreOffice -- I suppose, German in both cases?
2) You say that you experience constant crashes "since I have upgraded LibreOffice" to version 3.5.4. This seems to indicate that you have used LibreOffice before without crashes, and is very interesting for us. Which version did you use before you upgraded to LibreOffice 3.5.4? Did it run without crashes (at least, without so many crahes) at the same tasks which cause a crash now?
3) An important point: Do you have any accessibility utilities enabled? This is to say, have you enabled any of the options in the section "Universal Access" (German "Bedienungshilfen" of the MacOS X System Prefererences? E.g., "VoiceOver" or "Zoom" or "Zugriff für Hilfsgeräte aktivieren"? Or do you have installed any other special utilities like a screenreader for people with visual impairment (Sehbehinderung), or some window management application like "Moom", or anything similar? This point is important because many accessibility utilities are known to cause crashes with LibreOffice ...
4) Do you have any special extensions for LibreOffice installed? If you are not sure, please select "Tools > Extensions Manager ..." (in German: "Extras > Extensions Manager ..." from the menu bar in LibreOffice 3.5.4. In the window which appears now please UNcheck (deselect) the checkbox "Installation" at the bottom, but make sure that both "Shared" ("Gemeinsam") and "User" ("Nutzer") are checked. Is the list above the checkboxes now empty (then there are no special extensions installed), or does it contain some entries? If the latter, please report all extensions which are listed there now.
5) Does Impress crash even when you create a new (empty) presentation and just begin to edit it? Or does it crash (more often) with existing presentations which contain quite some text and images?
6) Could you please attach any Impress file (presentation) which causes crashes to you to this bug report, and describe some typical actions with this file that often cause crashes to you? Then I can try to play around with the file and see if I find something special about it which may explain the crashes (this is not very probable, I know, but at least there is a chance).
7) It may be also helpful if you could attach some MacOS log files created on the crashes to this bug report. I don't know if Apple has changed this in MacOS X 10.7, but with MacOS X 10.6 this is simple:
* When LibreOffice (or any other application) crashes, MacOS will present to you a dialog window saying something like "LibreOffice wurde unerwartet beended." Either this dialog window already contains a big text field labelled "Problemdetails und Systemkonfiguration", or you may have to click on "Details einblenden" first to show this text field.
* Just click in this large text field, press Command+A to select all the text, then press Command+C to copy it.
* Then please switch to any text editor (like Apple's TextEdit), create a new empty text file and insert the complete copied text via pressing Command+V.
* Now please save the new text file under a new name.
* Then come back to this bug report at
and click on "Add an attachment". Select your new text file to attach it. In the comments field, please describe in short words what you did (or wanted do do) when this crash occured.
You may repeat this for some times, e.g. attach two or three or ... files of this kind to this bug report, which were created on crashes under different circumstances, i.e. when you did different things. Comparing the log files may allow us to infer if LibreOffice always crashes for the same reason(s) or if there seem to be different bugs involved here.
I know answering this questions and following these instructions will be laborious for you, but it may help us to track down the problem and to solve it. If anything is unclear, feel free to ask here again -- or contact me directly via an e-mail to firstname.lastname@example.org, especially if you prefer to talk about the issue in German -- this may make it easier for both of us ;-). Thank you very much in advance for your help!
As I asked for most of bugs referring a crash, could you also first try to reproduce with a brand new LO profile ? (see http://wiki.documentfoundation.org/UserProfile)
A lot of bugs were due to the profile. A meta bug exists about profile problems fdo#43489 (NB : this one doesn't include crash but anyway...)
(In reply to comment #3)
> As I asked for most of bugs referring a crash, could you also first try to
> reproduce with a brand new LO profile ? (see
Yes, Julien is right -- in enumerating all these possible steps (comment #2) I completely forgot this one, which is probably the most important idea. Sorry for that! So, please try this first -- thank you very much! (And thank you, Julien, too!)
I did reset the user profile and now LibreOffice seams to rum much better.
I do not had the time now to test everything, but I promise to to so today and tomorrow.
If I do not post anything here consider the problem solved ;-)
Roman: no problem :-) (I see so often problems linked to profile)
Thorsten: it could be useful you zip your buggy LO profile and attach to this bugtracker.
Then I'll link to fdo#43489
Created attachment 63425 [details]
(In reply to comment #6)
> Then I'll link to fdo#43489
Changed Status to "NEW", because even if the bug is solved for the original reporter (see comment #5) by our workaround (a new user profile), this workaround is still a workaround and no fix. Also this report is of some importance for the handling of our meta-bug 43489, because this present bug report has got the attachment of the problematic profile folder. So don't close this one, but leave it as "NEW", linked to the meta bug.
Also adapted the summary to reflect our increased knowledge (and to make it easier to find this bug when searching for User Profile-related problems).
Since there's a task about this, I put it as a dup.
*** This bug has been marked as a duplicate of bug 43489 ***
(In reply to comment #10)
> Since there's a task about this, I put it as a dup.
I agree, but I'm not sure if this is the correct way to proceed. Should we
(a) mark bug reports of this kind as a duplicate of the task bug report,
or should we
(b) just add them to the "Depends on" list of the task bug report?
Julien, you have asked the same question in some other, very similar bug report. Did you get/find an answer?
I just want to get a consensus about this question to ensure that we all handle such bugs in a consistent way. At the moment we use a mix of both ways ...
Roman: you're entirely right, we must be coherent and I'm not sure now :-(
Rainer: Any idea ? Perhaps you had already answered about this but I don't remember right now.
A real Bug can't be a DUP of a TASK bug, because there will no be any bugfix for the task bugs, that's the proceeding we do. At least this one is not not a DUP of Bug 43489, so I reopen it to show that currently there is no fix.
The attachment " profile folder" contains the profile causing the crashes?
Roman/tschloesser: do you reproduce the problem with the buggy profile folder attached and last LO version (3.6.4)?
It's good to have this profile archived here; looking at it quickly - I see only bundled extensions - so nothing much exotic there. A bibliography database ( but that won't affect impress ), and quite a large registrymodifications.xcu
That has a number of templates listed in it - really quite a lot in fact in elements like:
<node oor:name="vnd.sun.star.hier://com.sun.star.ucb.DefaultHierarchyDataSource/templates/-/Pr%C3%A4sentationshintergr%C3%BCnde/Wine" oor:op=
It's not entirely clear what those paths are for, they do look unusual.
Given the lack of more feedback and/or interest in testing with this old profile to get stack traces, the lack of more recent duplicates, and a number of other fixes around profile migration, I guess we can close this for now :-)
Please re-open if you can reproduce any of this / get a stack trace.