How to change keyboard layout in gnome 3 from command line












10














I am using gnome 3.22.1 but problem exists since 3.18.



Before that (don't remember the exact version) I was able to switch keyboard layout using xkb-witch, simple application that uses X.org bindings under the hood.



After 3.18 if you run xkb-switch, the keyboard layout won't be switched in gnome. Further investigation have shown that layout switching is working, but for a very short amount of time.



If you run this script:



for i in $(seq 1000); do
lang=$(xkb-switch -s ru; xkb-switch);
if [[ "$lang" == "ru" ]]; then
echo $lang;
fi;
done


You will get from 3 to 20 "successfull" layout switchings, depending on how lucky you are.



After googling this problem I the following advice:



gsettings set org.gnome.desktop.input-sources current 0


The setting is being changed, but the layout stays the same.



I have found one "hacky" method to change the layout:



setxkbmap us,ru
setxkbmap ru,us


but the gnome shell isn't aware of that change, and shows wrong language in layout indicator.



I've posted about this problem (sorry, not enough reputation, https ://bbs.archlinux.org/viewtopic.php?pid=1657582 https ://github.com/ierton/xkb-switch/issues/15), but had no luck getting any good answers.



And at this point I'm stuck. I'm not skilled enough to identify the problem in gnome shell code. I'm not even sure it is it's(gnome shell's) problem.



What I want is a gnome-aware way to switch keyboard layout from terminal. Can someone point me in the right direction? Should I file this as a bug (especially the fact that keyboard layout cannot be changed through gsettings)?










share|improve this question



























    10














    I am using gnome 3.22.1 but problem exists since 3.18.



    Before that (don't remember the exact version) I was able to switch keyboard layout using xkb-witch, simple application that uses X.org bindings under the hood.



    After 3.18 if you run xkb-switch, the keyboard layout won't be switched in gnome. Further investigation have shown that layout switching is working, but for a very short amount of time.



    If you run this script:



    for i in $(seq 1000); do
    lang=$(xkb-switch -s ru; xkb-switch);
    if [[ "$lang" == "ru" ]]; then
    echo $lang;
    fi;
    done


    You will get from 3 to 20 "successfull" layout switchings, depending on how lucky you are.



    After googling this problem I the following advice:



    gsettings set org.gnome.desktop.input-sources current 0


    The setting is being changed, but the layout stays the same.



    I have found one "hacky" method to change the layout:



    setxkbmap us,ru
    setxkbmap ru,us


    but the gnome shell isn't aware of that change, and shows wrong language in layout indicator.



    I've posted about this problem (sorry, not enough reputation, https ://bbs.archlinux.org/viewtopic.php?pid=1657582 https ://github.com/ierton/xkb-switch/issues/15), but had no luck getting any good answers.



    And at this point I'm stuck. I'm not skilled enough to identify the problem in gnome shell code. I'm not even sure it is it's(gnome shell's) problem.



    What I want is a gnome-aware way to switch keyboard layout from terminal. Can someone point me in the right direction? Should I file this as a bug (especially the fact that keyboard layout cannot be changed through gsettings)?










    share|improve this question

























      10












      10








      10


      1





      I am using gnome 3.22.1 but problem exists since 3.18.



      Before that (don't remember the exact version) I was able to switch keyboard layout using xkb-witch, simple application that uses X.org bindings under the hood.



      After 3.18 if you run xkb-switch, the keyboard layout won't be switched in gnome. Further investigation have shown that layout switching is working, but for a very short amount of time.



      If you run this script:



      for i in $(seq 1000); do
      lang=$(xkb-switch -s ru; xkb-switch);
      if [[ "$lang" == "ru" ]]; then
      echo $lang;
      fi;
      done


      You will get from 3 to 20 "successfull" layout switchings, depending on how lucky you are.



      After googling this problem I the following advice:



      gsettings set org.gnome.desktop.input-sources current 0


      The setting is being changed, but the layout stays the same.



      I have found one "hacky" method to change the layout:



      setxkbmap us,ru
      setxkbmap ru,us


      but the gnome shell isn't aware of that change, and shows wrong language in layout indicator.



      I've posted about this problem (sorry, not enough reputation, https ://bbs.archlinux.org/viewtopic.php?pid=1657582 https ://github.com/ierton/xkb-switch/issues/15), but had no luck getting any good answers.



      And at this point I'm stuck. I'm not skilled enough to identify the problem in gnome shell code. I'm not even sure it is it's(gnome shell's) problem.



      What I want is a gnome-aware way to switch keyboard layout from terminal. Can someone point me in the right direction? Should I file this as a bug (especially the fact that keyboard layout cannot be changed through gsettings)?










      share|improve this question













      I am using gnome 3.22.1 but problem exists since 3.18.



      Before that (don't remember the exact version) I was able to switch keyboard layout using xkb-witch, simple application that uses X.org bindings under the hood.



      After 3.18 if you run xkb-switch, the keyboard layout won't be switched in gnome. Further investigation have shown that layout switching is working, but for a very short amount of time.



      If you run this script:



      for i in $(seq 1000); do
      lang=$(xkb-switch -s ru; xkb-switch);
      if [[ "$lang" == "ru" ]]; then
      echo $lang;
      fi;
      done


      You will get from 3 to 20 "successfull" layout switchings, depending on how lucky you are.



      After googling this problem I the following advice:



      gsettings set org.gnome.desktop.input-sources current 0


      The setting is being changed, but the layout stays the same.



      I have found one "hacky" method to change the layout:



      setxkbmap us,ru
      setxkbmap ru,us


      but the gnome shell isn't aware of that change, and shows wrong language in layout indicator.



      I've posted about this problem (sorry, not enough reputation, https ://bbs.archlinux.org/viewtopic.php?pid=1657582 https ://github.com/ierton/xkb-switch/issues/15), but had no luck getting any good answers.



      And at this point I'm stuck. I'm not skilled enough to identify the problem in gnome shell code. I'm not even sure it is it's(gnome shell's) problem.



      What I want is a gnome-aware way to switch keyboard layout from terminal. Can someone point me in the right direction? Should I file this as a bug (especially the fact that keyboard layout cannot be changed through gsettings)?







      gnome3 keyboard-layout






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Oct 17 '16 at 16:02









      RGBDRGBD

      5113




      5113






















          4 Answers
          4






          active

          oldest

          votes


















          4














          Since gnome-shell exposes a JS eval interface on DBus which has access to all variables, the feat is possible with the following command:



          gdbus call --session --dest org.gnome.Shell 
          --object-path /org/gnome/Shell
          --method org.gnome.Shell.Eval
          "imports.ui.status.keyboard.getInputSourceManager().inputSources[0].activate()"


          Which will activate 0th layout, and so forth.



          Credit.





          And this is how to switch to last used input method (from comments):



          gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Shell 
          --method org.gnome.Shell.Eval "imports.ui.status.keyboard.getInputSourceManager()._mruSources[1].activate()"





          share|improve this answer























          • Thank you for your answer – it saved me a lot of googling! And this is how to switch to last used input method: gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Shell --method org.gnome.Shell.Eval "imports.ui.status.keyboard.getInputSourceManager()._mruSources[1].activate()"
            – Envek
            8 hours ago










          • @Envek thanks, that's a useful addition!
            – sanmai
            2 hours ago



















          3














          Using gsettings.



          Setting org.gnome.desktop.input-sources.sources to the null list, "", allows you to use the X server keyboard configuration without gnome-shell trying to configure it, so you could be able to do as before.



          $ gsettings set org.gnome.desktop.input-sources sources ''





          share|improve this answer































            2





            +25









            If you are using IBus as your input method (which is a likely default), you can change your input using the ibus command:



            # Set the layout to US English
            ibus engine xkb:us::eng
            # Set the input method to Japanese Mozc IME
            ibus engine mozc-jp
            # Set the layout to Russian
            ibus engine xkb:ru::rus


            You can see all available layouts with the ibus list-engine command.



            It must be noted this approach does not change the language indicator, although it works reliably otherwise.






            share|improve this answer























            • That's same as setxkbmap us - with no way to change layout using standard shortcuts after that.
              – sanmai
              Jun 16 '18 at 2:32










            • @sanmai Not quite the same — it's impossible to switch to languages needing IME (Japanese, Chinese, etc) using setxkbmap. Furthermore, setxkbmap can act plain buggy in modern WM environments, see the question for details on this.
              – undercat
              Jun 16 '18 at 3:17












            • Can't comment on the default shortcuts not working though — I'm using custom ones for every layout that I use.
              – undercat
              Jun 16 '18 at 3:20










            • OK, not the same, but still I can't use the default switch. As you may know, there's only as much extra keys on a Japanese keyboard, for other layouts I still have to use the default switch.
              – sanmai
              Jun 16 '18 at 3:22



















            0














            I think you should try sudo dpkg-reconfigure keyboard-configuration






            share|improve this answer





















              Your Answer








              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "106"
              };
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function() {
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled) {
              StackExchange.using("snippets", function() {
              createEditor();
              });
              }
              else {
              createEditor();
              }
              });

              function createEditor() {
              StackExchange.prepareEditor({
              heartbeatType: 'answer',
              autoActivateHeartbeat: false,
              convertImagesToLinks: false,
              noModals: true,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: null,
              bindNavPrevention: true,
              postfix: "",
              imageUploader: {
              brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
              contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
              allowUrls: true
              },
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              });


              }
              });














              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f316998%2fhow-to-change-keyboard-layout-in-gnome-3-from-command-line%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              4 Answers
              4






              active

              oldest

              votes








              4 Answers
              4






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              4














              Since gnome-shell exposes a JS eval interface on DBus which has access to all variables, the feat is possible with the following command:



              gdbus call --session --dest org.gnome.Shell 
              --object-path /org/gnome/Shell
              --method org.gnome.Shell.Eval
              "imports.ui.status.keyboard.getInputSourceManager().inputSources[0].activate()"


              Which will activate 0th layout, and so forth.



              Credit.





              And this is how to switch to last used input method (from comments):



              gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Shell 
              --method org.gnome.Shell.Eval "imports.ui.status.keyboard.getInputSourceManager()._mruSources[1].activate()"





              share|improve this answer























              • Thank you for your answer – it saved me a lot of googling! And this is how to switch to last used input method: gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Shell --method org.gnome.Shell.Eval "imports.ui.status.keyboard.getInputSourceManager()._mruSources[1].activate()"
                – Envek
                8 hours ago










              • @Envek thanks, that's a useful addition!
                – sanmai
                2 hours ago
















              4














              Since gnome-shell exposes a JS eval interface on DBus which has access to all variables, the feat is possible with the following command:



              gdbus call --session --dest org.gnome.Shell 
              --object-path /org/gnome/Shell
              --method org.gnome.Shell.Eval
              "imports.ui.status.keyboard.getInputSourceManager().inputSources[0].activate()"


              Which will activate 0th layout, and so forth.



              Credit.





              And this is how to switch to last used input method (from comments):



              gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Shell 
              --method org.gnome.Shell.Eval "imports.ui.status.keyboard.getInputSourceManager()._mruSources[1].activate()"





              share|improve this answer























              • Thank you for your answer – it saved me a lot of googling! And this is how to switch to last used input method: gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Shell --method org.gnome.Shell.Eval "imports.ui.status.keyboard.getInputSourceManager()._mruSources[1].activate()"
                – Envek
                8 hours ago










              • @Envek thanks, that's a useful addition!
                – sanmai
                2 hours ago














              4












              4








              4






              Since gnome-shell exposes a JS eval interface on DBus which has access to all variables, the feat is possible with the following command:



              gdbus call --session --dest org.gnome.Shell 
              --object-path /org/gnome/Shell
              --method org.gnome.Shell.Eval
              "imports.ui.status.keyboard.getInputSourceManager().inputSources[0].activate()"


              Which will activate 0th layout, and so forth.



              Credit.





              And this is how to switch to last used input method (from comments):



              gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Shell 
              --method org.gnome.Shell.Eval "imports.ui.status.keyboard.getInputSourceManager()._mruSources[1].activate()"





              share|improve this answer














              Since gnome-shell exposes a JS eval interface on DBus which has access to all variables, the feat is possible with the following command:



              gdbus call --session --dest org.gnome.Shell 
              --object-path /org/gnome/Shell
              --method org.gnome.Shell.Eval
              "imports.ui.status.keyboard.getInputSourceManager().inputSources[0].activate()"


              Which will activate 0th layout, and so forth.



              Credit.





              And this is how to switch to last used input method (from comments):



              gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Shell 
              --method org.gnome.Shell.Eval "imports.ui.status.keyboard.getInputSourceManager()._mruSources[1].activate()"






              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited 2 hours ago

























              answered Jun 13 '18 at 8:31









              sanmaisanmai

              567515




              567515












              • Thank you for your answer – it saved me a lot of googling! And this is how to switch to last used input method: gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Shell --method org.gnome.Shell.Eval "imports.ui.status.keyboard.getInputSourceManager()._mruSources[1].activate()"
                – Envek
                8 hours ago










              • @Envek thanks, that's a useful addition!
                – sanmai
                2 hours ago


















              • Thank you for your answer – it saved me a lot of googling! And this is how to switch to last used input method: gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Shell --method org.gnome.Shell.Eval "imports.ui.status.keyboard.getInputSourceManager()._mruSources[1].activate()"
                – Envek
                8 hours ago










              • @Envek thanks, that's a useful addition!
                – sanmai
                2 hours ago
















              Thank you for your answer – it saved me a lot of googling! And this is how to switch to last used input method: gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Shell --method org.gnome.Shell.Eval "imports.ui.status.keyboard.getInputSourceManager()._mruSources[1].activate()"
              – Envek
              8 hours ago




              Thank you for your answer – it saved me a lot of googling! And this is how to switch to last used input method: gdbus call --session --dest org.gnome.Shell --object-path /org/gnome/Shell --method org.gnome.Shell.Eval "imports.ui.status.keyboard.getInputSourceManager()._mruSources[1].activate()"
              – Envek
              8 hours ago












              @Envek thanks, that's a useful addition!
              – sanmai
              2 hours ago




              @Envek thanks, that's a useful addition!
              – sanmai
              2 hours ago













              3














              Using gsettings.



              Setting org.gnome.desktop.input-sources.sources to the null list, "", allows you to use the X server keyboard configuration without gnome-shell trying to configure it, so you could be able to do as before.



              $ gsettings set org.gnome.desktop.input-sources sources ''





              share|improve this answer




























                3














                Using gsettings.



                Setting org.gnome.desktop.input-sources.sources to the null list, "", allows you to use the X server keyboard configuration without gnome-shell trying to configure it, so you could be able to do as before.



                $ gsettings set org.gnome.desktop.input-sources sources ''





                share|improve this answer


























                  3












                  3








                  3






                  Using gsettings.



                  Setting org.gnome.desktop.input-sources.sources to the null list, "", allows you to use the X server keyboard configuration without gnome-shell trying to configure it, so you could be able to do as before.



                  $ gsettings set org.gnome.desktop.input-sources sources ''





                  share|improve this answer














                  Using gsettings.



                  Setting org.gnome.desktop.input-sources.sources to the null list, "", allows you to use the X server keyboard configuration without gnome-shell trying to configure it, so you could be able to do as before.



                  $ gsettings set org.gnome.desktop.input-sources sources ''






                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Oct 17 '16 at 21:01

























                  answered Oct 17 '16 at 20:52









                  xaexae

                  1,37376




                  1,37376























                      2





                      +25









                      If you are using IBus as your input method (which is a likely default), you can change your input using the ibus command:



                      # Set the layout to US English
                      ibus engine xkb:us::eng
                      # Set the input method to Japanese Mozc IME
                      ibus engine mozc-jp
                      # Set the layout to Russian
                      ibus engine xkb:ru::rus


                      You can see all available layouts with the ibus list-engine command.



                      It must be noted this approach does not change the language indicator, although it works reliably otherwise.






                      share|improve this answer























                      • That's same as setxkbmap us - with no way to change layout using standard shortcuts after that.
                        – sanmai
                        Jun 16 '18 at 2:32










                      • @sanmai Not quite the same — it's impossible to switch to languages needing IME (Japanese, Chinese, etc) using setxkbmap. Furthermore, setxkbmap can act plain buggy in modern WM environments, see the question for details on this.
                        – undercat
                        Jun 16 '18 at 3:17












                      • Can't comment on the default shortcuts not working though — I'm using custom ones for every layout that I use.
                        – undercat
                        Jun 16 '18 at 3:20










                      • OK, not the same, but still I can't use the default switch. As you may know, there's only as much extra keys on a Japanese keyboard, for other layouts I still have to use the default switch.
                        – sanmai
                        Jun 16 '18 at 3:22
















                      2





                      +25









                      If you are using IBus as your input method (which is a likely default), you can change your input using the ibus command:



                      # Set the layout to US English
                      ibus engine xkb:us::eng
                      # Set the input method to Japanese Mozc IME
                      ibus engine mozc-jp
                      # Set the layout to Russian
                      ibus engine xkb:ru::rus


                      You can see all available layouts with the ibus list-engine command.



                      It must be noted this approach does not change the language indicator, although it works reliably otherwise.






                      share|improve this answer























                      • That's same as setxkbmap us - with no way to change layout using standard shortcuts after that.
                        – sanmai
                        Jun 16 '18 at 2:32










                      • @sanmai Not quite the same — it's impossible to switch to languages needing IME (Japanese, Chinese, etc) using setxkbmap. Furthermore, setxkbmap can act plain buggy in modern WM environments, see the question for details on this.
                        – undercat
                        Jun 16 '18 at 3:17












                      • Can't comment on the default shortcuts not working though — I'm using custom ones for every layout that I use.
                        – undercat
                        Jun 16 '18 at 3:20










                      • OK, not the same, but still I can't use the default switch. As you may know, there's only as much extra keys on a Japanese keyboard, for other layouts I still have to use the default switch.
                        – sanmai
                        Jun 16 '18 at 3:22














                      2





                      +25







                      2





                      +25



                      2




                      +25




                      If you are using IBus as your input method (which is a likely default), you can change your input using the ibus command:



                      # Set the layout to US English
                      ibus engine xkb:us::eng
                      # Set the input method to Japanese Mozc IME
                      ibus engine mozc-jp
                      # Set the layout to Russian
                      ibus engine xkb:ru::rus


                      You can see all available layouts with the ibus list-engine command.



                      It must be noted this approach does not change the language indicator, although it works reliably otherwise.






                      share|improve this answer














                      If you are using IBus as your input method (which is a likely default), you can change your input using the ibus command:



                      # Set the layout to US English
                      ibus engine xkb:us::eng
                      # Set the input method to Japanese Mozc IME
                      ibus engine mozc-jp
                      # Set the layout to Russian
                      ibus engine xkb:ru::rus


                      You can see all available layouts with the ibus list-engine command.



                      It must be noted this approach does not change the language indicator, although it works reliably otherwise.







                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Jun 13 '18 at 15:23

























                      answered Jun 13 '18 at 15:12









                      undercatundercat

                      843314




                      843314












                      • That's same as setxkbmap us - with no way to change layout using standard shortcuts after that.
                        – sanmai
                        Jun 16 '18 at 2:32










                      • @sanmai Not quite the same — it's impossible to switch to languages needing IME (Japanese, Chinese, etc) using setxkbmap. Furthermore, setxkbmap can act plain buggy in modern WM environments, see the question for details on this.
                        – undercat
                        Jun 16 '18 at 3:17












                      • Can't comment on the default shortcuts not working though — I'm using custom ones for every layout that I use.
                        – undercat
                        Jun 16 '18 at 3:20










                      • OK, not the same, but still I can't use the default switch. As you may know, there's only as much extra keys on a Japanese keyboard, for other layouts I still have to use the default switch.
                        – sanmai
                        Jun 16 '18 at 3:22


















                      • That's same as setxkbmap us - with no way to change layout using standard shortcuts after that.
                        – sanmai
                        Jun 16 '18 at 2:32










                      • @sanmai Not quite the same — it's impossible to switch to languages needing IME (Japanese, Chinese, etc) using setxkbmap. Furthermore, setxkbmap can act plain buggy in modern WM environments, see the question for details on this.
                        – undercat
                        Jun 16 '18 at 3:17












                      • Can't comment on the default shortcuts not working though — I'm using custom ones for every layout that I use.
                        – undercat
                        Jun 16 '18 at 3:20










                      • OK, not the same, but still I can't use the default switch. As you may know, there's only as much extra keys on a Japanese keyboard, for other layouts I still have to use the default switch.
                        – sanmai
                        Jun 16 '18 at 3:22
















                      That's same as setxkbmap us - with no way to change layout using standard shortcuts after that.
                      – sanmai
                      Jun 16 '18 at 2:32




                      That's same as setxkbmap us - with no way to change layout using standard shortcuts after that.
                      – sanmai
                      Jun 16 '18 at 2:32












                      @sanmai Not quite the same — it's impossible to switch to languages needing IME (Japanese, Chinese, etc) using setxkbmap. Furthermore, setxkbmap can act plain buggy in modern WM environments, see the question for details on this.
                      – undercat
                      Jun 16 '18 at 3:17






                      @sanmai Not quite the same — it's impossible to switch to languages needing IME (Japanese, Chinese, etc) using setxkbmap. Furthermore, setxkbmap can act plain buggy in modern WM environments, see the question for details on this.
                      – undercat
                      Jun 16 '18 at 3:17














                      Can't comment on the default shortcuts not working though — I'm using custom ones for every layout that I use.
                      – undercat
                      Jun 16 '18 at 3:20




                      Can't comment on the default shortcuts not working though — I'm using custom ones for every layout that I use.
                      – undercat
                      Jun 16 '18 at 3:20












                      OK, not the same, but still I can't use the default switch. As you may know, there's only as much extra keys on a Japanese keyboard, for other layouts I still have to use the default switch.
                      – sanmai
                      Jun 16 '18 at 3:22




                      OK, not the same, but still I can't use the default switch. As you may know, there's only as much extra keys on a Japanese keyboard, for other layouts I still have to use the default switch.
                      – sanmai
                      Jun 16 '18 at 3:22











                      0














                      I think you should try sudo dpkg-reconfigure keyboard-configuration






                      share|improve this answer


























                        0














                        I think you should try sudo dpkg-reconfigure keyboard-configuration






                        share|improve this answer
























                          0












                          0








                          0






                          I think you should try sudo dpkg-reconfigure keyboard-configuration






                          share|improve this answer












                          I think you should try sudo dpkg-reconfigure keyboard-configuration







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Jun 19 '18 at 17:01









                          Romain L.Romain L.

                          213




                          213






























                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Unix & Linux Stack Exchange!


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.





                              Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                              Please pay close attention to the following guidance:


                              • Please be sure to answer the question. Provide details and share your research!

                              But avoid



                              • Asking for help, clarification, or responding to other answers.

                              • Making statements based on opinion; back them up with references or personal experience.


                              To learn more, see our tips on writing great answers.




                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function () {
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f316998%2fhow-to-change-keyboard-layout-in-gnome-3-from-command-line%23new-answer', 'question_page');
                              }
                              );

                              Post as a guest















                              Required, but never shown





















































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown

































                              Required, but never shown














                              Required, but never shown












                              Required, but never shown







                              Required, but never shown







                              Popular posts from this blog

                              Accessing regular linux commands in Huawei's Dopra Linux

                              Can't connect RFCOMM socket: Host is down

                              Kernel panic - not syncing: Fatal Exception in Interrupt