https://bugs.winehq.org/show_bug.cgi?id=57329
Michael Pfister schoko.bombe44@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |schoko.bombe44@gmail.com
--- Comment #2 from Michael Pfister schoko.bombe44@gmail.com --- I ran into this exact issue using an app-launcher that was adhering to desktop entry specifications as by https://specifications.freedesktop.org/desktop-entry-spec/latest/exec-variab....
This is an example of one of the Exec lines in my wine desktop entries: Exec=env WINEPREFIX="/home/michael/.wine" wine C:\\users\\michael\\AppData\\Roaming\\Microsoft\\Windows\\Start\ Menu\\Programs\\Games\\Pinball.lnk
The problem seems to be the space in Start\ Menu. It is not eligible for plain desktop entry spec implementations running the command directly since the Exec key rule "Arguments are separated by a space." applies.
This behavior is also visible in my system journal. I have added the relevant lines to the "Attachments" section.
I posted the original issue on https://github.com/albertlauncher/albert/issues/1486 but then came to the realization that this is a problem with wine incorrectly setting the Exec paths on wine desktop entries.