KMenuEditor 5.26 splits what was previously the "Command" textbox into a "Program" textbox and a "Command-Line Arguments" textbox. Attempting to pass an environment variable (ie trying to run a command such as "LANG=C /usr/bin/foobar" is now much more wonky, as it requires filling in 'env' for the "Program" textbox and the actual program into the "Command-Line Arguments" textbox, which isn't particularly intuitive or elegant.
Created attachment 152878 [details] How it worked in 5.25
Created attachment 152879 [details] How it works (doesn't work) now
Created attachment 152880 [details] How it works (doesn't work) now, p2
This was done intentionally to prevent you from entering "FOO=bar app". This is not a valid Exec line according to https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s07.html Quoting: > The Exec key must contain a command line. A command line consists of an executable program optionally followed by one or more arguments. Your way of specifying environment variables happend to work in some places, but fails in other, so this change was done to make it explicit that this way is not supported
(In reply to Nicolas Fella from comment #4) > This was done intentionally to prevent you from entering "FOO=bar app". This > is not a valid Exec line according to > https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s07.html > > Quoting: > > The Exec key must contain a command line. A command line consists of an executable program optionally followed by one or more arguments. > > Your way of specifying environment variables happend to work in some places, > but fails in other, so this change was done to make it explicit that this > way is not supported I happen to install the same app with different versions and formats (appimage and native) that use different config paths, how I'm supposed to specify those paths as env vars in the command line inside kmenueditor ?
Fixed with Bug 461315.