Managed to uninstall package for keyboard and mouse input. (libinput?)

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












The keyboard and mouse problem



I am running a laptop with touchpad and keyboard integrated, and I have previously had an issue where my touchpad would make my mouse go in a grid-like pattern. Upon investigating solutions to this issue, I managed to do something incredibly stupid. I removed a package that supposedly controlled my input, and now I can't log in or do anything but hold the power button down when I log into normal mode. Recovery mode works well, but Re-installing packages in recovery seem to not reflect in normal mode.



On the laptop (Lenovo Yoga 710) I have Deepin linux 15.5 installed.
All I know and I can recall I did before I chose to restart it, was that i was uninstalling a package starting at: xorg-xserver-input-*but can't really specify the exact package I removed.



As I stated above, I think that my recovery mode doesn't reflect package changes on normal mode (i could be wrong), as I can't get my mouse or keyboard working at all when I then re-log into normal mode. I have tried reinstalling xorg-xserver-input-all and even tried with wildcards. Am I missing some configuration?



It's critical for me to get it working until monday, and I guess I am the reason why I made it this way. Has anyone a clue where I could start to get my mouse and keyboard working again? I tried external devices over USB ad bluetooth but none of the input devices are recognised.







share|improve this question























    up vote
    1
    down vote

    favorite












    The keyboard and mouse problem



    I am running a laptop with touchpad and keyboard integrated, and I have previously had an issue where my touchpad would make my mouse go in a grid-like pattern. Upon investigating solutions to this issue, I managed to do something incredibly stupid. I removed a package that supposedly controlled my input, and now I can't log in or do anything but hold the power button down when I log into normal mode. Recovery mode works well, but Re-installing packages in recovery seem to not reflect in normal mode.



    On the laptop (Lenovo Yoga 710) I have Deepin linux 15.5 installed.
    All I know and I can recall I did before I chose to restart it, was that i was uninstalling a package starting at: xorg-xserver-input-*but can't really specify the exact package I removed.



    As I stated above, I think that my recovery mode doesn't reflect package changes on normal mode (i could be wrong), as I can't get my mouse or keyboard working at all when I then re-log into normal mode. I have tried reinstalling xorg-xserver-input-all and even tried with wildcards. Am I missing some configuration?



    It's critical for me to get it working until monday, and I guess I am the reason why I made it this way. Has anyone a clue where I could start to get my mouse and keyboard working again? I tried external devices over USB ad bluetooth but none of the input devices are recognised.







    share|improve this question





















      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      The keyboard and mouse problem



      I am running a laptop with touchpad and keyboard integrated, and I have previously had an issue where my touchpad would make my mouse go in a grid-like pattern. Upon investigating solutions to this issue, I managed to do something incredibly stupid. I removed a package that supposedly controlled my input, and now I can't log in or do anything but hold the power button down when I log into normal mode. Recovery mode works well, but Re-installing packages in recovery seem to not reflect in normal mode.



      On the laptop (Lenovo Yoga 710) I have Deepin linux 15.5 installed.
      All I know and I can recall I did before I chose to restart it, was that i was uninstalling a package starting at: xorg-xserver-input-*but can't really specify the exact package I removed.



      As I stated above, I think that my recovery mode doesn't reflect package changes on normal mode (i could be wrong), as I can't get my mouse or keyboard working at all when I then re-log into normal mode. I have tried reinstalling xorg-xserver-input-all and even tried with wildcards. Am I missing some configuration?



      It's critical for me to get it working until monday, and I guess I am the reason why I made it this way. Has anyone a clue where I could start to get my mouse and keyboard working again? I tried external devices over USB ad bluetooth but none of the input devices are recognised.







      share|improve this question











      The keyboard and mouse problem



      I am running a laptop with touchpad and keyboard integrated, and I have previously had an issue where my touchpad would make my mouse go in a grid-like pattern. Upon investigating solutions to this issue, I managed to do something incredibly stupid. I removed a package that supposedly controlled my input, and now I can't log in or do anything but hold the power button down when I log into normal mode. Recovery mode works well, but Re-installing packages in recovery seem to not reflect in normal mode.



      On the laptop (Lenovo Yoga 710) I have Deepin linux 15.5 installed.
      All I know and I can recall I did before I chose to restart it, was that i was uninstalling a package starting at: xorg-xserver-input-*but can't really specify the exact package I removed.



      As I stated above, I think that my recovery mode doesn't reflect package changes on normal mode (i could be wrong), as I can't get my mouse or keyboard working at all when I then re-log into normal mode. I have tried reinstalling xorg-xserver-input-all and even tried with wildcards. Am I missing some configuration?



      It's critical for me to get it working until monday, and I guess I am the reason why I made it this way. Has anyone a clue where I could start to get my mouse and keyboard working again? I tried external devices over USB ad bluetooth but none of the input devices are recognised.









      share|improve this question










      share|improve this question




      share|improve this question









      asked Apr 27 at 10:21









      denNorske

      1084




      1084




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          1
          down vote



          accepted










          Have you got a second machine on the network you can SSH from?



          If so, you can ssh in, and manually install libinput as per this documentation:



          https://wayland.freedesktop.org/libinput/doc/latest/building_libinput.html



          If ssh is not an option, then I would suggest booting a recovery CD/USB, mount your deepin main partition and compile libinput there as per the documentation above.






          share|improve this answer





















          • Oh ssh - that's a hilariously good suggestion. I'll give it a shot. I didn't realise it was was an option before now.
            – denNorske
            Apr 27 at 13:27











          • Hello again - Didn't work through SSH, but managed to CHROOT the correct partition (/mnt/sda5) in recovery, and then reinstall the packages needed.That solved my problem. Thanks for your input, it was clever.
            – denNorske
            Apr 28 at 9:30










          • great, glad you got it working @denNorske :)
            – RobotJohnny
            Apr 28 at 11:30










          Your Answer







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

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

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );








           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f440384%2fmanaged-to-uninstall-package-for-keyboard-and-mouse-input-libinput%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          1
          down vote



          accepted










          Have you got a second machine on the network you can SSH from?



          If so, you can ssh in, and manually install libinput as per this documentation:



          https://wayland.freedesktop.org/libinput/doc/latest/building_libinput.html



          If ssh is not an option, then I would suggest booting a recovery CD/USB, mount your deepin main partition and compile libinput there as per the documentation above.






          share|improve this answer





















          • Oh ssh - that's a hilariously good suggestion. I'll give it a shot. I didn't realise it was was an option before now.
            – denNorske
            Apr 27 at 13:27











          • Hello again - Didn't work through SSH, but managed to CHROOT the correct partition (/mnt/sda5) in recovery, and then reinstall the packages needed.That solved my problem. Thanks for your input, it was clever.
            – denNorske
            Apr 28 at 9:30










          • great, glad you got it working @denNorske :)
            – RobotJohnny
            Apr 28 at 11:30














          up vote
          1
          down vote



          accepted










          Have you got a second machine on the network you can SSH from?



          If so, you can ssh in, and manually install libinput as per this documentation:



          https://wayland.freedesktop.org/libinput/doc/latest/building_libinput.html



          If ssh is not an option, then I would suggest booting a recovery CD/USB, mount your deepin main partition and compile libinput there as per the documentation above.






          share|improve this answer





















          • Oh ssh - that's a hilariously good suggestion. I'll give it a shot. I didn't realise it was was an option before now.
            – denNorske
            Apr 27 at 13:27











          • Hello again - Didn't work through SSH, but managed to CHROOT the correct partition (/mnt/sda5) in recovery, and then reinstall the packages needed.That solved my problem. Thanks for your input, it was clever.
            – denNorske
            Apr 28 at 9:30










          • great, glad you got it working @denNorske :)
            – RobotJohnny
            Apr 28 at 11:30












          up vote
          1
          down vote



          accepted







          up vote
          1
          down vote



          accepted






          Have you got a second machine on the network you can SSH from?



          If so, you can ssh in, and manually install libinput as per this documentation:



          https://wayland.freedesktop.org/libinput/doc/latest/building_libinput.html



          If ssh is not an option, then I would suggest booting a recovery CD/USB, mount your deepin main partition and compile libinput there as per the documentation above.






          share|improve this answer













          Have you got a second machine on the network you can SSH from?



          If so, you can ssh in, and manually install libinput as per this documentation:



          https://wayland.freedesktop.org/libinput/doc/latest/building_libinput.html



          If ssh is not an option, then I would suggest booting a recovery CD/USB, mount your deepin main partition and compile libinput there as per the documentation above.







          share|improve this answer













          share|improve this answer



          share|improve this answer











          answered Apr 27 at 11:30









          RobotJohnny

          407212




          407212











          • Oh ssh - that's a hilariously good suggestion. I'll give it a shot. I didn't realise it was was an option before now.
            – denNorske
            Apr 27 at 13:27











          • Hello again - Didn't work through SSH, but managed to CHROOT the correct partition (/mnt/sda5) in recovery, and then reinstall the packages needed.That solved my problem. Thanks for your input, it was clever.
            – denNorske
            Apr 28 at 9:30










          • great, glad you got it working @denNorske :)
            – RobotJohnny
            Apr 28 at 11:30
















          • Oh ssh - that's a hilariously good suggestion. I'll give it a shot. I didn't realise it was was an option before now.
            – denNorske
            Apr 27 at 13:27











          • Hello again - Didn't work through SSH, but managed to CHROOT the correct partition (/mnt/sda5) in recovery, and then reinstall the packages needed.That solved my problem. Thanks for your input, it was clever.
            – denNorske
            Apr 28 at 9:30










          • great, glad you got it working @denNorske :)
            – RobotJohnny
            Apr 28 at 11:30















          Oh ssh - that's a hilariously good suggestion. I'll give it a shot. I didn't realise it was was an option before now.
          – denNorske
          Apr 27 at 13:27





          Oh ssh - that's a hilariously good suggestion. I'll give it a shot. I didn't realise it was was an option before now.
          – denNorske
          Apr 27 at 13:27













          Hello again - Didn't work through SSH, but managed to CHROOT the correct partition (/mnt/sda5) in recovery, and then reinstall the packages needed.That solved my problem. Thanks for your input, it was clever.
          – denNorske
          Apr 28 at 9:30




          Hello again - Didn't work through SSH, but managed to CHROOT the correct partition (/mnt/sda5) in recovery, and then reinstall the packages needed.That solved my problem. Thanks for your input, it was clever.
          – denNorske
          Apr 28 at 9:30












          great, glad you got it working @denNorske :)
          – RobotJohnny
          Apr 28 at 11:30




          great, glad you got it working @denNorske :)
          – RobotJohnny
          Apr 28 at 11:30












           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f440384%2fmanaged-to-uninstall-package-for-keyboard-and-mouse-input-libinput%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay