Bug 54882 - Calc will not open a file containing a colon from command line
Summary: Calc will not open a file containing a colon from command line
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2012-09-13 16:28 UTC by Ray
Modified: 2015-09-08 10:23 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Ray 2012-09-13 16:28:07 UTC

Comment 1 Ray 2012-09-13 16:32:46 UTC
Files with a ':' in the file name open properly from File -> Open, but it will not open the same file when parsing it from the command line.

soffice myfile:xxxx
soffice myfile\:xxxx
soffice 'myfile:xxxx'

All of these commands will begin to load calc, show the splash screen, and then silently fail.
Comment 2 QA Administrators 2015-01-05 17:50:59 UTC
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)

Thank you for your help!

-- The LibreOffice QA Team
Comment 3 Buovjaga 2015-01-19 12:13:09 UTC
Yep, I get this for all of the three variants mentioned in comment 1:

./soffice kaksois\:piste.ods 
warn:unotools.misc:3251:1:unotools/source/misc/mediadescriptor.cxx:626: caught ContentCreationException "No Content Provider available for URL: kaksois:piste.ods" while opening <kaksois:piste.ods>
warn:filter.config:3251:1:filter/source/config/cache/typedetection.cxx:455: caught Exception "Could not open stream for <kaksois:piste.ods>" while querying type of <kaksois:piste.ods>
warn:fwk.dispatch:3251:1:framework/source/dispatch/loaddispatcher.cxx:132: caught LoadEnvException 0 "type detection failed" while dispatching <kaksois:piste.ods>
warn:tools.debug:3251:1:tools/source/debug/debug.cxx:297: no DbgTestSolarMutex function set

Ubuntu 14.10 64-bit Version:
Build ID: 0ffa3abc7d6c0437ece30cfb1430d28ffcc9f5c1
TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2015-01-15_22:47:16
Comment 4 Stephan Bergmann 2015-09-08 10:20:46 UTC
soffice accepts arguments that are either URLs or pathnames in system-specific notation.  Those two sorts of syntax have overlap, so there are inputs that are ambiguous whether they shall denote a URL or a pathname, and LO uses some heuristics there but will necessarily mis-guess in some cases.

What you need to do to disambiguate a filename containing a colon as a pathname is to make it into a relative pathname containing a slash before the colon, as in

  soffice ./myfile:xxxx

(The quoting examples you gave above, myfile:\xxxx and 'myfile:xxxx' are completely irrelevant here, assuming you are demonstrating what you typed into a Posix shell, as these quotings are undone by the shell and are not seen by soffice.)
Comment 5 Stephan Bergmann 2015-09-08 10:23:19 UTC
(What /is/ a bug, though, is that LO silently fails for command line URLs that it doesn't know how to handle, like <myfile:xxxx>, without giving any error message to the user.  But I'm almost certain there is already a bug report for that.)