I did a writer serial-letter (starting from new blank document)
did around 10 trys with 2 sources (some .mdb some mysql) bouth via .odb as datasource
when i arrived at last step it prepares the adresses and it runs trough (in my case 200 datarows)
at the end screen gets grey and the standard windows error "programm did not respond" (programm reagiert nicht mehr)
Libre Office got crashd and killd
at start LO again it tryes to restore.. but only restores an empty doc
i already solfed it:
disabled java in the LibreOffice options and tried again
now it works
my java version is: "Java 7 updater 79" 7.0.790
Created attachment 120491 [details]
the errormsg that i got
in the background you can see the last step of the serialletter wizard
Could you please try to get a backtrace of the crash? It would be helpful.
Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the bt.
I got the same problem with an AMD64 system using Linux Mint 17.3. I've got the following error message:
SfxBaseModel::impl_store <file:///tmp/lu13475f3ear9.tmp/0.sxw> failed: 0x81a
(In reply to Uwe Richter from comment #3)
> I got the same problem with an AMD64 system using Linux Mint 17.3. I've got
> the following error message:
> SfxBaseModel::impl_store <file:///tmp/lu13475f3ear9.tmp/0.sxw> failed: 0x81a
Ok I'm setting this to new.
Uwe: it would be great, if you could get a gdb trace of the crash and attach it here.
You first have to install a debug package. Here are the instructions: https://wiki.documentfoundation.org/QA/BugReport/Debug_Information
Maybe you could first test, if the crash is still in version 5.1 RC1.
OS set to All.
*** Bug 96634 has been marked as a duplicate of this bug. ***
Any update with last stable LO version (5.1.3) + brand new profile?
Also, would it be possible to have a small kit to reproduce this with minimal step by step process?
More than 12 months of no response, bug was for 5.0 and from 5.2 there are just 5 steps, not reproducible. I'll close this one.
Should this exact bug be reproduced with current LO version, feel free to set back to New or, better, open a new bug. Hopefully from 5.2 there would be a Crash Report available.