Launch file associations break if path includes any spaces

Just discovered that new desktop shortcuts installed in Linux only work if the path doesn't contain any spaces. I dug in and manually generated a launcher jar load with the spaces encoded, and it worked. Spaces are not encoded in command line arguments in Linux.

If this isn't yet a known problem, I'll open a support ticket.

{ Unable to upload the screenshot at the moment, for some reason. }

Hm. This lines up with a reported and resolved bug ticket from four years ago, supposed to have been resolved in 8.1.21. It apparently regressed?

Can you reference IGN-6471 in your support ticket?

This is the v8.3.7 launcher. The targets are shortcut files ending in .designer, .vision, and .perspective. Deep links in the browser work fine, and these files work fine if I leave them in my normal Desktop folder. But when I organize into various folders, where some folder names have spaces, boom.

Not applicable to v8.1 at all. I guess this will be a new ticket.

The desktop files to which these file extensions are associated construct a file URL as file://%U, blindly concatenating the scheme with the rest of the absolute path. There is no automatic encoding of spaces or special characters at this point, and the launch jar is obviously expecting a compliant URL. :man_shrugging:

Ticket #191279, fyi.