Description: When creating a new document or creating a PDF a file dialogue appears, which is hard to position. You cannot scroll to the top of the tree. It stops at position 2 or jumps back to the initial directory, its a bad component. Also for PDF the initial directory should be the last one chosen, but it's the one from the save dialogue. Steps to Reproduce: 1. open document 2. press button for PDF 3. the file dialogue appears Actual Results: it's positioned somewhere by old memory Expected Results: it should be positioned to the last directory used in that context Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no
The PDF dialog not remembering the last location is in bug 147202. About the other issues, can you please test again in a recent version of LibreOffice to see if it is still the case, and paste here the version information from Help > About LibreOffice? https://www.libreoffice.org/download/download-libreoffice/ Thank you!
Dear Jens-D Doll, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
The file dialogue is OK now.
Thank you for testing again and confirming it is now gone in 7.4.7.2! (The version field is for "earliest version affected by the bug", so I am changing back to 3.3, even though I'm not sure you actually had tested that far back. If you can remember which version had the issue, please put that one in the field.) Marking as "works for me" as we are not sure what fixed it. Thanks!