void-linux / void-linux/void-packages
VSCode's desktop file is executable
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.4k
- Forks
- 2.8k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 299
Description
Is this a new report?
Yes
System Info
Void 6.6.8_1 x86_64 GenuineIntel uptodate hold rrrdDFFFFFFFFFFFFFFFF
Package(s) Affected
vscode-1.85.1_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
-rw-r--r-- /usr/lib/code-oss/resources/app/resources/linux/code.desktop
Actual behaviour
-rwxr-xr-x /usr/lib/code-oss/resources/app/resources/linux/code.desktop
Steps to reproduce
This is strange. I might take a look at this myself. There doesn't seem to be anything out of ordinary in the template file. A simple chmod added to do_install() would solve the problem, but that wouldn't solve the cause of this (which I do not know).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the VSCode package template and its do_install() entry point, then compare the source mode with the installed code.desktop path at /usr/lib/code-oss/resources/app/resources/linux/code.desktop. Determine why the desktop file becomes executable; done means the installed file has -rw-r--r-- without masking the underlying cause with an unrelated workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- build-system, desktop
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100