This bug also occurs for filenames that actually have "%20" strings instead of spaces.
So attempting to open either "some file.xxx" or "some%20file.xxx" by double-clicking in Nautilus results in the error message: "failed to open file:///some%20file.xxx." I wonder if this is a Nautilus issue, because the following commands issued from a terminal work just fine: $ gmplayer some\ file.xxx $ gmplayer some%20file.xxx -- gmplayer fails to play a file whose filename contains spaces https://bugs.launchpad.net/bugs/164709 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
