Add troubleshooting tips for the keyboard service dialog #168
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In Bash, backticks are used for command substitution. In PowerShell they're escapes.
We had marked some powershell code as "bash"
|
Docs Build status updates of commit 5035bda: 🕙 Pending: waiting for processors (40 builds ahead of you) |
4 tasks
|
Docs Build status updates of commit 5035bda: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
ghost
pushed a commit
to microsoft/terminal
that referenced
this pull request
Nov 4, 2020
## Summary of the Pull Request  With this PR, the Terminal will check to make sure the "Touch, Keyboard and Handwriting Panel Service" is enabled at startup. If it isn't, then the Terminal won't be able to receive keyboard input (see #4448 and the 20 linked issues to that one). ## References * See #4448 for more details ## PR Checklist * [x] Closes #7886 * [ ] Should this make #4448 not-open as well? * [x] I work here * [n/a] Tests added/passed * [x] Docs: MicrosoftDocs/terminal#168 ## Validation Steps Performed I manually set the service to "Disabled", restarted the machine, verified the dialog opens (and that I'm unable to type in the Terminal), then re-set the service to automatic and rebooted, and the dialog doesn't appear.
DHowett
pushed a commit
to microsoft/terminal
that referenced
this pull request
Nov 9, 2020
 With this PR, the Terminal will check to make sure the "Touch, Keyboard and Handwriting Panel Service" is enabled at startup. If it isn't, then the Terminal won't be able to receive keyboard input (see #4448 and the 20 linked issues to that one). * See #4448 for more details * [x] Closes #7886 * [ ] Should this make #4448 not-open as well? * [x] I work here * [n/a] Tests added/passed * [x] Docs: MicrosoftDocs/terminal#168 I manually set the service to "Disabled", restarted the machine, verified the dialog opens (and that I'm unable to type in the Terminal), then re-set the service to automatic and rebooted, and the dialog doesn't appear. (cherry picked from commit d5d2b77)
cinnamon-msft
approved these changes
Nov 10, 2020
|
Docs Build status updates of commit 80c3c02: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
cinnamon-msft
deleted the
dev/migrie/warn-if-youve-turned-off-the-keyboard
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These are the steps to re-enable the keyboard service, the one that we'll warn about in microsoft/terminal#8095.
🔔 THERE'S NO
release-1.5BRANCH YET 🔔 @cinnamon-msft make sure to fix this before merge