Alacarte menu changes do not change applications menu item.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Wine |
Confirmed
|
Undecided
|
Unassigned | ||
alacarte (Ubuntu) |
Confirmed
|
Low
|
Unassigned | ||
gnome-menus (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
Binary package hint: alacarte
This bug affects both Feisty and Gutsy and is reproducible.
When editing a application launcher that was incorrectly added during a Wine installation alacarte didn't edit both file affected.
This file was correctly changed with alacarte.
.local/
This file was NOT changed with alacarte.
.local/
The second file is the one that appears in "main menu > Applications > Wine > Programs > MEDITECH"
Alacarte should update the new path when the application launcher is edited.
Reproduction.
Install application "wine setup.exe"
Click on menu "Application > Wine > Programs > MEDITECH > Workstation 3"
Error "Path not found"
Open alacarte and correct the the application path.
Click on menu "Application > Wine > Programs > MEDITECH > Workstation 3"
Error "Path not found"
To correct the error, edit the following file with a text editor
.local/
Just a note: I believe the application path was incorrectly generated in the first place because it's a legacy 16 bit proprietary telnet client. This app is poorly hacked on Windows. It's not surprising to find problems with it in Ubuntu.
Please advise me if I need to file additional bugs with the wine or gnome teams. I filed this bug because the editing process is handled by alacarte. If I can be of further assistance let me know.
Changed in alacarte: | |
status: | New → Confirmed |
affects: | gnome-panel (Ubuntu) → gnome-menus (Ubuntu) |
Changed in gnome-menus (Ubuntu): | |
importance: | Undecided → Low |
Changed in alacarte (Ubuntu): | |
importance: | Undecided → Low |
I can confirm this bug. Actually, I did not know this was what was happening until I read this bug report and checked those paths.
It is very confusing to change a menu entry, then trying it, nothing happens, then using the menu edito again, copying the string to be executed, running it in a terminal, and it works! "Ehhh. What?"
This should be updated soon - has been a bug for *ages*