Bug 165967 - Version 25.2.2.2 on Windows 11 export to PDF now defaulting to last location instead of folder the file originates in.
Summary: Version 25.2.2.2 on Windows 11 export to PDF now defaulting to last location ...
Status: RESOLVED DUPLICATE of bug 165917
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
25.2.2.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-29 13:13 UTC by CSimmons
Modified: 2025-04-03 15:01 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description CSimmons 2025-03-29 13:13:07 UTC
Description:
Recently I upgraded to version 25.2.2.2. In Calc specifically, when I export to PDF from the menu it use to default to export location to the root folder where the Calc file is stored. Now it is defaulting to the last location I exported to. I believe this is a regression as I'm finding a lot of information about this exact same problem occurring about 4 years ago. The answer then was to use LO save/load dialogues in settings, but that fix does not work in current LO. This problem also occurs in Writer so it seems to be more than just Calc affected.  

Steps to Reproduce:
1. Export any Calc or Writer file to PDF
2. 
3.

Actual Results:
Export dialogue opens the last export location instead of the root folder the LO file is saved in. 

Expected Results:
Export dialogue should have defaulted to the same folder the original LO file is saved, as it has traditionally done for years. 


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 25.2.2.2 (X86_64) / LibreOffice Community
Build ID: 7370d4be9e3cf6031a51beef54ff3bda878e3fac
CPU threads: 12; OS: Windows 11 X86_64 (10.0 build 26100); UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded
Comment 1 m_a_riosv 2025-03-29 23:33:03 UTC

*** This bug has been marked as a duplicate of bug 165917 ***