GNOME Bugzilla – Bug 614596
Nautilus Actions' actions don't show up in context menus
Last modified: 2010-04-09 12:35:35 UTC
All Nautilus Actions' actions have stopped showing up in the context menus of Nautilus after a recent update. They don't work whatsoever, even killing Nautilus and rebooting the system doesn't work, no matter how loose you set the filters. This bug was originally reported by Mike Durham on Launchpad in Ubuntu at <https://launchpad.net/bugs/488612>
Created attachment 157723 [details] Nautilus context menu with a 'N-A action'
Hi Sense, Previous attachment is a screenshot of an action defined in NACT and displayed in Nautilus context menu. So I'm not able to confirm this bug. I have no idea at the moment why such regressions are seen under Lucid :( I have to do more tests.. However, I may bring some comments to https://bugs.launchpad.net/ubuntu/+source/nautilus-actions/+bug/488612: - there is no need to killall nautilus when you update an action in NACT; GConf is monitored, and the Nautilus context menu is automatically updated when an action is updated in GConf. - yes, 2.29.x is a big evolution over 1.12 serie - I confirm that export tool doesn't actually export anything under Lucid (though as a temporary work-around, drag-and-drop seems fine) - "albeit with lots of minor and not-so-minor bugs": could Sebastian be kind enough to report them, please ?
Export is fixed and pushed in git.
It seems that this bug was caused by confusion over the requirements for the commands. Most people, including me, just entered a command. That does not work, but apparently it did work in previous releases. May I suggest some sort of auto-detection for the command path, which is called when the action is saved?
Well, this is not a bug, this is a feature ;-) I was not conscious that most existing actions didn't use absolute path. This appears to me as a possible source of mistakes, if not a security hole. Previous versions of N-A didn't know how to determine the actual path of a command. They just didn't care, fully relying on 'g_spawn_command_line_async' function to find a command with the same expected name in the current PATH. Checking a command againt a PATH at save time is far less relevant that checking it at runtime. More, a command for a user may do not resolve to same command for another user, because of different PATHs :( I may propose : - accept command without an absolute path at runtime only - as soon as an action is edited in NACT, requires that the command be absolute. What do you think about this ?
Ah! Another precision. In NACT, actions are : - in italic: modified - in red: invalid. Since 1.11.2.
I'm not so sure if letting the user discover the whole path would be the best solution as binaries may be located at several places. But as it is now I do think that your suggestion would be the best (temporary) solution.
Fixed in 35cc18e44dafd0ededa35f76f57f7c133f516b6d.
Thank you, you have been very helpful with several bugs forwarded from Ubuntu.