Issue 50216 - Input/Output Error while opening file with spaces in directory name
Summary: Input/Output Error while opening file with spaces in directory name
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: OOo 2.0 Beta
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: thorsten.martens
QA Contact: issues@framework
URL:
Keywords: needmoreinfo, oooqa
Depends on:
Blocks:
 
Reported: 2005-06-01 22:49 UTC by mibraun
Modified: 2005-06-02 16:53 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description mibraun 2005-06-01 22:49:31 UTC 
Hi,

when I'm opening or saving a file which resists in a directory with a space in
the directory name, I'll get the following error: "General Input/Output Error."

If I do the same in a similar directory not containing a space in its name,
everything works fine.
I tried in calc, drawing, writer, database module and it's everywhere the same
Comment 1 mci 2005-06-02 10:27:43 UTC 
Hi mibraun,

thanks for using and supporting OpenOffice.org...

I get no problem here on FC3 and Solaris using m106....

- Which distribution do you use?
- Do you OOo downloaded from OpenOffice.org  or delivered by your distirbutor?
- Do you open the file out of the office or by shell (something like 
          soffice path/to/file/file.odt)?
- If you open the file out of the Office: Do you use OpenOffice.orgs own dialogs?
          (Tools->Options->OpenOffice.org -> General 
          -> checkbox "Use OpenOffice.orgs own dialogs")
Comment 2 mci 2005-06-02 10:36:43 UTC 
hmmmm, I tried this using both dialogs on FC3 and didn't get that problem...
Comment 3 mibraun 2005-06-02 16:53:25 UTC 
Hi,

it tourned out to be the same as Bug 36634. By accident, the directory with
space in name was put on a nfs share by a symlink, that's why it didn't notice
the change of mount point before.