V key not working, down key stuck only in GRUB












0















I was merrily editing away in nano, using CTRL (okay, Shift+t is also not working...) Ctrl+v to page down through the document. Suddenly the paging down stopped, and a bunch of Vs started appearing, as though the key was stuck. I managed to stop it by pressing some other keys, and then realized that I could no longer page down through ctrl+v. I later realized that V was also no longer working, so I tried pressing all the keys, which didn't work, so I rebooted.



On rebooting I noticed that the down arrow seemed to be stuck, so grub tried to choose the bottom option in the boot menu. Pressing down to try to unstick the key didn't work, but holding down the up key eventually managed to get to the top option and I was able to boot. Funny thing is, the down key is only stuck in boot.



I think this is a software issue due to the sudden appearance after using nano, and the "t works, but Shift+t doesn't" issue I discovered writing this question. I've tried resetting all keyboard shortcuts in system settings, and rebooting the laptop multiple times. It is a laptop, so unplugging and re-plugging the keyboard is rather involved, and something I haven't tried yet. Inserting V from Characters and pasting by right-click is getting kind of old.



TL;DR: V key is not working at all, down key stuck only in BIOS, t works but Shift+t doesn't. This happened while using nano. Tried resetting keyboard shortcuts, computer is a laptop. Ideas?



Ubuntu 18.04, kernel 4.19.9



EDIT: While it appears that there is some input while initially booting (the notification for the shortcut keys for system setup and boot menu comes up) the down arrow is not actually stuck in BIOS, only in grub.










share|improve this question









New contributor




IronEagle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0















    I was merrily editing away in nano, using CTRL (okay, Shift+t is also not working...) Ctrl+v to page down through the document. Suddenly the paging down stopped, and a bunch of Vs started appearing, as though the key was stuck. I managed to stop it by pressing some other keys, and then realized that I could no longer page down through ctrl+v. I later realized that V was also no longer working, so I tried pressing all the keys, which didn't work, so I rebooted.



    On rebooting I noticed that the down arrow seemed to be stuck, so grub tried to choose the bottom option in the boot menu. Pressing down to try to unstick the key didn't work, but holding down the up key eventually managed to get to the top option and I was able to boot. Funny thing is, the down key is only stuck in boot.



    I think this is a software issue due to the sudden appearance after using nano, and the "t works, but Shift+t doesn't" issue I discovered writing this question. I've tried resetting all keyboard shortcuts in system settings, and rebooting the laptop multiple times. It is a laptop, so unplugging and re-plugging the keyboard is rather involved, and something I haven't tried yet. Inserting V from Characters and pasting by right-click is getting kind of old.



    TL;DR: V key is not working at all, down key stuck only in BIOS, t works but Shift+t doesn't. This happened while using nano. Tried resetting keyboard shortcuts, computer is a laptop. Ideas?



    Ubuntu 18.04, kernel 4.19.9



    EDIT: While it appears that there is some input while initially booting (the notification for the shortcut keys for system setup and boot menu comes up) the down arrow is not actually stuck in BIOS, only in grub.










    share|improve this question









    New contributor




    IronEagle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      I was merrily editing away in nano, using CTRL (okay, Shift+t is also not working...) Ctrl+v to page down through the document. Suddenly the paging down stopped, and a bunch of Vs started appearing, as though the key was stuck. I managed to stop it by pressing some other keys, and then realized that I could no longer page down through ctrl+v. I later realized that V was also no longer working, so I tried pressing all the keys, which didn't work, so I rebooted.



      On rebooting I noticed that the down arrow seemed to be stuck, so grub tried to choose the bottom option in the boot menu. Pressing down to try to unstick the key didn't work, but holding down the up key eventually managed to get to the top option and I was able to boot. Funny thing is, the down key is only stuck in boot.



      I think this is a software issue due to the sudden appearance after using nano, and the "t works, but Shift+t doesn't" issue I discovered writing this question. I've tried resetting all keyboard shortcuts in system settings, and rebooting the laptop multiple times. It is a laptop, so unplugging and re-plugging the keyboard is rather involved, and something I haven't tried yet. Inserting V from Characters and pasting by right-click is getting kind of old.



      TL;DR: V key is not working at all, down key stuck only in BIOS, t works but Shift+t doesn't. This happened while using nano. Tried resetting keyboard shortcuts, computer is a laptop. Ideas?



      Ubuntu 18.04, kernel 4.19.9



      EDIT: While it appears that there is some input while initially booting (the notification for the shortcut keys for system setup and boot menu comes up) the down arrow is not actually stuck in BIOS, only in grub.










      share|improve this question









      New contributor




      IronEagle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      I was merrily editing away in nano, using CTRL (okay, Shift+t is also not working...) Ctrl+v to page down through the document. Suddenly the paging down stopped, and a bunch of Vs started appearing, as though the key was stuck. I managed to stop it by pressing some other keys, and then realized that I could no longer page down through ctrl+v. I later realized that V was also no longer working, so I tried pressing all the keys, which didn't work, so I rebooted.



      On rebooting I noticed that the down arrow seemed to be stuck, so grub tried to choose the bottom option in the boot menu. Pressing down to try to unstick the key didn't work, but holding down the up key eventually managed to get to the top option and I was able to boot. Funny thing is, the down key is only stuck in boot.



      I think this is a software issue due to the sudden appearance after using nano, and the "t works, but Shift+t doesn't" issue I discovered writing this question. I've tried resetting all keyboard shortcuts in system settings, and rebooting the laptop multiple times. It is a laptop, so unplugging and re-plugging the keyboard is rather involved, and something I haven't tried yet. Inserting V from Characters and pasting by right-click is getting kind of old.



      TL;DR: V key is not working at all, down key stuck only in BIOS, t works but Shift+t doesn't. This happened while using nano. Tried resetting keyboard shortcuts, computer is a laptop. Ideas?



      Ubuntu 18.04, kernel 4.19.9



      EDIT: While it appears that there is some input while initially booting (the notification for the shortcut keys for system setup and boot menu comes up) the down arrow is not actually stuck in BIOS, only in grub.







      keyboard keyboard-layout






      share|improve this question









      New contributor




      IronEagle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      IronEagle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited yesterday







      IronEagle













      New contributor




      IronEagle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked yesterday









      IronEagleIronEagle

      1013




      1013




      New contributor




      IronEagle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      IronEagle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      IronEagle is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes











          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
          });


          }
          });






          IronEagle is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1115181%2fv-key-not-working-down-key-stuck-only-in-grub%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          IronEagle is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          IronEagle is a new contributor. Be nice, and check out our Code of Conduct.













          IronEagle is a new contributor. Be nice, and check out our Code of Conduct.












          IronEagle is a new contributor. Be nice, and check out our Code of Conduct.
















          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%2f1115181%2fv-key-not-working-down-key-stuck-only-in-grub%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

          數位音樂下載

          When can things happen in Etherscan, such as the picture below?

          格利澤436b