How to disable Ctrl+Shift+U in Ubuntu Linux?












46















ctrl+shift+u is a combined shortcut key in Eclipse.



But when I press it, it shows up a u, just like input with an underline. I guess this shortcut has been declared by Ubuntu, so I can't use it.



I used to solve this problem by typing capslock first. Is there any better method?










share|improve this question















migrated from stackoverflow.com Nov 18 '11 at 1:15


This question came from our site for professional and enthusiast programmers.























    46















    ctrl+shift+u is a combined shortcut key in Eclipse.



    But when I press it, it shows up a u, just like input with an underline. I guess this shortcut has been declared by Ubuntu, so I can't use it.



    I used to solve this problem by typing capslock first. Is there any better method?










    share|improve this question















    migrated from stackoverflow.com Nov 18 '11 at 1:15


    This question came from our site for professional and enthusiast programmers.





















      46












      46








      46


      15






      ctrl+shift+u is a combined shortcut key in Eclipse.



      But when I press it, it shows up a u, just like input with an underline. I guess this shortcut has been declared by Ubuntu, so I can't use it.



      I used to solve this problem by typing capslock first. Is there any better method?










      share|improve this question
















      ctrl+shift+u is a combined shortcut key in Eclipse.



      But when I press it, it shows up a u, just like input with an underline. I guess this shortcut has been declared by Ubuntu, so I can't use it.



      I used to solve this problem by typing capslock first. Is there any better method?







      ubuntu keyboard-shortcuts eclipse






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 18 '11 at 13:49









      slhck

      160k47444466




      160k47444466










      asked Nov 18 '11 at 1:12









      Frank ChengFrank Cheng

      333135




      333135




      migrated from stackoverflow.com Nov 18 '11 at 1:15


      This question came from our site for professional and enthusiast programmers.









      migrated from stackoverflow.com Nov 18 '11 at 1:15


      This question came from our site for professional and enthusiast programmers.
























          8 Answers
          8






          active

          oldest

          votes


















          40














          Found a way to unbind it on Ubuntu 13.10.



          Go to Language Support on System Settings and change the Keyboard input method system to none



          Then restart the system.






          share|improve this answer



















          • 11





            Just logging out and back in works for me.

            – Martin
            Apr 29 '14 at 10:13











          • In latest Ubuntu versions you just go Language Support then Keyboard input method system is available

            – vmoh_ir
            May 30 '18 at 21:26






          • 8





            This did not work for me on Ubuntu 18.0.4 LTS. Any ideas why?

            – Pytry
            Jun 19 '18 at 22:05






          • 1





            why Ubuntu made it so difficult to disable keyboard input system? keystrokes entered going directly to program should be the default anyway.

            – weima
            Jul 18 '18 at 15:08






          • 2





            does not work for me on ubuntu 18.04

            – iRaS
            Aug 22 '18 at 8:59



















          4














          Changing the input method as PutzKipa explains actually fixes the problem.



          However, I've failed to find any configuration panel under KDE ubuntu 14.04 to do the job, and the standard im-config utility seems broken. I finally succeeded by creating a file ~/.xinputrc that contains a single line:



          run_im xim


          then logout/login. This chooses xim as the input method (ibus is the default). If you remove your ~/.xinputrc, then im-config can list the input methods available, even if it fails to select one.






          share|improve this answer



















          • 1





            this also doesnt seem to work in 16.04 LTS

            – weima
            Jul 18 '18 at 15:10



















          2














          For Ubuntu 18.04.



          I struggled with this problem for two days. I tried all the methods listed here earlier. And it looks like I came up with a solution. But it is very unstable and has bugs.



          The basic idea is this: in the system settings you can specify the command that is started by the Ctrl+Shift+U key combination.



          Note: if you specify false as the command, the combination will not work at all.



          However, we can specify the path to the script as the command, in which we will simulate pressing the same key combination.



          To simulate keystrokes, I tried the xdotool (apt install xdotool) and the xte (apt install xautomation).
          Both options were unstable. However, xte turned out to be more flexible for me.



          Example with xte




          • Create a file /home/username/shortcut.sh

          • Add permission to execute: chmod u+x /home/username/shortcut.sh

          • Specify the path to the script as a command for the Ctrl+Shift+U key combination in the keyboard settings


          Here is an example script:



          #!/bin/sh
          # Make a small delay in order to have time to release the keys.
          sleep 0.2

          # Simulate the release of just pressed keys, if they are still pressed.
          xte 'keyup u' 'keyup Shift_L' 'keyup Control_L'

          # Hack: Caps_Lock is used so that the system does not intercept this combination.
          # You can try to remove it if it hinders you.
          xte 'key Caps_Lock'

          # Simulate pressing a key combination
          xte 'keydown Shift_L' 'keydown Control_L' 'key u'

          # Simulate releasing a key combination
          xte 'keyup Shift_L' 'keyup Control_L'

          # Restore Caps_Lock to the previous state.
          xte 'key Caps_Lock'


          I tested this in PhpStorm 2018.2 EAP Build #PS-182.3458.35 and I can say that it works, but with some caveats:




          • this works slowly (on my rather old PC)

          • during the execution of the script, it is better not to press any keys

          • sometimes it may not work

          • sometimes it can enter an infinite loop. Therefore, it's better to add a check to the script that the script is already running.


          In general, if you do not often use this combination, then this solution may suit you.



          But, probably, someone will come up with a better and more stable solution.



          I hope this idea will help someone.






          share|improve this answer































            1





            +50









            Try:



            export GTK_IM_MODULE="gtk-im-context-simple"


            and then run Eclipse from the same shell. Or if that doesn't work,



            export GTK_IM_MODULE="xim"


            (This test only works entering running the export command and then Eclipse from the same shell command line, it won't change anything if you use a desktop shortcut or the Applications menu, or run Eclipse from a new shell.)



            If either test works, you can make the change system-wide by adding it to /etc/environment, or per-user in ~/.gnomerc. (The export command doesn't go in those files, just a new line with GTK_IM_MODULE="xim" or GTK_IM_MODULE="gtk-im-context-simple".)



            It sounds like this behavior comes from GTK's input mappings as described here: https://developer.gnome.org/gtk3/unstable/GtkIMContext.html




            ... This is called preediting, and an input method may provide feedback about this process by displaying the intermediate composition states as preedit text. For instance, the default GTK+ input method implements the input of arbitrary Unicode code points by holding down the Control and Shift keys and then typing “U” followed by the hexadecimal digits of the code point. When releasing the Control and Shift keys, preediting ends and the character is inserted as text. Ctrl+Shift+u20AC for example results in the € sign.




            GTK is used by a whole lot of common apps in Ubuntu, including Eclipse.






            share|improve this answer

































              1














              Ubuntu 14.04/18.04 Solution



              recently upgrade to 18.04 and fight my way to solve this issue.




              1. open search using super key

              2. go to language support

              3. click Keyboard input method system dropdown menu and choose none


              Language Support Menu





              1. dont forget to click - apply system wide

              2. close the window (wont activate until you do)

              3. reboot (logout might be enough)


              Credit goes to reverse issue on askubuntu - for some reason someone wants to enable this shortcut.






              share|improve this answer


























              • This solution did not work for me. Should I also reboot? (I have too many windows opened now and cannot test it quickly)

                – desa
                Sep 30 '18 at 11:58











              • works after reboot (maybe logout is enough) @desa thanks ill update the answer

                – ShmulikA
                Oct 2 '18 at 11:21











              • does not solve the problem in 18.04

                – James
                Nov 21 '18 at 14:55



















              1














              Ubuntu 18.04



              Running into this problem on Ubuntu 18.04, I've tried all suggestion above, but unfortunately none of them worked. I ended up uninstalling the ibus package.



              Background / sidenotes



              I tried to disable IBus using




              1. the Language Support menu


              2. im-config (configures ~/.xinputrc)


              3. sudo im-config (configures /etc/X11/xinit/xinputrc)


              I noticed however that no matter what config I tried, the ibus daemon was running everytime after I had rebooted.






              share|improve this answer































                1















                1. Run ibus-setup from the terminal (or open IBus Preferences).

                2. Go to “Emoji”.

                3. Next to “Unicode code point:”, click on the three dots (i.e. ...).

                4. In the dialog, click “Delete”, then “OK”.

                5. Close the IBus Preferences window.






                share|improve this answer































                  0














                  Open a terminal window.



                  cd ~/.gconf/desktop/gnome/interface
                  gedit %gconf.xml


                  Change the show_unicode_menu from true to false.



                  Save, Log out and back in.






                  share|improve this answer
























                  • /desktop/gnome/interface/show_unicode_menu is already disabled (false) Question is about keyboard shorcut, not menu.

                    – MariuszS
                    Aug 22 '13 at 17:15













                  • good use of time, downvoting an answer almost two years old.

                    – John Barry
                    Aug 22 '13 at 18:42






                  • 7





                    Two years later this question is still valid... so why not?

                    – MariuszS
                    Aug 23 '13 at 12:13











                  • disabling show_unicode_menu works on elementaryOS, though I use a different tool to do the job: dconf-editor. This point me to the correct key anyway, thank you.

                    – Hoang Tran
                    Jul 10 '16 at 10:08











                  Your Answer








                  StackExchange.ready(function() {
                  var channelOptions = {
                  tags: "".split(" "),
                  id: "3"
                  };
                  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: true,
                  noModals: true,
                  showLowRepImageUploadWarning: true,
                  reputationToPostImages: 10,
                  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%2fsuperuser.com%2fquestions%2f358749%2fhow-to-disable-ctrlshiftu-in-ubuntu-linux%23new-answer', 'question_page');
                  }
                  );

                  Post as a guest















                  Required, but never shown

























                  8 Answers
                  8






                  active

                  oldest

                  votes








                  8 Answers
                  8






                  active

                  oldest

                  votes









                  active

                  oldest

                  votes






                  active

                  oldest

                  votes









                  40














                  Found a way to unbind it on Ubuntu 13.10.



                  Go to Language Support on System Settings and change the Keyboard input method system to none



                  Then restart the system.






                  share|improve this answer



















                  • 11





                    Just logging out and back in works for me.

                    – Martin
                    Apr 29 '14 at 10:13











                  • In latest Ubuntu versions you just go Language Support then Keyboard input method system is available

                    – vmoh_ir
                    May 30 '18 at 21:26






                  • 8





                    This did not work for me on Ubuntu 18.0.4 LTS. Any ideas why?

                    – Pytry
                    Jun 19 '18 at 22:05






                  • 1





                    why Ubuntu made it so difficult to disable keyboard input system? keystrokes entered going directly to program should be the default anyway.

                    – weima
                    Jul 18 '18 at 15:08






                  • 2





                    does not work for me on ubuntu 18.04

                    – iRaS
                    Aug 22 '18 at 8:59
















                  40














                  Found a way to unbind it on Ubuntu 13.10.



                  Go to Language Support on System Settings and change the Keyboard input method system to none



                  Then restart the system.






                  share|improve this answer



















                  • 11





                    Just logging out and back in works for me.

                    – Martin
                    Apr 29 '14 at 10:13











                  • In latest Ubuntu versions you just go Language Support then Keyboard input method system is available

                    – vmoh_ir
                    May 30 '18 at 21:26






                  • 8





                    This did not work for me on Ubuntu 18.0.4 LTS. Any ideas why?

                    – Pytry
                    Jun 19 '18 at 22:05






                  • 1





                    why Ubuntu made it so difficult to disable keyboard input system? keystrokes entered going directly to program should be the default anyway.

                    – weima
                    Jul 18 '18 at 15:08






                  • 2





                    does not work for me on ubuntu 18.04

                    – iRaS
                    Aug 22 '18 at 8:59














                  40












                  40








                  40







                  Found a way to unbind it on Ubuntu 13.10.



                  Go to Language Support on System Settings and change the Keyboard input method system to none



                  Then restart the system.






                  share|improve this answer













                  Found a way to unbind it on Ubuntu 13.10.



                  Go to Language Support on System Settings and change the Keyboard input method system to none



                  Then restart the system.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 7 '13 at 14:31









                  PutzKipaPutzKipa

                  51654




                  51654








                  • 11





                    Just logging out and back in works for me.

                    – Martin
                    Apr 29 '14 at 10:13











                  • In latest Ubuntu versions you just go Language Support then Keyboard input method system is available

                    – vmoh_ir
                    May 30 '18 at 21:26






                  • 8





                    This did not work for me on Ubuntu 18.0.4 LTS. Any ideas why?

                    – Pytry
                    Jun 19 '18 at 22:05






                  • 1





                    why Ubuntu made it so difficult to disable keyboard input system? keystrokes entered going directly to program should be the default anyway.

                    – weima
                    Jul 18 '18 at 15:08






                  • 2





                    does not work for me on ubuntu 18.04

                    – iRaS
                    Aug 22 '18 at 8:59














                  • 11





                    Just logging out and back in works for me.

                    – Martin
                    Apr 29 '14 at 10:13











                  • In latest Ubuntu versions you just go Language Support then Keyboard input method system is available

                    – vmoh_ir
                    May 30 '18 at 21:26






                  • 8





                    This did not work for me on Ubuntu 18.0.4 LTS. Any ideas why?

                    – Pytry
                    Jun 19 '18 at 22:05






                  • 1





                    why Ubuntu made it so difficult to disable keyboard input system? keystrokes entered going directly to program should be the default anyway.

                    – weima
                    Jul 18 '18 at 15:08






                  • 2





                    does not work for me on ubuntu 18.04

                    – iRaS
                    Aug 22 '18 at 8:59








                  11




                  11





                  Just logging out and back in works for me.

                  – Martin
                  Apr 29 '14 at 10:13





                  Just logging out and back in works for me.

                  – Martin
                  Apr 29 '14 at 10:13













                  In latest Ubuntu versions you just go Language Support then Keyboard input method system is available

                  – vmoh_ir
                  May 30 '18 at 21:26





                  In latest Ubuntu versions you just go Language Support then Keyboard input method system is available

                  – vmoh_ir
                  May 30 '18 at 21:26




                  8




                  8





                  This did not work for me on Ubuntu 18.0.4 LTS. Any ideas why?

                  – Pytry
                  Jun 19 '18 at 22:05





                  This did not work for me on Ubuntu 18.0.4 LTS. Any ideas why?

                  – Pytry
                  Jun 19 '18 at 22:05




                  1




                  1





                  why Ubuntu made it so difficult to disable keyboard input system? keystrokes entered going directly to program should be the default anyway.

                  – weima
                  Jul 18 '18 at 15:08





                  why Ubuntu made it so difficult to disable keyboard input system? keystrokes entered going directly to program should be the default anyway.

                  – weima
                  Jul 18 '18 at 15:08




                  2




                  2





                  does not work for me on ubuntu 18.04

                  – iRaS
                  Aug 22 '18 at 8:59





                  does not work for me on ubuntu 18.04

                  – iRaS
                  Aug 22 '18 at 8:59













                  4














                  Changing the input method as PutzKipa explains actually fixes the problem.



                  However, I've failed to find any configuration panel under KDE ubuntu 14.04 to do the job, and the standard im-config utility seems broken. I finally succeeded by creating a file ~/.xinputrc that contains a single line:



                  run_im xim


                  then logout/login. This chooses xim as the input method (ibus is the default). If you remove your ~/.xinputrc, then im-config can list the input methods available, even if it fails to select one.






                  share|improve this answer



















                  • 1





                    this also doesnt seem to work in 16.04 LTS

                    – weima
                    Jul 18 '18 at 15:10
















                  4














                  Changing the input method as PutzKipa explains actually fixes the problem.



                  However, I've failed to find any configuration panel under KDE ubuntu 14.04 to do the job, and the standard im-config utility seems broken. I finally succeeded by creating a file ~/.xinputrc that contains a single line:



                  run_im xim


                  then logout/login. This chooses xim as the input method (ibus is the default). If you remove your ~/.xinputrc, then im-config can list the input methods available, even if it fails to select one.






                  share|improve this answer



















                  • 1





                    this also doesnt seem to work in 16.04 LTS

                    – weima
                    Jul 18 '18 at 15:10














                  4












                  4








                  4







                  Changing the input method as PutzKipa explains actually fixes the problem.



                  However, I've failed to find any configuration panel under KDE ubuntu 14.04 to do the job, and the standard im-config utility seems broken. I finally succeeded by creating a file ~/.xinputrc that contains a single line:



                  run_im xim


                  then logout/login. This chooses xim as the input method (ibus is the default). If you remove your ~/.xinputrc, then im-config can list the input methods available, even if it fails to select one.






                  share|improve this answer













                  Changing the input method as PutzKipa explains actually fixes the problem.



                  However, I've failed to find any configuration panel under KDE ubuntu 14.04 to do the job, and the standard im-config utility seems broken. I finally succeeded by creating a file ~/.xinputrc that contains a single line:



                  run_im xim


                  then logout/login. This chooses xim as the input method (ibus is the default). If you remove your ~/.xinputrc, then im-config can list the input methods available, even if it fails to select one.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Apr 24 '14 at 7:47









                  ChampignacChampignac

                  1412




                  1412








                  • 1





                    this also doesnt seem to work in 16.04 LTS

                    – weima
                    Jul 18 '18 at 15:10














                  • 1





                    this also doesnt seem to work in 16.04 LTS

                    – weima
                    Jul 18 '18 at 15:10








                  1




                  1





                  this also doesnt seem to work in 16.04 LTS

                  – weima
                  Jul 18 '18 at 15:10





                  this also doesnt seem to work in 16.04 LTS

                  – weima
                  Jul 18 '18 at 15:10











                  2














                  For Ubuntu 18.04.



                  I struggled with this problem for two days. I tried all the methods listed here earlier. And it looks like I came up with a solution. But it is very unstable and has bugs.



                  The basic idea is this: in the system settings you can specify the command that is started by the Ctrl+Shift+U key combination.



                  Note: if you specify false as the command, the combination will not work at all.



                  However, we can specify the path to the script as the command, in which we will simulate pressing the same key combination.



                  To simulate keystrokes, I tried the xdotool (apt install xdotool) and the xte (apt install xautomation).
                  Both options were unstable. However, xte turned out to be more flexible for me.



                  Example with xte




                  • Create a file /home/username/shortcut.sh

                  • Add permission to execute: chmod u+x /home/username/shortcut.sh

                  • Specify the path to the script as a command for the Ctrl+Shift+U key combination in the keyboard settings


                  Here is an example script:



                  #!/bin/sh
                  # Make a small delay in order to have time to release the keys.
                  sleep 0.2

                  # Simulate the release of just pressed keys, if they are still pressed.
                  xte 'keyup u' 'keyup Shift_L' 'keyup Control_L'

                  # Hack: Caps_Lock is used so that the system does not intercept this combination.
                  # You can try to remove it if it hinders you.
                  xte 'key Caps_Lock'

                  # Simulate pressing a key combination
                  xte 'keydown Shift_L' 'keydown Control_L' 'key u'

                  # Simulate releasing a key combination
                  xte 'keyup Shift_L' 'keyup Control_L'

                  # Restore Caps_Lock to the previous state.
                  xte 'key Caps_Lock'


                  I tested this in PhpStorm 2018.2 EAP Build #PS-182.3458.35 and I can say that it works, but with some caveats:




                  • this works slowly (on my rather old PC)

                  • during the execution of the script, it is better not to press any keys

                  • sometimes it may not work

                  • sometimes it can enter an infinite loop. Therefore, it's better to add a check to the script that the script is already running.


                  In general, if you do not often use this combination, then this solution may suit you.



                  But, probably, someone will come up with a better and more stable solution.



                  I hope this idea will help someone.






                  share|improve this answer




























                    2














                    For Ubuntu 18.04.



                    I struggled with this problem for two days. I tried all the methods listed here earlier. And it looks like I came up with a solution. But it is very unstable and has bugs.



                    The basic idea is this: in the system settings you can specify the command that is started by the Ctrl+Shift+U key combination.



                    Note: if you specify false as the command, the combination will not work at all.



                    However, we can specify the path to the script as the command, in which we will simulate pressing the same key combination.



                    To simulate keystrokes, I tried the xdotool (apt install xdotool) and the xte (apt install xautomation).
                    Both options were unstable. However, xte turned out to be more flexible for me.



                    Example with xte




                    • Create a file /home/username/shortcut.sh

                    • Add permission to execute: chmod u+x /home/username/shortcut.sh

                    • Specify the path to the script as a command for the Ctrl+Shift+U key combination in the keyboard settings


                    Here is an example script:



                    #!/bin/sh
                    # Make a small delay in order to have time to release the keys.
                    sleep 0.2

                    # Simulate the release of just pressed keys, if they are still pressed.
                    xte 'keyup u' 'keyup Shift_L' 'keyup Control_L'

                    # Hack: Caps_Lock is used so that the system does not intercept this combination.
                    # You can try to remove it if it hinders you.
                    xte 'key Caps_Lock'

                    # Simulate pressing a key combination
                    xte 'keydown Shift_L' 'keydown Control_L' 'key u'

                    # Simulate releasing a key combination
                    xte 'keyup Shift_L' 'keyup Control_L'

                    # Restore Caps_Lock to the previous state.
                    xte 'key Caps_Lock'


                    I tested this in PhpStorm 2018.2 EAP Build #PS-182.3458.35 and I can say that it works, but with some caveats:




                    • this works slowly (on my rather old PC)

                    • during the execution of the script, it is better not to press any keys

                    • sometimes it may not work

                    • sometimes it can enter an infinite loop. Therefore, it's better to add a check to the script that the script is already running.


                    In general, if you do not often use this combination, then this solution may suit you.



                    But, probably, someone will come up with a better and more stable solution.



                    I hope this idea will help someone.






                    share|improve this answer


























                      2












                      2








                      2







                      For Ubuntu 18.04.



                      I struggled with this problem for two days. I tried all the methods listed here earlier. And it looks like I came up with a solution. But it is very unstable and has bugs.



                      The basic idea is this: in the system settings you can specify the command that is started by the Ctrl+Shift+U key combination.



                      Note: if you specify false as the command, the combination will not work at all.



                      However, we can specify the path to the script as the command, in which we will simulate pressing the same key combination.



                      To simulate keystrokes, I tried the xdotool (apt install xdotool) and the xte (apt install xautomation).
                      Both options were unstable. However, xte turned out to be more flexible for me.



                      Example with xte




                      • Create a file /home/username/shortcut.sh

                      • Add permission to execute: chmod u+x /home/username/shortcut.sh

                      • Specify the path to the script as a command for the Ctrl+Shift+U key combination in the keyboard settings


                      Here is an example script:



                      #!/bin/sh
                      # Make a small delay in order to have time to release the keys.
                      sleep 0.2

                      # Simulate the release of just pressed keys, if they are still pressed.
                      xte 'keyup u' 'keyup Shift_L' 'keyup Control_L'

                      # Hack: Caps_Lock is used so that the system does not intercept this combination.
                      # You can try to remove it if it hinders you.
                      xte 'key Caps_Lock'

                      # Simulate pressing a key combination
                      xte 'keydown Shift_L' 'keydown Control_L' 'key u'

                      # Simulate releasing a key combination
                      xte 'keyup Shift_L' 'keyup Control_L'

                      # Restore Caps_Lock to the previous state.
                      xte 'key Caps_Lock'


                      I tested this in PhpStorm 2018.2 EAP Build #PS-182.3458.35 and I can say that it works, but with some caveats:




                      • this works slowly (on my rather old PC)

                      • during the execution of the script, it is better not to press any keys

                      • sometimes it may not work

                      • sometimes it can enter an infinite loop. Therefore, it's better to add a check to the script that the script is already running.


                      In general, if you do not often use this combination, then this solution may suit you.



                      But, probably, someone will come up with a better and more stable solution.



                      I hope this idea will help someone.






                      share|improve this answer













                      For Ubuntu 18.04.



                      I struggled with this problem for two days. I tried all the methods listed here earlier. And it looks like I came up with a solution. But it is very unstable and has bugs.



                      The basic idea is this: in the system settings you can specify the command that is started by the Ctrl+Shift+U key combination.



                      Note: if you specify false as the command, the combination will not work at all.



                      However, we can specify the path to the script as the command, in which we will simulate pressing the same key combination.



                      To simulate keystrokes, I tried the xdotool (apt install xdotool) and the xte (apt install xautomation).
                      Both options were unstable. However, xte turned out to be more flexible for me.



                      Example with xte




                      • Create a file /home/username/shortcut.sh

                      • Add permission to execute: chmod u+x /home/username/shortcut.sh

                      • Specify the path to the script as a command for the Ctrl+Shift+U key combination in the keyboard settings


                      Here is an example script:



                      #!/bin/sh
                      # Make a small delay in order to have time to release the keys.
                      sleep 0.2

                      # Simulate the release of just pressed keys, if they are still pressed.
                      xte 'keyup u' 'keyup Shift_L' 'keyup Control_L'

                      # Hack: Caps_Lock is used so that the system does not intercept this combination.
                      # You can try to remove it if it hinders you.
                      xte 'key Caps_Lock'

                      # Simulate pressing a key combination
                      xte 'keydown Shift_L' 'keydown Control_L' 'key u'

                      # Simulate releasing a key combination
                      xte 'keyup Shift_L' 'keyup Control_L'

                      # Restore Caps_Lock to the previous state.
                      xte 'key Caps_Lock'


                      I tested this in PhpStorm 2018.2 EAP Build #PS-182.3458.35 and I can say that it works, but with some caveats:




                      • this works slowly (on my rather old PC)

                      • during the execution of the script, it is better not to press any keys

                      • sometimes it may not work

                      • sometimes it can enter an infinite loop. Therefore, it's better to add a check to the script that the script is already running.


                      In general, if you do not often use this combination, then this solution may suit you.



                      But, probably, someone will come up with a better and more stable solution.



                      I hope this idea will help someone.







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Jul 15 '18 at 16:46









                      VadimVadim

                      415




                      415























                          1





                          +50









                          Try:



                          export GTK_IM_MODULE="gtk-im-context-simple"


                          and then run Eclipse from the same shell. Or if that doesn't work,



                          export GTK_IM_MODULE="xim"


                          (This test only works entering running the export command and then Eclipse from the same shell command line, it won't change anything if you use a desktop shortcut or the Applications menu, or run Eclipse from a new shell.)



                          If either test works, you can make the change system-wide by adding it to /etc/environment, or per-user in ~/.gnomerc. (The export command doesn't go in those files, just a new line with GTK_IM_MODULE="xim" or GTK_IM_MODULE="gtk-im-context-simple".)



                          It sounds like this behavior comes from GTK's input mappings as described here: https://developer.gnome.org/gtk3/unstable/GtkIMContext.html




                          ... This is called preediting, and an input method may provide feedback about this process by displaying the intermediate composition states as preedit text. For instance, the default GTK+ input method implements the input of arbitrary Unicode code points by holding down the Control and Shift keys and then typing “U” followed by the hexadecimal digits of the code point. When releasing the Control and Shift keys, preediting ends and the character is inserted as text. Ctrl+Shift+u20AC for example results in the € sign.




                          GTK is used by a whole lot of common apps in Ubuntu, including Eclipse.






                          share|improve this answer






























                            1





                            +50









                            Try:



                            export GTK_IM_MODULE="gtk-im-context-simple"


                            and then run Eclipse from the same shell. Or if that doesn't work,



                            export GTK_IM_MODULE="xim"


                            (This test only works entering running the export command and then Eclipse from the same shell command line, it won't change anything if you use a desktop shortcut or the Applications menu, or run Eclipse from a new shell.)



                            If either test works, you can make the change system-wide by adding it to /etc/environment, or per-user in ~/.gnomerc. (The export command doesn't go in those files, just a new line with GTK_IM_MODULE="xim" or GTK_IM_MODULE="gtk-im-context-simple".)



                            It sounds like this behavior comes from GTK's input mappings as described here: https://developer.gnome.org/gtk3/unstable/GtkIMContext.html




                            ... This is called preediting, and an input method may provide feedback about this process by displaying the intermediate composition states as preedit text. For instance, the default GTK+ input method implements the input of arbitrary Unicode code points by holding down the Control and Shift keys and then typing “U” followed by the hexadecimal digits of the code point. When releasing the Control and Shift keys, preediting ends and the character is inserted as text. Ctrl+Shift+u20AC for example results in the € sign.




                            GTK is used by a whole lot of common apps in Ubuntu, including Eclipse.






                            share|improve this answer




























                              1





                              +50







                              1





                              +50



                              1




                              +50





                              Try:



                              export GTK_IM_MODULE="gtk-im-context-simple"


                              and then run Eclipse from the same shell. Or if that doesn't work,



                              export GTK_IM_MODULE="xim"


                              (This test only works entering running the export command and then Eclipse from the same shell command line, it won't change anything if you use a desktop shortcut or the Applications menu, or run Eclipse from a new shell.)



                              If either test works, you can make the change system-wide by adding it to /etc/environment, or per-user in ~/.gnomerc. (The export command doesn't go in those files, just a new line with GTK_IM_MODULE="xim" or GTK_IM_MODULE="gtk-im-context-simple".)



                              It sounds like this behavior comes from GTK's input mappings as described here: https://developer.gnome.org/gtk3/unstable/GtkIMContext.html




                              ... This is called preediting, and an input method may provide feedback about this process by displaying the intermediate composition states as preedit text. For instance, the default GTK+ input method implements the input of arbitrary Unicode code points by holding down the Control and Shift keys and then typing “U” followed by the hexadecimal digits of the code point. When releasing the Control and Shift keys, preediting ends and the character is inserted as text. Ctrl+Shift+u20AC for example results in the € sign.




                              GTK is used by a whole lot of common apps in Ubuntu, including Eclipse.






                              share|improve this answer















                              Try:



                              export GTK_IM_MODULE="gtk-im-context-simple"


                              and then run Eclipse from the same shell. Or if that doesn't work,



                              export GTK_IM_MODULE="xim"


                              (This test only works entering running the export command and then Eclipse from the same shell command line, it won't change anything if you use a desktop shortcut or the Applications menu, or run Eclipse from a new shell.)



                              If either test works, you can make the change system-wide by adding it to /etc/environment, or per-user in ~/.gnomerc. (The export command doesn't go in those files, just a new line with GTK_IM_MODULE="xim" or GTK_IM_MODULE="gtk-im-context-simple".)



                              It sounds like this behavior comes from GTK's input mappings as described here: https://developer.gnome.org/gtk3/unstable/GtkIMContext.html




                              ... This is called preediting, and an input method may provide feedback about this process by displaying the intermediate composition states as preedit text. For instance, the default GTK+ input method implements the input of arbitrary Unicode code points by holding down the Control and Shift keys and then typing “U” followed by the hexadecimal digits of the code point. When releasing the Control and Shift keys, preediting ends and the character is inserted as text. Ctrl+Shift+u20AC for example results in the € sign.




                              GTK is used by a whole lot of common apps in Ubuntu, including Eclipse.







                              share|improve this answer














                              share|improve this answer



                              share|improve this answer








                              edited Jun 26 '18 at 0:33

























                              answered Jun 26 '18 at 0:28









                              Steven KSteven K

                              27818




                              27818























                                  1














                                  Ubuntu 14.04/18.04 Solution



                                  recently upgrade to 18.04 and fight my way to solve this issue.




                                  1. open search using super key

                                  2. go to language support

                                  3. click Keyboard input method system dropdown menu and choose none


                                  Language Support Menu





                                  1. dont forget to click - apply system wide

                                  2. close the window (wont activate until you do)

                                  3. reboot (logout might be enough)


                                  Credit goes to reverse issue on askubuntu - for some reason someone wants to enable this shortcut.






                                  share|improve this answer


























                                  • This solution did not work for me. Should I also reboot? (I have too many windows opened now and cannot test it quickly)

                                    – desa
                                    Sep 30 '18 at 11:58











                                  • works after reboot (maybe logout is enough) @desa thanks ill update the answer

                                    – ShmulikA
                                    Oct 2 '18 at 11:21











                                  • does not solve the problem in 18.04

                                    – James
                                    Nov 21 '18 at 14:55
















                                  1














                                  Ubuntu 14.04/18.04 Solution



                                  recently upgrade to 18.04 and fight my way to solve this issue.




                                  1. open search using super key

                                  2. go to language support

                                  3. click Keyboard input method system dropdown menu and choose none


                                  Language Support Menu





                                  1. dont forget to click - apply system wide

                                  2. close the window (wont activate until you do)

                                  3. reboot (logout might be enough)


                                  Credit goes to reverse issue on askubuntu - for some reason someone wants to enable this shortcut.






                                  share|improve this answer


























                                  • This solution did not work for me. Should I also reboot? (I have too many windows opened now and cannot test it quickly)

                                    – desa
                                    Sep 30 '18 at 11:58











                                  • works after reboot (maybe logout is enough) @desa thanks ill update the answer

                                    – ShmulikA
                                    Oct 2 '18 at 11:21











                                  • does not solve the problem in 18.04

                                    – James
                                    Nov 21 '18 at 14:55














                                  1












                                  1








                                  1







                                  Ubuntu 14.04/18.04 Solution



                                  recently upgrade to 18.04 and fight my way to solve this issue.




                                  1. open search using super key

                                  2. go to language support

                                  3. click Keyboard input method system dropdown menu and choose none


                                  Language Support Menu





                                  1. dont forget to click - apply system wide

                                  2. close the window (wont activate until you do)

                                  3. reboot (logout might be enough)


                                  Credit goes to reverse issue on askubuntu - for some reason someone wants to enable this shortcut.






                                  share|improve this answer















                                  Ubuntu 14.04/18.04 Solution



                                  recently upgrade to 18.04 and fight my way to solve this issue.




                                  1. open search using super key

                                  2. go to language support

                                  3. click Keyboard input method system dropdown menu and choose none


                                  Language Support Menu





                                  1. dont forget to click - apply system wide

                                  2. close the window (wont activate until you do)

                                  3. reboot (logout might be enough)


                                  Credit goes to reverse issue on askubuntu - for some reason someone wants to enable this shortcut.







                                  share|improve this answer














                                  share|improve this answer



                                  share|improve this answer








                                  edited Oct 2 '18 at 11:21

























                                  answered Jul 31 '18 at 18:35









                                  ShmulikAShmulikA

                                  1114




                                  1114













                                  • This solution did not work for me. Should I also reboot? (I have too many windows opened now and cannot test it quickly)

                                    – desa
                                    Sep 30 '18 at 11:58











                                  • works after reboot (maybe logout is enough) @desa thanks ill update the answer

                                    – ShmulikA
                                    Oct 2 '18 at 11:21











                                  • does not solve the problem in 18.04

                                    – James
                                    Nov 21 '18 at 14:55



















                                  • This solution did not work for me. Should I also reboot? (I have too many windows opened now and cannot test it quickly)

                                    – desa
                                    Sep 30 '18 at 11:58











                                  • works after reboot (maybe logout is enough) @desa thanks ill update the answer

                                    – ShmulikA
                                    Oct 2 '18 at 11:21











                                  • does not solve the problem in 18.04

                                    – James
                                    Nov 21 '18 at 14:55

















                                  This solution did not work for me. Should I also reboot? (I have too many windows opened now and cannot test it quickly)

                                  – desa
                                  Sep 30 '18 at 11:58





                                  This solution did not work for me. Should I also reboot? (I have too many windows opened now and cannot test it quickly)

                                  – desa
                                  Sep 30 '18 at 11:58













                                  works after reboot (maybe logout is enough) @desa thanks ill update the answer

                                  – ShmulikA
                                  Oct 2 '18 at 11:21





                                  works after reboot (maybe logout is enough) @desa thanks ill update the answer

                                  – ShmulikA
                                  Oct 2 '18 at 11:21













                                  does not solve the problem in 18.04

                                  – James
                                  Nov 21 '18 at 14:55





                                  does not solve the problem in 18.04

                                  – James
                                  Nov 21 '18 at 14:55











                                  1














                                  Ubuntu 18.04



                                  Running into this problem on Ubuntu 18.04, I've tried all suggestion above, but unfortunately none of them worked. I ended up uninstalling the ibus package.



                                  Background / sidenotes



                                  I tried to disable IBus using




                                  1. the Language Support menu


                                  2. im-config (configures ~/.xinputrc)


                                  3. sudo im-config (configures /etc/X11/xinit/xinputrc)


                                  I noticed however that no matter what config I tried, the ibus daemon was running everytime after I had rebooted.






                                  share|improve this answer




























                                    1














                                    Ubuntu 18.04



                                    Running into this problem on Ubuntu 18.04, I've tried all suggestion above, but unfortunately none of them worked. I ended up uninstalling the ibus package.



                                    Background / sidenotes



                                    I tried to disable IBus using




                                    1. the Language Support menu


                                    2. im-config (configures ~/.xinputrc)


                                    3. sudo im-config (configures /etc/X11/xinit/xinputrc)


                                    I noticed however that no matter what config I tried, the ibus daemon was running everytime after I had rebooted.






                                    share|improve this answer


























                                      1












                                      1








                                      1







                                      Ubuntu 18.04



                                      Running into this problem on Ubuntu 18.04, I've tried all suggestion above, but unfortunately none of them worked. I ended up uninstalling the ibus package.



                                      Background / sidenotes



                                      I tried to disable IBus using




                                      1. the Language Support menu


                                      2. im-config (configures ~/.xinputrc)


                                      3. sudo im-config (configures /etc/X11/xinit/xinputrc)


                                      I noticed however that no matter what config I tried, the ibus daemon was running everytime after I had rebooted.






                                      share|improve this answer













                                      Ubuntu 18.04



                                      Running into this problem on Ubuntu 18.04, I've tried all suggestion above, but unfortunately none of them worked. I ended up uninstalling the ibus package.



                                      Background / sidenotes



                                      I tried to disable IBus using




                                      1. the Language Support menu


                                      2. im-config (configures ~/.xinputrc)


                                      3. sudo im-config (configures /etc/X11/xinit/xinputrc)


                                      I noticed however that no matter what config I tried, the ibus daemon was running everytime after I had rebooted.







                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered Oct 21 '18 at 16:52









                                      jbvojbvo

                                      112




                                      112























                                          1















                                          1. Run ibus-setup from the terminal (or open IBus Preferences).

                                          2. Go to “Emoji”.

                                          3. Next to “Unicode code point:”, click on the three dots (i.e. ...).

                                          4. In the dialog, click “Delete”, then “OK”.

                                          5. Close the IBus Preferences window.






                                          share|improve this answer




























                                            1















                                            1. Run ibus-setup from the terminal (or open IBus Preferences).

                                            2. Go to “Emoji”.

                                            3. Next to “Unicode code point:”, click on the three dots (i.e. ...).

                                            4. In the dialog, click “Delete”, then “OK”.

                                            5. Close the IBus Preferences window.






                                            share|improve this answer


























                                              1












                                              1








                                              1








                                              1. Run ibus-setup from the terminal (or open IBus Preferences).

                                              2. Go to “Emoji”.

                                              3. Next to “Unicode code point:”, click on the three dots (i.e. ...).

                                              4. In the dialog, click “Delete”, then “OK”.

                                              5. Close the IBus Preferences window.






                                              share|improve this answer














                                              1. Run ibus-setup from the terminal (or open IBus Preferences).

                                              2. Go to “Emoji”.

                                              3. Next to “Unicode code point:”, click on the three dots (i.e. ...).

                                              4. In the dialog, click “Delete”, then “OK”.

                                              5. Close the IBus Preferences window.







                                              share|improve this answer












                                              share|improve this answer



                                              share|improve this answer










                                              answered Jan 10 at 9:49









                                              kleinfreundkleinfreund

                                              1851214




                                              1851214























                                                  0














                                                  Open a terminal window.



                                                  cd ~/.gconf/desktop/gnome/interface
                                                  gedit %gconf.xml


                                                  Change the show_unicode_menu from true to false.



                                                  Save, Log out and back in.






                                                  share|improve this answer
























                                                  • /desktop/gnome/interface/show_unicode_menu is already disabled (false) Question is about keyboard shorcut, not menu.

                                                    – MariuszS
                                                    Aug 22 '13 at 17:15













                                                  • good use of time, downvoting an answer almost two years old.

                                                    – John Barry
                                                    Aug 22 '13 at 18:42






                                                  • 7





                                                    Two years later this question is still valid... so why not?

                                                    – MariuszS
                                                    Aug 23 '13 at 12:13











                                                  • disabling show_unicode_menu works on elementaryOS, though I use a different tool to do the job: dconf-editor. This point me to the correct key anyway, thank you.

                                                    – Hoang Tran
                                                    Jul 10 '16 at 10:08
















                                                  0














                                                  Open a terminal window.



                                                  cd ~/.gconf/desktop/gnome/interface
                                                  gedit %gconf.xml


                                                  Change the show_unicode_menu from true to false.



                                                  Save, Log out and back in.






                                                  share|improve this answer
























                                                  • /desktop/gnome/interface/show_unicode_menu is already disabled (false) Question is about keyboard shorcut, not menu.

                                                    – MariuszS
                                                    Aug 22 '13 at 17:15













                                                  • good use of time, downvoting an answer almost two years old.

                                                    – John Barry
                                                    Aug 22 '13 at 18:42






                                                  • 7





                                                    Two years later this question is still valid... so why not?

                                                    – MariuszS
                                                    Aug 23 '13 at 12:13











                                                  • disabling show_unicode_menu works on elementaryOS, though I use a different tool to do the job: dconf-editor. This point me to the correct key anyway, thank you.

                                                    – Hoang Tran
                                                    Jul 10 '16 at 10:08














                                                  0












                                                  0








                                                  0







                                                  Open a terminal window.



                                                  cd ~/.gconf/desktop/gnome/interface
                                                  gedit %gconf.xml


                                                  Change the show_unicode_menu from true to false.



                                                  Save, Log out and back in.






                                                  share|improve this answer













                                                  Open a terminal window.



                                                  cd ~/.gconf/desktop/gnome/interface
                                                  gedit %gconf.xml


                                                  Change the show_unicode_menu from true to false.



                                                  Save, Log out and back in.







                                                  share|improve this answer












                                                  share|improve this answer



                                                  share|improve this answer










                                                  answered Nov 18 '11 at 1:42









                                                  John BarryJohn Barry

                                                  23019




                                                  23019













                                                  • /desktop/gnome/interface/show_unicode_menu is already disabled (false) Question is about keyboard shorcut, not menu.

                                                    – MariuszS
                                                    Aug 22 '13 at 17:15













                                                  • good use of time, downvoting an answer almost two years old.

                                                    – John Barry
                                                    Aug 22 '13 at 18:42






                                                  • 7





                                                    Two years later this question is still valid... so why not?

                                                    – MariuszS
                                                    Aug 23 '13 at 12:13











                                                  • disabling show_unicode_menu works on elementaryOS, though I use a different tool to do the job: dconf-editor. This point me to the correct key anyway, thank you.

                                                    – Hoang Tran
                                                    Jul 10 '16 at 10:08



















                                                  • /desktop/gnome/interface/show_unicode_menu is already disabled (false) Question is about keyboard shorcut, not menu.

                                                    – MariuszS
                                                    Aug 22 '13 at 17:15













                                                  • good use of time, downvoting an answer almost two years old.

                                                    – John Barry
                                                    Aug 22 '13 at 18:42






                                                  • 7





                                                    Two years later this question is still valid... so why not?

                                                    – MariuszS
                                                    Aug 23 '13 at 12:13











                                                  • disabling show_unicode_menu works on elementaryOS, though I use a different tool to do the job: dconf-editor. This point me to the correct key anyway, thank you.

                                                    – Hoang Tran
                                                    Jul 10 '16 at 10:08

















                                                  /desktop/gnome/interface/show_unicode_menu is already disabled (false) Question is about keyboard shorcut, not menu.

                                                  – MariuszS
                                                  Aug 22 '13 at 17:15







                                                  /desktop/gnome/interface/show_unicode_menu is already disabled (false) Question is about keyboard shorcut, not menu.

                                                  – MariuszS
                                                  Aug 22 '13 at 17:15















                                                  good use of time, downvoting an answer almost two years old.

                                                  – John Barry
                                                  Aug 22 '13 at 18:42





                                                  good use of time, downvoting an answer almost two years old.

                                                  – John Barry
                                                  Aug 22 '13 at 18:42




                                                  7




                                                  7





                                                  Two years later this question is still valid... so why not?

                                                  – MariuszS
                                                  Aug 23 '13 at 12:13





                                                  Two years later this question is still valid... so why not?

                                                  – MariuszS
                                                  Aug 23 '13 at 12:13













                                                  disabling show_unicode_menu works on elementaryOS, though I use a different tool to do the job: dconf-editor. This point me to the correct key anyway, thank you.

                                                  – Hoang Tran
                                                  Jul 10 '16 at 10:08





                                                  disabling show_unicode_menu works on elementaryOS, though I use a different tool to do the job: dconf-editor. This point me to the correct key anyway, thank you.

                                                  – Hoang Tran
                                                  Jul 10 '16 at 10:08


















                                                  draft saved

                                                  draft discarded




















































                                                  Thanks for contributing an answer to Super User!


                                                  • 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%2fsuperuser.com%2fquestions%2f358749%2fhow-to-disable-ctrlshiftu-in-ubuntu-linux%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

                                                  Probability when a professor distributes a quiz and homework assignment to a class of n students.

                                                  Aardman Animations

                                                  Are they similar matrix