| Summary: | Visual Studio Code desktop action doesn't launch | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | codingkoopa |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | nate, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.18.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
The error dialog that is shown after clicking on the desktop action.
The context menu in which the desktop action appears. |
||
|
Description
codingkoopa
2020-04-16 02:07:51 UTC
Created attachment 127589 [details]
The context menu in which the desktop action appears.
>/usr/bin/code-oss --no-sandbox --new-window %F
How can an action take a filepath, that sounds wrong, but I assume we would parse it out.
What happens when you run:
/usr/bin/code-oss --no-sandbox --new-window
and
/usr/bin/code-oss --no-sandbox --new-window %F
Also note that this code path has changed super recently so that we share the same path for action activation, that should help resolve this.
- "/usr/bin/code-oss --no-sandbox --new-window" opens a new empty window of VS Code. "Warning: 'sandbox' is not in the list of known options, but still passed to Electron/Chromium." is printed to the console. - "/usr/bin/code-oss --no-sandbox --new-window %F" opens a new empty window of VS Code, with "%F" (literally) opened as a new file. I do still call this a "new empty window" because of it launching without opening the most recent directory, which is what it can be configured to do when launched without the "--new-window" switch. The same string as before is printed to the console. > How can an action take a filepath, that sounds wrong, but I assume we would parse it out. It doesn't make sense to me either, but it does seem to be valid under the specification. "Action keys" (https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#extra-actions-keys) simply refers to the Exec key as it's used normally, under which "%F" is valid. desktop-file-validate doesn't say that there are any issues with it either. Information was added with comment 3; changing status for inspection. No longer able to reproduce. The "New Empty Window" action works without issue, as I test it right now. Aside from the "Icon" key of the desktop entry being changed to "com.visualstudio.code.oss", the desktop entry doesn't seem to have changed since I opened this bug. Cool, thanks. |