https://bugs.documentfoundation.org/show_bug.cgi?id=172760

            Bug ID: 172760
           Summary: Writer cannot save documents when folder name starts
                    with "#"
           Product: LibreOffice
           Version: 26.2.2.2 release
          Hardware: x86-64 (AMD64)
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Writer Web
          Assignee: [email protected]
          Reporter: [email protected]

LibreOffice Writer cannot save documents when the destination folder name
begins with the character "#".

X:\temp\      → works
X:\# temp\    → fails


Environment:

Operating system: Windows 11
LibreOffice version: 26.2.2.2
Hardware: x86_64 (AMD64)
File format tested: DOCX
Storage: External drive

Steps to reproduce:

Create a folder on an external drive:

X:\temp

Open a LibreOffice Writer document and save it in this folder:

X:\temp\test.docx

Result:
The document saves successfully.

Create another folder:

X:\# temp

Open the same document and save it in this folder:

X:\# temp\test.docx

Result:
Saving fails.

Error message:

"Error saving the document.
Object not accessible.
The object cannot be accessed due to insufficient user rights."

Additional observations:

The same document saves successfully in the root directory of the external
drive.
The same document saves successfully in folders that do not begin with "#".
Windows applications such as Notepad can create and save files in the "# temp"
folder.
The problem appears to be specific to LibreOffice.
LibreOffice backup files (.bak) are created correctly in normal folders.

Expected behaviour:

LibreOffice should be able to save documents in any valid Windows folder name.
The "#" character is valid in Windows folder names.

Possible cause:

LibreOffice may be incorrectly handling paths beginning with "#" during save
operations, backup creation, temporary file creation, or lock file handling.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to