"New Item" does not show up in menu

[SebiTimeWaster]

Expected behaviour

Creating a "New Item" shows up in menu editor and in Brisk.

Actual behaviour

After creating a "New Item" it is created in ~/.local/share/applications/, but does not show up in the menu editor or in the menu itself. Adding the .desktop entry by hand in the "mate-applications.menu" file does not make it show up either, when i move another item (basically just changing something) the entry is removed from the file. Tried to play around with file rights and copying the .desktop file to /usr/share/applications/ to no avail. The .desktop file itself work perfectly fine.

Steps to reproduce the behaviour

Create a new item

MATE general version

1.24.0

Package version

?

Linux Distribution

Ubuntu 20.04

Link to downstream report of your Distribution

?

[SebiTimeWaster]

Ok, i just found out this happens when the specified command is a target in the user directory (even though it is in the PATH) AND it is not fully qualified (ie. "myscript" instead of "/home/user/myscript").

There should either be an error message or it should correct it automagically.

[linuxgirl22]

Hi and just tell me to create my own thread if it isn't right to add this onto your thread, but same issues here (launcher visible in ~/.local/share/applications/, but not anywhere else). Tried menulibre, and running Mozo from terminal, but same. An entry is never visibly created in either. Uninstalled menulibre, as Mozo runs, despite not working.

Mate 1.24.0-1, Anarchy (arch, at baby level though, lol). Not understanding how to manually fix it at this point, so just to report a +1 really.

[mbkma]

I can confirm this issue. I agree that there should be an error dialog or the OK button should be insensitive. That said you should specify the whole path as mozo can not (and should not) guess which script you mean by "myscript" (imagine "/home/user/myscript" and "/home/user/scripts/myscript". Which one should mozo pick?).

[SebiTimeWaster]

I can confirm this issue. I agree that there should be an error dialog or the OK button should be insensitive. That said you should specify the whole path as mozo can not (and should not) guess which script you mean by "myscript" (imagine "/home/user/myscript" and "/home/user/scripts/myscript". Which one should mozo pick?).

i have no problem with mozo checking the specified command, not finding it and refusing to create the menu entry (and telling the user why), perfectly fine with me.

about the multiple commands issue: there is a order to $PATH that defines that the first found match is what is intended to be used.

[ghecko]

Hi,

It seems that adding NoDisplay=false to the .desktop file resolve the issue