Issue 126141

Summary: File creation or PDF export fails with pound (#) in export filename (nonexistent object error)
Product: General Reporter: Lewis Rosenthal <lgrosenthal>
Component: uiAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Minor    
Priority: P5 (lowest) CC: mseidel
Version: 4.1.1   
Target Milestone: ---   
Hardware: All   
OS: OS/2   
Issue Type: DEFECT Latest Confirmation in: 4.1.7
Developer Difficulty: ---
Issue Depends on:    
Issue Blocks: 126518    

Description Lewis Rosenthal 2015-02-28 15:41:34 UTC
Attempting to export as PDF with an otherwise-legal "#" in the filename fails consistently on OS/2 but works on other platforms.

It apparently does not mater whether the "#" is preceded or succeeded by a space. Failure occurs on multiple filesystems (JFS, HPFS, NetWare IFS, Samba share).

I just noticed this same failure under OOo 3.2.0, so apparently, this has been with us for a while (I don't normally use these characters in filenames, but was quickly exporting a document sent to me).

No special output formatting has been selected (i.e., defaults set).
Comment 1 Lewis Rosenthal 2020-03-13 18:55:16 UTC
This is a more widespread issue than I originally thought.
Comment 2 Lewis Rosenthal 2020-03-13 18:58:16 UTC
Apparently, we are unable to create new files containing "#" even when such a character is legal in the filesystem. We can rename a file to contain "#" and open it without incident (see first case reported here), but attempting to export to PDF or to Save As with the new filename containing "#" will fail. Saving the existing file (with "#" in the filename) succeeds.
Comment 3 Matthias Seidel 2020-03-13 19:11:57 UTC
Confirmed wit AOO 4.1.7 on ArcaOS using a JFS formatted partition.