"Open With" application file paths incorrect

[NoOp]

Binary package hint: nautilus

System: Edgy 2.6.15-28-386 (#1 PREEMPT Thu Feb 1 15:51:56 UTC 2007)
Nautilus: Nautilus 2.16.1
Situation: Added new menu items via Applications|Edit Menus|New Item. Specifically to an OpenOffice install in the /opt/ directory. Example: /opt/openoffice.org2.2/program/swriter. However, the browsed to path shown in the application properties menu shows: /opt/openoffice\.org\2\.\2/program/swriter.
This does not present a problem in Applications|Office|menuitem as the program opens properly from the Applications menu.

Problem:
The above example link does create a problem (and is repeatable) in the following circumstance:
1. From Nautilus browser I click on a .doc file (or .odt or simlar) and wish to open it with the OOo Writer program that I've added in the Applications|Office| menu. So I right click the file and select "Open with Other Application".
2. I select the application that I've added to the Office menu (in this case OOo 2.2 Writer) from the application dropdown list. An error results: Could not add application - Could not add application to the application database.
3. Click on 'Custom Command' and find the path listed as: /opt/openoffice\.org\2\.\2/program/swriter (the same as was entered by adding to the menu via the browse to application box).
4. If the path is corrected to properly show: /opt/openoffice.org2.2/program/swriter the application is added to the application database.

It appears that an application with a path containing a period (.) in the path is not correctly added in Applications|Edit Menu|New Item.

[xtknight (xt-knight)]

Odd. Mine makes it "'/opt/testing.app/opera'" not "/opt/testing\.app/opera", e.g.

[xtknight (xt-knight)]

Woops. I was using Feisty, where it appears to have been fixed.

[Daniel Holbach (dholbach)]

Thanks for following up. Closing the bug.

[NoOp (glgxg)]

On 04/12/2007 03:34 AM, Daniel Holbach wrote:
> Thanks for following up. Closing the bug.
>
> ** Changed in: nautilus (Ubuntu)
> Status: Unconfirmed => Fix Released
>

Confirm that the bug is fixed in *Feisty*.

Ummm... the bug is filed against Edgy *not* Feisty.
I check updates daily and have found no fix that has been
released for Edgy. Please reopen the bug unless you can point to a
released fix for Edgy.

[Sebastien Bacher (seb128)]

We will not fix this bug to edgy, stables update are a non trivial work as they need to be tested to avoid any regression. You are the only one who opened a bug about this, that's not a security bug and looks like low importance, it's not a stable update candidate then