Bug 49583 - VIEWING: Libreoffice does not work with %20 in filenames on the commandline
Summary: VIEWING: Libreoffice does not work with %20 in filenames on the commandline
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
3.4.6 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-07 06:37 UTC by Matthijs Kooijman
Modified: 2013-02-21 15:45 UTC (History)
0 users

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 Matthijs Kooijman 2012-05-07 06:37:10 UTC
Problem description:

When a filename is specified on the commandline that contains %20, it seems the %20 is replaced by a space before trying to open a file (even though no file:// url is used, just a plain filename).

Steps to reproduce:
1. Create a file with %20 in it:
 $ touch foo%20bar.odt
2. Try to open it through the commandline:
 $ libreoffice 'foo%20bar.odt'
3. Libreoffice now shows an error message: "/tmp/foo bar.odt does not exist" (Not that /tmp is just the cwd when running these commands).

The following ways of opening the file do _not_ fail and work as expected:
 - When specifying an absolute path:
    $ libreoffice '/tmp/foo%20bar.odt'
 - When opening the file through File->Open...
 - When passing the filename urlencoded (i.e., encoding the % from %20 as %25):
    $ libreoffice 'foo%2520bar.odt'

Platform (if different from the browser): Debian wheezy
              
Browser: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.3) Gecko/20100101 Firefox/10.0.3 Iceweasel/10.0.3
Comment 1 Juan Canham 2012-12-23 18:31:34 UTC
Hi,

I just tried this on Version 3.6.2.2 (Build ID: 360m1(Build:2)) on kubuntu 12.10, it seems to work correctly, could you confirm if this has been fixed?

Thank, Juan
Comment 2 Matthijs Kooijman 2012-12-24 10:14:49 UTC
I just tried 3.6.4 from Debian experimental and I can no longer reproduce the problem.

Thanks!
Comment 3 Joe Hockaday 2013-02-21 15:45:20 UTC
Appears to have been fixed a long time ago.

Tested on version 3.6.5.2 on FC18, cannot reproduce original bug.

Closing due to age.