AltGr is not working












2















I have a strange problem with my AltGr key.



My keyboard layout is set to "English (international AltGr dead keys)", but when I press AltGre I get a normal "e" instead of an "eacute" (é).



As workaround I added a second keyboard layout "English (Dvorak, international with dead keys)". After switching to the Dvorak layout and then immediately back to the AltGr layout, the combination AltGre gives an "eacute" (é).



In an other question someone mentioned running xev, so I did that too.
Here is the output BEFORE the switch:



KeyPress event, serial 37, synthetic NO, window 0x5400001,
root 0x2c3, subw 0x0, time 568919, (-1132,160), root:(130,212),
state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
XKeysymToKeycode returns keycode: 92
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 37, synthetic NO, window 0x5400001,
root 0x2c3, subw 0x0, time 570395, (-1132,160), root:(130,212),
state 0x90, keycode 26 (keysym 0x65, e), same_screen YES,
XLookupString gives 1 bytes: (65) "e"
XmbLookupString gives 1 bytes: (65) "e"
XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x5400001,
root 0x2c3, subw 0x0, time 570530, (-1132,160), root:(130,212),
state 0x90, keycode 26 (keysym 0x65, e), same_screen YES,
XLookupString gives 1 bytes: (65) "e"
XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x5400001,
root 0x2c3, subw 0x0, time 571313, (-1132,160), root:(130,212),
state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
XKeysymToKeycode returns keycode: 92
XLookupString gives 0 bytes:
XFilterEvent returns: False


output AFTER the switch



KeyPress event, serial 49, synthetic NO, window 0x5400001,
root 0x2c3, subw 0x0, time 662306, (62,149), root:(1324,201),
state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
XKeysymToKeycode returns keycode: 92
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 49, synthetic NO, window 0x5400001,
root 0x2c3, subw 0x0, time 662625, (62,149), root:(1324,201),
state 0x90, keycode 26 (keysym 0xe9, eacute), same_screen YES,
XLookupString gives 2 bytes: (c3 a9) "é"
XmbLookupString gives 2 bytes: (c3 a9) "é"
XFilterEvent returns: False

KeyRelease event, serial 49, synthetic NO, window 0x5400001,
root 0x2c3, subw 0x0, time 662769, (62,149), root:(1324,201),
state 0x90, keycode 26 (keysym 0xe9, eacute), same_screen YES,
XLookupString gives 2 bytes: (c3 a9) "é"
XFilterEvent returns: False

KeyRelease event, serial 49, synthetic NO, window 0x5400001,
root 0x2c3, subw 0x0, time 664317, (62,149), root:(1324,201),
state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
XKeysymToKeycode returns keycode: 92
XLookupString gives 0 bytes:
XFilterEvent returns: False


I don't know if more info is needed to fix my problem, so please let me know if that's the case.
And if you know how to fix it for me, please let me know.



Thanks,
Matt










share|improve this question





























    2















    I have a strange problem with my AltGr key.



    My keyboard layout is set to "English (international AltGr dead keys)", but when I press AltGre I get a normal "e" instead of an "eacute" (é).



    As workaround I added a second keyboard layout "English (Dvorak, international with dead keys)". After switching to the Dvorak layout and then immediately back to the AltGr layout, the combination AltGre gives an "eacute" (é).



    In an other question someone mentioned running xev, so I did that too.
    Here is the output BEFORE the switch:



    KeyPress event, serial 37, synthetic NO, window 0x5400001,
    root 0x2c3, subw 0x0, time 568919, (-1132,160), root:(130,212),
    state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
    XKeysymToKeycode returns keycode: 92
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

    KeyPress event, serial 37, synthetic NO, window 0x5400001,
    root 0x2c3, subw 0x0, time 570395, (-1132,160), root:(130,212),
    state 0x90, keycode 26 (keysym 0x65, e), same_screen YES,
    XLookupString gives 1 bytes: (65) "e"
    XmbLookupString gives 1 bytes: (65) "e"
    XFilterEvent returns: False

    KeyRelease event, serial 37, synthetic NO, window 0x5400001,
    root 0x2c3, subw 0x0, time 570530, (-1132,160), root:(130,212),
    state 0x90, keycode 26 (keysym 0x65, e), same_screen YES,
    XLookupString gives 1 bytes: (65) "e"
    XFilterEvent returns: False

    KeyRelease event, serial 37, synthetic NO, window 0x5400001,
    root 0x2c3, subw 0x0, time 571313, (-1132,160), root:(130,212),
    state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
    XKeysymToKeycode returns keycode: 92
    XLookupString gives 0 bytes:
    XFilterEvent returns: False


    output AFTER the switch



    KeyPress event, serial 49, synthetic NO, window 0x5400001,
    root 0x2c3, subw 0x0, time 662306, (62,149), root:(1324,201),
    state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
    XKeysymToKeycode returns keycode: 92
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

    KeyPress event, serial 49, synthetic NO, window 0x5400001,
    root 0x2c3, subw 0x0, time 662625, (62,149), root:(1324,201),
    state 0x90, keycode 26 (keysym 0xe9, eacute), same_screen YES,
    XLookupString gives 2 bytes: (c3 a9) "é"
    XmbLookupString gives 2 bytes: (c3 a9) "é"
    XFilterEvent returns: False

    KeyRelease event, serial 49, synthetic NO, window 0x5400001,
    root 0x2c3, subw 0x0, time 662769, (62,149), root:(1324,201),
    state 0x90, keycode 26 (keysym 0xe9, eacute), same_screen YES,
    XLookupString gives 2 bytes: (c3 a9) "é"
    XFilterEvent returns: False

    KeyRelease event, serial 49, synthetic NO, window 0x5400001,
    root 0x2c3, subw 0x0, time 664317, (62,149), root:(1324,201),
    state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
    XKeysymToKeycode returns keycode: 92
    XLookupString gives 0 bytes:
    XFilterEvent returns: False


    I don't know if more info is needed to fix my problem, so please let me know if that's the case.
    And if you know how to fix it for me, please let me know.



    Thanks,
    Matt










    share|improve this question



























      2












      2








      2








      I have a strange problem with my AltGr key.



      My keyboard layout is set to "English (international AltGr dead keys)", but when I press AltGre I get a normal "e" instead of an "eacute" (é).



      As workaround I added a second keyboard layout "English (Dvorak, international with dead keys)". After switching to the Dvorak layout and then immediately back to the AltGr layout, the combination AltGre gives an "eacute" (é).



      In an other question someone mentioned running xev, so I did that too.
      Here is the output BEFORE the switch:



      KeyPress event, serial 37, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 568919, (-1132,160), root:(130,212),
      state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
      XKeysymToKeycode returns keycode: 92
      XLookupString gives 0 bytes:
      XmbLookupString gives 0 bytes:
      XFilterEvent returns: False

      KeyPress event, serial 37, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 570395, (-1132,160), root:(130,212),
      state 0x90, keycode 26 (keysym 0x65, e), same_screen YES,
      XLookupString gives 1 bytes: (65) "e"
      XmbLookupString gives 1 bytes: (65) "e"
      XFilterEvent returns: False

      KeyRelease event, serial 37, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 570530, (-1132,160), root:(130,212),
      state 0x90, keycode 26 (keysym 0x65, e), same_screen YES,
      XLookupString gives 1 bytes: (65) "e"
      XFilterEvent returns: False

      KeyRelease event, serial 37, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 571313, (-1132,160), root:(130,212),
      state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
      XKeysymToKeycode returns keycode: 92
      XLookupString gives 0 bytes:
      XFilterEvent returns: False


      output AFTER the switch



      KeyPress event, serial 49, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 662306, (62,149), root:(1324,201),
      state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
      XKeysymToKeycode returns keycode: 92
      XLookupString gives 0 bytes:
      XmbLookupString gives 0 bytes:
      XFilterEvent returns: False

      KeyPress event, serial 49, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 662625, (62,149), root:(1324,201),
      state 0x90, keycode 26 (keysym 0xe9, eacute), same_screen YES,
      XLookupString gives 2 bytes: (c3 a9) "é"
      XmbLookupString gives 2 bytes: (c3 a9) "é"
      XFilterEvent returns: False

      KeyRelease event, serial 49, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 662769, (62,149), root:(1324,201),
      state 0x90, keycode 26 (keysym 0xe9, eacute), same_screen YES,
      XLookupString gives 2 bytes: (c3 a9) "é"
      XFilterEvent returns: False

      KeyRelease event, serial 49, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 664317, (62,149), root:(1324,201),
      state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
      XKeysymToKeycode returns keycode: 92
      XLookupString gives 0 bytes:
      XFilterEvent returns: False


      I don't know if more info is needed to fix my problem, so please let me know if that's the case.
      And if you know how to fix it for me, please let me know.



      Thanks,
      Matt










      share|improve this question
















      I have a strange problem with my AltGr key.



      My keyboard layout is set to "English (international AltGr dead keys)", but when I press AltGre I get a normal "e" instead of an "eacute" (é).



      As workaround I added a second keyboard layout "English (Dvorak, international with dead keys)". After switching to the Dvorak layout and then immediately back to the AltGr layout, the combination AltGre gives an "eacute" (é).



      In an other question someone mentioned running xev, so I did that too.
      Here is the output BEFORE the switch:



      KeyPress event, serial 37, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 568919, (-1132,160), root:(130,212),
      state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
      XKeysymToKeycode returns keycode: 92
      XLookupString gives 0 bytes:
      XmbLookupString gives 0 bytes:
      XFilterEvent returns: False

      KeyPress event, serial 37, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 570395, (-1132,160), root:(130,212),
      state 0x90, keycode 26 (keysym 0x65, e), same_screen YES,
      XLookupString gives 1 bytes: (65) "e"
      XmbLookupString gives 1 bytes: (65) "e"
      XFilterEvent returns: False

      KeyRelease event, serial 37, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 570530, (-1132,160), root:(130,212),
      state 0x90, keycode 26 (keysym 0x65, e), same_screen YES,
      XLookupString gives 1 bytes: (65) "e"
      XFilterEvent returns: False

      KeyRelease event, serial 37, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 571313, (-1132,160), root:(130,212),
      state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
      XKeysymToKeycode returns keycode: 92
      XLookupString gives 0 bytes:
      XFilterEvent returns: False


      output AFTER the switch



      KeyPress event, serial 49, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 662306, (62,149), root:(1324,201),
      state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
      XKeysymToKeycode returns keycode: 92
      XLookupString gives 0 bytes:
      XmbLookupString gives 0 bytes:
      XFilterEvent returns: False

      KeyPress event, serial 49, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 662625, (62,149), root:(1324,201),
      state 0x90, keycode 26 (keysym 0xe9, eacute), same_screen YES,
      XLookupString gives 2 bytes: (c3 a9) "é"
      XmbLookupString gives 2 bytes: (c3 a9) "é"
      XFilterEvent returns: False

      KeyRelease event, serial 49, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 662769, (62,149), root:(1324,201),
      state 0x90, keycode 26 (keysym 0xe9, eacute), same_screen YES,
      XLookupString gives 2 bytes: (c3 a9) "é"
      XFilterEvent returns: False

      KeyRelease event, serial 49, synthetic NO, window 0x5400001,
      root 0x2c3, subw 0x0, time 664317, (62,149), root:(1324,201),
      state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES,
      XKeysymToKeycode returns keycode: 92
      XLookupString gives 0 bytes:
      XFilterEvent returns: False


      I don't know if more info is needed to fix my problem, so please let me know if that's the case.
      And if you know how to fix it for me, please let me know.



      Thanks,
      Matt







      14.04 keyboard-layout






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Feb 5 at 2:27









      TDK

      25013




      25013










      asked Sep 27 '15 at 18:13









      MattijsMattijs

      4818




      4818






















          1 Answer
          1






          active

          oldest

          votes


















          0














          EDIT / reading again your question I understand that this one maybe is not answering you. I will let this here momentarily and see if it can be of general help.



          Anyway, layout switching is so broken that it's not a surprise that it can do anything and its contrary... the second link here bite me a lot of time: even if you change layout, Ubuntu will often default to plain us unless you switch it back and forth, that may be your problem here.



          I'll try here to give some ideas:



          In "Internaltional Alt-Gr dead key" to have a "è" you have to press AltGr` and then e.



          I don't know if the direct AltGre is defined to be anything --- I do not have the layout handy now.



          You should be able to see the current layout in settings / region and language / Input Sources --- select the keyboard and press the small keyboard icon.



          keyboard layout



          On each key, the AltGr variants are the one on the right side. The keyboard shown is a personalized one, so it's different from the standard ones available.



          You can find more info on my (mostly silent) blog here and here, and if you still have problem, check Alt-Gr key is not working in Ubuntu 13.10 and he post linked from there.






          share|improve this answer


























          • Thanks for the reply Rmano. It didn't help fixing my problem, but it did help me to reread my question and hopefully make it more clear.

            – Mattijs
            Oct 3 '15 at 11:03








          • 1





            I suspect you are experiencing this bug --- the keyboard tend to go to "plain us" at login and then again sometime, and you need to switch back and forth to have your "Alt-Gr intl US" one. I suspect that the bug is still there because no one know why it happens.

            – Rmano
            Oct 3 '15 at 15:03













          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          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%2faskubuntu.com%2fquestions%2f679078%2faltgr-is-not-working%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          EDIT / reading again your question I understand that this one maybe is not answering you. I will let this here momentarily and see if it can be of general help.



          Anyway, layout switching is so broken that it's not a surprise that it can do anything and its contrary... the second link here bite me a lot of time: even if you change layout, Ubuntu will often default to plain us unless you switch it back and forth, that may be your problem here.



          I'll try here to give some ideas:



          In "Internaltional Alt-Gr dead key" to have a "è" you have to press AltGr` and then e.



          I don't know if the direct AltGre is defined to be anything --- I do not have the layout handy now.



          You should be able to see the current layout in settings / region and language / Input Sources --- select the keyboard and press the small keyboard icon.



          keyboard layout



          On each key, the AltGr variants are the one on the right side. The keyboard shown is a personalized one, so it's different from the standard ones available.



          You can find more info on my (mostly silent) blog here and here, and if you still have problem, check Alt-Gr key is not working in Ubuntu 13.10 and he post linked from there.






          share|improve this answer


























          • Thanks for the reply Rmano. It didn't help fixing my problem, but it did help me to reread my question and hopefully make it more clear.

            – Mattijs
            Oct 3 '15 at 11:03








          • 1





            I suspect you are experiencing this bug --- the keyboard tend to go to "plain us" at login and then again sometime, and you need to switch back and forth to have your "Alt-Gr intl US" one. I suspect that the bug is still there because no one know why it happens.

            – Rmano
            Oct 3 '15 at 15:03


















          0














          EDIT / reading again your question I understand that this one maybe is not answering you. I will let this here momentarily and see if it can be of general help.



          Anyway, layout switching is so broken that it's not a surprise that it can do anything and its contrary... the second link here bite me a lot of time: even if you change layout, Ubuntu will often default to plain us unless you switch it back and forth, that may be your problem here.



          I'll try here to give some ideas:



          In "Internaltional Alt-Gr dead key" to have a "è" you have to press AltGr` and then e.



          I don't know if the direct AltGre is defined to be anything --- I do not have the layout handy now.



          You should be able to see the current layout in settings / region and language / Input Sources --- select the keyboard and press the small keyboard icon.



          keyboard layout



          On each key, the AltGr variants are the one on the right side. The keyboard shown is a personalized one, so it's different from the standard ones available.



          You can find more info on my (mostly silent) blog here and here, and if you still have problem, check Alt-Gr key is not working in Ubuntu 13.10 and he post linked from there.






          share|improve this answer


























          • Thanks for the reply Rmano. It didn't help fixing my problem, but it did help me to reread my question and hopefully make it more clear.

            – Mattijs
            Oct 3 '15 at 11:03








          • 1





            I suspect you are experiencing this bug --- the keyboard tend to go to "plain us" at login and then again sometime, and you need to switch back and forth to have your "Alt-Gr intl US" one. I suspect that the bug is still there because no one know why it happens.

            – Rmano
            Oct 3 '15 at 15:03
















          0












          0








          0







          EDIT / reading again your question I understand that this one maybe is not answering you. I will let this here momentarily and see if it can be of general help.



          Anyway, layout switching is so broken that it's not a surprise that it can do anything and its contrary... the second link here bite me a lot of time: even if you change layout, Ubuntu will often default to plain us unless you switch it back and forth, that may be your problem here.



          I'll try here to give some ideas:



          In "Internaltional Alt-Gr dead key" to have a "è" you have to press AltGr` and then e.



          I don't know if the direct AltGre is defined to be anything --- I do not have the layout handy now.



          You should be able to see the current layout in settings / region and language / Input Sources --- select the keyboard and press the small keyboard icon.



          keyboard layout



          On each key, the AltGr variants are the one on the right side. The keyboard shown is a personalized one, so it's different from the standard ones available.



          You can find more info on my (mostly silent) blog here and here, and if you still have problem, check Alt-Gr key is not working in Ubuntu 13.10 and he post linked from there.






          share|improve this answer















          EDIT / reading again your question I understand that this one maybe is not answering you. I will let this here momentarily and see if it can be of general help.



          Anyway, layout switching is so broken that it's not a surprise that it can do anything and its contrary... the second link here bite me a lot of time: even if you change layout, Ubuntu will often default to plain us unless you switch it back and forth, that may be your problem here.



          I'll try here to give some ideas:



          In "Internaltional Alt-Gr dead key" to have a "è" you have to press AltGr` and then e.



          I don't know if the direct AltGre is defined to be anything --- I do not have the layout handy now.



          You should be able to see the current layout in settings / region and language / Input Sources --- select the keyboard and press the small keyboard icon.



          keyboard layout



          On each key, the AltGr variants are the one on the right side. The keyboard shown is a personalized one, so it's different from the standard ones available.



          You can find more info on my (mostly silent) blog here and here, and if you still have problem, check Alt-Gr key is not working in Ubuntu 13.10 and he post linked from there.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Apr 13 '17 at 12:23









          Community

          1




          1










          answered Sep 27 '15 at 18:24









          RmanoRmano

          25.4k879147




          25.4k879147













          • Thanks for the reply Rmano. It didn't help fixing my problem, but it did help me to reread my question and hopefully make it more clear.

            – Mattijs
            Oct 3 '15 at 11:03








          • 1





            I suspect you are experiencing this bug --- the keyboard tend to go to "plain us" at login and then again sometime, and you need to switch back and forth to have your "Alt-Gr intl US" one. I suspect that the bug is still there because no one know why it happens.

            – Rmano
            Oct 3 '15 at 15:03





















          • Thanks for the reply Rmano. It didn't help fixing my problem, but it did help me to reread my question and hopefully make it more clear.

            – Mattijs
            Oct 3 '15 at 11:03








          • 1





            I suspect you are experiencing this bug --- the keyboard tend to go to "plain us" at login and then again sometime, and you need to switch back and forth to have your "Alt-Gr intl US" one. I suspect that the bug is still there because no one know why it happens.

            – Rmano
            Oct 3 '15 at 15:03



















          Thanks for the reply Rmano. It didn't help fixing my problem, but it did help me to reread my question and hopefully make it more clear.

          – Mattijs
          Oct 3 '15 at 11:03







          Thanks for the reply Rmano. It didn't help fixing my problem, but it did help me to reread my question and hopefully make it more clear.

          – Mattijs
          Oct 3 '15 at 11:03






          1




          1





          I suspect you are experiencing this bug --- the keyboard tend to go to "plain us" at login and then again sometime, and you need to switch back and forth to have your "Alt-Gr intl US" one. I suspect that the bug is still there because no one know why it happens.

          – Rmano
          Oct 3 '15 at 15:03







          I suspect you are experiencing this bug --- the keyboard tend to go to "plain us" at login and then again sometime, and you need to switch back and forth to have your "Alt-Gr intl US" one. I suspect that the bug is still there because no one know why it happens.

          – Rmano
          Oct 3 '15 at 15:03




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ask Ubuntu!


          • 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%2faskubuntu.com%2fquestions%2f679078%2faltgr-is-not-working%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

          flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

          Mangá

          Eduardo VII do Reino Unido