-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create /etc/shells
if it is missing
#309
Conversation
Resolves: #288 The shell discovery process in vscode crashes if `/etc/shells` does not exist, resulting in no shells being available (including any custom profiles). This will link `/var/run/host/etc/shells` to `/etc/shells` if the latter is missing.
Started test build 89432 |
Untested, will test this in a few hours. |
Build 89432 successful
|
Tested on Silverblue 36. |
Works well for me on Fedora 36 Workstation, as long as I have my settings.json set up as directed at first startup. Thank you for the fix! This enables me to stop using the deprecated workaround for settings.json listed in the bug #288 thread. |
@nedrichards does this make sense to merge? Thank you! |
So far works well for me (Fedora 35 Silverblue). 👍 |
Yep - working flawlessly. Been working with it full-time for the past 3 days. |
Resolves: #288
The shell discovery process in vscode crashes if
/etc/shells
does not exist, resulting in no shells being available (including any custom profiles). This will link/var/run/host/etc/shells
to/etc/shells
if the latter is missing.