Steps how to reproduce with "LibreOffice 3.6.3.2” German UI/ German Locale [Build-ID: 58f22d5] on German WIN7 Home Premium (64bit) 1. Install extension from harddisk, make sure that 1.6 JRE is selected 2. Close / reopen LibO 3. Menu 'File -> New -> Master Document' > Master Document will be created 4. Menu 'File -> Print' Bug: Crash with message "Runtime Error! Progran ...\soffice.bin abnormal program termination" AOOo 3.4.0 suffers from the same problem @grimeton@gmx.net It would be great if you could create a crash report Major due to Marketing issues
Rainer: On pc Debian x86-64 with 3.6 sources updated today I don't reproduce this problem. But : - I installed extension for all users (should i have choosen "just for me"?) - above all, I've got Open jdk 1.7 not 1.6 So it's more for information than to really help :-( Anyway, did you mean the bug doesn't appear with Java 1.7?
I installed for ALL. I did not test Java 1.7, because on the website Java 1.6 is recommended and I read about additional problems on <discuss@de.libreoffice.org>. I did a second test with "LibreOffice 3.6.3.2” German UI/ German Locale [Build-ID: 58f22d5] on German WIN7 Home Premium (64bit) an Java 1.7.0.9, also crashes. Sorry, I forgot to select the OS, I think this one is a typical WIN crash A similar crash also appears form time to time without any typical user action, I am pretty sure that reason is the Porto Extension.
Taking these Communication Platform Bugs for now. Please leave the bugs open, I hope that soon someone of Deutsche Post will start to fix these bugs.
*** Bug 56509 has been marked as a duplicate of this bug. ***
Today I sent an email to "Deutsche Post", will see...
Currently no longer reproducible with "LibreOffice 3.6.5.2 " German UI/ German Locale [Build-ID: 5b93205] {pull date 2013-01-18} on German WIN7 Home Premium (64bit), also not with OOOo 3.4.0. I tested Extension versions 1.0.1 and 1.0.2. Might have been some Java related issue or whatever. Can someone confirm this progress?
Win8 64bit LibreOffice 3.6.5.2 Extension 1.0.2 so far no problem.
thank you Frank for your feedback, I put it RESOLVED/WFM. (Of course Rainer, if you disagree, don't hesitate to reopen,... :-) )