Bug Hunting Session
Bug 89675 - Cannot save filenames containing # on sftp shares
Summary: Cannot save filenames containing # on sftp shares
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.4.0.3 release
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Network
  Show dependency treegraph
 
Reported: 2015-02-26 07:59 UTC by berte
Modified: 2017-09-29 21:00 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Save as dialog (27.50 KB, image/png)
2015-02-26 07:59 UTC, berte
Details
Error message (11.90 KB, image/png)
2015-02-26 08:00 UTC, berte
Details

Note You need to log in before you can comment on or make changes to this bug.
Description berte 2015-02-26 07:59:04 UTC
Created attachment 113701 [details]
Save as dialog

Overview:

    In Calc, saving a document containing a # in its name results in an error when the location is a sftp share. There is no poblem to open such a file.

Steps to Reproduce:

    1) Open Calc

    2) Save as "test#.ods" on a mounted sftp share

Actual Results:

    Error dialog. File is not saved. Application do not crash.

Expected Results: 

    File saved correctly.

Build Date & Hardware: Date and hardware of the build in which you first encountered the bug.

    Version: 4.4.0.3 Build ID: 40m0(Build:3) on Ubuntu 14.04

Additional Builds and Platforms:

    No other platform tested

Additional Information: See attached files
Comment 1 berte 2015-02-26 08:00:11 UTC
Created attachment 113702 [details]
Error message
Comment 2 tommy27 2017-01-24 08:34:45 UTC
hi there, is the bug still present in LibO 5.2.4.2?
Comment 3 Xisco Faulí 2017-01-30 23:52:41 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2017-08-30 19:27:55 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2017-09-29 08:54:59 UTC Comment hidden (obsolete)
Comment 6 berte 2017-09-29 16:09:36 UTC
Bug is not present anymore. Tested on Version: 5.4.1.2
Thanks a lot.
Kind regards.