Steps to reproduce (with "LibreOffice 3.4Beta2 – WIN7 Home Premium (64bit) English UI [DEV300m103 (Build:1)]"): 1. open new WRITER document 2. type an "x" 3. Menu "File > Export as PDF ...' Expected: Options dialog to select page range, compresion, initial view and all other options. The problem is not limited to WRITER. Works fine with OOo-dev 3.4 I only selected Severity "Critical", but for me that makes LibO completely unusable.
I can't reproduce. Dialog is shown correctly on my Win 7 system.
Not reproducible (on WinXP). Options dialog is shown (Writer). Works fine.
Strange. Uninstall - Install did not work, but removing AppData user profile healed the problem. What might have happened on my PC during installation of Beta2 that destroyed that part of UI? Does someone have any Idea how to "repair" the old user profile? It would be annoying to restore all my old settings in a new profile.
Problem with my active "normal" user profile disappeared after fallback from 3.4Beta2 to 3.3.2 and reappeared after installation of 3.4Beta3
Reported exactly the same prob (missing pdf-export-dialogue) as it appears on all of my Macs under Mac OS 10.6.7.
(In reply to comment #5) > Reported exactly the same prob So I set this to NEW although nearby all aspects of the effect are unknown. No idea with what research we can shed light on the dark.
I can confirm this on Windows 2008 R2. Installed 3.2.2 on a clean system, upgraded to 3.4 beta 4. When clicking on File > Export to PDF, an export save dialog prompts, not showing PDF options dialog. Removing my user folder and restarting LibreOffice solves the issue.
I can confirm that on a second very different WIN PC after upgrade from 3.3. to 3.4Beta4. Modified OS due to confirmations.
On my Laptop with "LibreOffice 3.4Beta4 – WIN7 Home Premium (64bit) German UI [DEV300m103 (Build:4)]" deletion of user profile also healed the problem with the missing dialog.
May be someone can try to confirm "Bug 36820 - PDFEXPORT with option "Tagged PDF" crashes WRITER documents"?
*** Bug 37111 has been marked as a duplicate of this bug. ***
After the prob continued with beta 4, I deleted the user-folder on my Mac (10.6.7) and now all is fine...
I can confirm. To avoid the problem it is sufficient to delete file ~/.libreoffice/3/user/extensions/bundled/registry/com.sun.star.comp.deployment.component.PackageRegistryBackend/Linux_X86_64.rdb (on 64bit Linux).
(In reply to comment #13) > I can confirm. To avoid the problem it is sufficient to delete file > ~/.libreoffice/3/user/extensions/bundled/registry/com.sun.star.comp.deployment.component.PackageRegistryBackend/Linux_X86_64.rdb > (on 64bit Linux). I can confirm the behaviour and that this tip works. Thanks
I confirm the bug for LibreOffice 3.4.4 OOO340m1 (Build:402) under Ubuntu Linux 11.10/32 Bit. After deleting/renaming the subfolder .libreoffice/3/user/uno_packages the pdf export dialogue became visible again.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
This bug is still unfixed (latest observation in December)
this bug also shows up with a fresh user profile (anyway in 3.5.0 rc1) and a regression and already added to 35673
(In reply to comment #18) > this bug also shows up with a fresh user profile (anyway in 3.5.0 rc1) Hmm, I was confused with another bug. Sorry
@Cor: That means you did NOT observe THIS problem with 3.5.0 rc1?
All indications seem to show that this is a LibO 3.4 Problem. 3.4 lifecycle is terminated, so I close this one. Please feel free to reopen (and to remove "Blocks: 35673") if you fin out that the problem still exists with LibO 3.5.
& close
*** Bug 45809 has been marked as a duplicate of this bug. ***
*** Bug 36842 has been marked as a duplicate of this bug. ***