-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
GUI configuration system (ninja menuconfig) exists with an error when the windows key is pressed #33212
Closed
thedjnK opened this issue
Mar 10, 2021
· 1 comment
· Fixed by #33347 · May be fixed by ulfalizer/Kconfiglib#103 or zephyrproject-rtos/Kconfiglib#11
Closed
GUI configuration system (ninja menuconfig) exists with an error when the windows key is pressed #33212
thedjnK opened this issue
Mar 10, 2021
· 1 comment
· Fixed by #33347 · May be fixed by ulfalizer/Kconfiglib#103 or zephyrproject-rtos/Kconfiglib#11
Labels
area: Build System
area: Kconfig
bug
The issue is a bug, or the PR is fixing a bug
priority: low
Low impact/importance bug
Comments
tejlmand
added a commit
to tejlmand/Kconfiglib-ulfalizer
that referenced
this issue
Mar 15, 2021
Fixes: zephyrproject-rtos/zephyr#33212 Ignoring when user inputs NULL in a text field. menuconfig exits with a python stack trace if NULL is provided as input character, therefore ignore NULL as an input character to prevent this behaviour. A NULL character may be given accidentally by the user through the following ways: - Pressing `Win` key on keyboard (Windows only) - Pressing `<CTRL>-@` / `<CTRL>-2`. Signed-off-by: Torsten Rasmussen <[email protected]>
tejlmand
added a commit
to tejlmand/zephyr
that referenced
this issue
Mar 15, 2021
Fixes: zephyrproject-rtos#33212 Upstream PR: ulfalizer/Kconfiglib#103 Ignoring when user inputs NULL in a text field. menuconfig exits with a python stack trace if NULL is provided as input character, therefore ignore NULL as an input character to prevent this behaviour. A NULL character may be given accidentally by the user through the following ways: - Pressing `Win` key on keyboard (Windows only) - Pressing `<CTRL>-@` / `<CTRL>-2`. Signed-off-by: Torsten Rasmussen <[email protected]>
carlescufi
pushed a commit
that referenced
this issue
Apr 7, 2021
Fixes: #33212 Upstream PR: ulfalizer/Kconfiglib#103 Ignoring when user inputs NULL in a text field. menuconfig exits with a python stack trace if NULL is provided as input character, therefore ignore NULL as an input character to prevent this behaviour. A NULL character may be given accidentally by the user through the following ways: - Pressing `Win` key on keyboard (Windows only) - Pressing `<CTRL>-@` / `<CTRL>-2`. Signed-off-by: Torsten Rasmussen <[email protected]>
tejlmand
added a commit
to tejlmand/Kconfiglib
that referenced
this issue
Oct 25, 2024
Fixes: zephyrproject-rtos/zephyr#33212 Ignoring when user inputs NULL in a text field. menuconfig exits with a python stack trace if NULL is provided as input character, therefore ignore NULL as an input character to prevent this behaviour. A NULL character may be given accidentally by the user through the following ways: - Pressing `Win` key on keyboard (Windows only) - Pressing `<CTRL>-@` / `<CTRL>-2`. Signed-off-by: Torsten Rasmussen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: Build System
area: Kconfig
bug
The issue is a bug, or the PR is fixing a bug
priority: low
Low impact/importance bug
Describe the bug
Configure a project for any board, run
ninja menuconfig
and press the windows key, it exits out with an error when it should handle it gracefully and ignore the inputExpected behavior
For it to not cause an exception
Impact
Annoyance
Logs and console output
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: