<!-- See our full bug reporting guidelines at https://inkscape.org/contribute/report-bugs/ Writing a good bug report will ensure we'll be able to help efficiently. 🙂 --> #### Summary: <!-- Summarize the issue/suggestion concisely: --> Changing keyboard-issues in Preferences cause that Commands-bar disappears, which thereafter can't be restored. #### Steps to reproduce: <!-- Describe what you did (step-by-step) so we can reproduce: --> Let's assume, you start inkscape as it would be for the first time. (delete preferences.xml in "..AppData/Roaming/Inkscape.." first). Enter "Preferences->Interface->Keyboard". Click on "reset" or change some Shortcut. #### What happened? Commands-Bar disappears #### What should have happened? Commands-Bar is still there #### Sample attachments: First "preferences.xml" after starting Inkscape for first time: [First_preferences.xml](/uploads/de40c71f4740b9807cc1ea2b83000d46/First_preferences.xml) "preferences.xml" after error occurred: [With_Error_preferences.xml](/uploads/8681454ec8ca8c48d1ed360613cd0d98/With_Error_preferences.xml) <!-- Attach the sample file(s) highlighting the issue, if appropriate. --> #### Version Info: - Inkscape Version: Inkscape 1.1 (c68e22c387, 2021-05-23) GLib version: 2.68.2 GTK version: 3.24.29 glibmm version: 2.66.0 gtkmm version: 3.24.3 libxml2 version: 2.9.12 libxslt version: 1.1.34 Cairo version: 1.17.4 Pango version: 1.48.5 HarfBuzz version: 2.8.1 Poppler version: 20.12.1 - Operating System: Win10Home - Operating System version:64bit, 21H1 Build 19043.1023 <!-- ❤️ Thank you for filling in a new bug report, we appreciate the help! ❤️ Please be patient while we try to find the time to look into your issue. Remember that Inkscape is developed by volunteers in their spare time, we'll try our best to respond to all reports. --> <!-- Please be careful when/after writing # for example in logs, code, or versions of linux - use inline code span - single backticks (`) before and after it, like this - `#1618` - use multi-line code block - triple backticks (```) to fence/enclose console logs - attach long logs as a text file. -->