Ubuntu 18.04 mouse issues after suspend












1














I am using Ubuntu 18.04 running on lenovo carbon yoga x1 (1st Gen).
Everything work fine most of the time, but after I put the computer to suspend and then wake it up in the am, the mouse goes a little whack:
- the left click of the mouse doesn't work.
- the sliding lock screen for example looks like it's stuck in drag mode, I can slide up and down but not all the way, and I have to power cycle the machine to get to the login box.










share|improve this question






















  • Read man pm-action to see what steps your system goes through when you suspend/resume. If you find a fix, this is where it would go. What do lsusb and sudo lshw tell you about your mouse?
    – waltinator
    Jul 13 '18 at 6:14










  • I ran both commands and read the man, I'm not sure how that helps. Happy to share the output. After suspend / hybernaite, I actaully have to reboot twice until the mouse comes back to normal work...
    – Dory Zidon
    Jul 13 '18 at 11:42










  • How am I suppose to fix this? I'm really unsure..
    – Dory Zidon
    Jul 13 '18 at 11:42










  • @waltinator happy to follow your instructions.
    – Dory Zidon
    Jul 13 '18 at 11:43
















1














I am using Ubuntu 18.04 running on lenovo carbon yoga x1 (1st Gen).
Everything work fine most of the time, but after I put the computer to suspend and then wake it up in the am, the mouse goes a little whack:
- the left click of the mouse doesn't work.
- the sliding lock screen for example looks like it's stuck in drag mode, I can slide up and down but not all the way, and I have to power cycle the machine to get to the login box.










share|improve this question






















  • Read man pm-action to see what steps your system goes through when you suspend/resume. If you find a fix, this is where it would go. What do lsusb and sudo lshw tell you about your mouse?
    – waltinator
    Jul 13 '18 at 6:14










  • I ran both commands and read the man, I'm not sure how that helps. Happy to share the output. After suspend / hybernaite, I actaully have to reboot twice until the mouse comes back to normal work...
    – Dory Zidon
    Jul 13 '18 at 11:42










  • How am I suppose to fix this? I'm really unsure..
    – Dory Zidon
    Jul 13 '18 at 11:42










  • @waltinator happy to follow your instructions.
    – Dory Zidon
    Jul 13 '18 at 11:43














1












1








1


1





I am using Ubuntu 18.04 running on lenovo carbon yoga x1 (1st Gen).
Everything work fine most of the time, but after I put the computer to suspend and then wake it up in the am, the mouse goes a little whack:
- the left click of the mouse doesn't work.
- the sliding lock screen for example looks like it's stuck in drag mode, I can slide up and down but not all the way, and I have to power cycle the machine to get to the login box.










share|improve this question













I am using Ubuntu 18.04 running on lenovo carbon yoga x1 (1st Gen).
Everything work fine most of the time, but after I put the computer to suspend and then wake it up in the am, the mouse goes a little whack:
- the left click of the mouse doesn't work.
- the sliding lock screen for example looks like it's stuck in drag mode, I can slide up and down but not all the way, and I have to power cycle the machine to get to the login box.







18.04 mouse suspend power-management lenovo






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jul 13 '18 at 5:59









Dory Zidon

1062




1062












  • Read man pm-action to see what steps your system goes through when you suspend/resume. If you find a fix, this is where it would go. What do lsusb and sudo lshw tell you about your mouse?
    – waltinator
    Jul 13 '18 at 6:14










  • I ran both commands and read the man, I'm not sure how that helps. Happy to share the output. After suspend / hybernaite, I actaully have to reboot twice until the mouse comes back to normal work...
    – Dory Zidon
    Jul 13 '18 at 11:42










  • How am I suppose to fix this? I'm really unsure..
    – Dory Zidon
    Jul 13 '18 at 11:42










  • @waltinator happy to follow your instructions.
    – Dory Zidon
    Jul 13 '18 at 11:43


















  • Read man pm-action to see what steps your system goes through when you suspend/resume. If you find a fix, this is where it would go. What do lsusb and sudo lshw tell you about your mouse?
    – waltinator
    Jul 13 '18 at 6:14










  • I ran both commands and read the man, I'm not sure how that helps. Happy to share the output. After suspend / hybernaite, I actaully have to reboot twice until the mouse comes back to normal work...
    – Dory Zidon
    Jul 13 '18 at 11:42










  • How am I suppose to fix this? I'm really unsure..
    – Dory Zidon
    Jul 13 '18 at 11:42










  • @waltinator happy to follow your instructions.
    – Dory Zidon
    Jul 13 '18 at 11:43
















Read man pm-action to see what steps your system goes through when you suspend/resume. If you find a fix, this is where it would go. What do lsusb and sudo lshw tell you about your mouse?
– waltinator
Jul 13 '18 at 6:14




Read man pm-action to see what steps your system goes through when you suspend/resume. If you find a fix, this is where it would go. What do lsusb and sudo lshw tell you about your mouse?
– waltinator
Jul 13 '18 at 6:14












I ran both commands and read the man, I'm not sure how that helps. Happy to share the output. After suspend / hybernaite, I actaully have to reboot twice until the mouse comes back to normal work...
– Dory Zidon
Jul 13 '18 at 11:42




I ran both commands and read the man, I'm not sure how that helps. Happy to share the output. After suspend / hybernaite, I actaully have to reboot twice until the mouse comes back to normal work...
– Dory Zidon
Jul 13 '18 at 11:42












How am I suppose to fix this? I'm really unsure..
– Dory Zidon
Jul 13 '18 at 11:42




How am I suppose to fix this? I'm really unsure..
– Dory Zidon
Jul 13 '18 at 11:42












@waltinator happy to follow your instructions.
– Dory Zidon
Jul 13 '18 at 11:43




@waltinator happy to follow your instructions.
– Dory Zidon
Jul 13 '18 at 11:43










2 Answers
2






active

oldest

votes


















1














Faced this problem today and this is what worked for me.



Make sure your device module is psmouse by running,



lsmod | grep psmouse


if its not, find the relavant module name.



$ cd /lib/systemd/system-sleep/
$ sudo vi fixtouchpad


then paste and save the following



#!/bin/bash
[ "$1" = "post" ] && exec modprobe psmouse
[ "$1" = "pre" ] && exec rmmod psmouse
exit 0


This will reload your psmouse module after resuming. Replace 'psmouse' with your module name.



Be sure to make the script executable



sudo chmod +x fixtouchpad





share|improve this answer































    0














    I was having similar issues with 18.04 and they actually got worse since upgrading to 18.10. I have a Logitech "unifying receiver" that has both a mouse and keyboard paired with it. When resuming from sleep, fairly often either the mouse or the keyboard no longer work. I don't remember suffering these issues with 17.10...



    What just fixed it for me was:



    for mod in hid_logitech_hidpp hid_logitech_dj usbhid; do
    sudo rmmod $mod && sleep 3
    sudo modprobe $mod
    done


    (not sure what the various modules are for but they looked like good candidates). I used my laptop's integrated keyboard to type this. If the approach works, I might consider @imeshU's approach to hook this into the System-D sleep/resume process.






    share|improve this answer




















      protected by Community Dec 18 '18 at 17:02



      Thank you for your interest in this question.
      Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



      Would you like to answer one of these unanswered questions instead?














      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1














      Faced this problem today and this is what worked for me.



      Make sure your device module is psmouse by running,



      lsmod | grep psmouse


      if its not, find the relavant module name.



      $ cd /lib/systemd/system-sleep/
      $ sudo vi fixtouchpad


      then paste and save the following



      #!/bin/bash
      [ "$1" = "post" ] && exec modprobe psmouse
      [ "$1" = "pre" ] && exec rmmod psmouse
      exit 0


      This will reload your psmouse module after resuming. Replace 'psmouse' with your module name.



      Be sure to make the script executable



      sudo chmod +x fixtouchpad





      share|improve this answer




























        1














        Faced this problem today and this is what worked for me.



        Make sure your device module is psmouse by running,



        lsmod | grep psmouse


        if its not, find the relavant module name.



        $ cd /lib/systemd/system-sleep/
        $ sudo vi fixtouchpad


        then paste and save the following



        #!/bin/bash
        [ "$1" = "post" ] && exec modprobe psmouse
        [ "$1" = "pre" ] && exec rmmod psmouse
        exit 0


        This will reload your psmouse module after resuming. Replace 'psmouse' with your module name.



        Be sure to make the script executable



        sudo chmod +x fixtouchpad





        share|improve this answer


























          1












          1








          1






          Faced this problem today and this is what worked for me.



          Make sure your device module is psmouse by running,



          lsmod | grep psmouse


          if its not, find the relavant module name.



          $ cd /lib/systemd/system-sleep/
          $ sudo vi fixtouchpad


          then paste and save the following



          #!/bin/bash
          [ "$1" = "post" ] && exec modprobe psmouse
          [ "$1" = "pre" ] && exec rmmod psmouse
          exit 0


          This will reload your psmouse module after resuming. Replace 'psmouse' with your module name.



          Be sure to make the script executable



          sudo chmod +x fixtouchpad





          share|improve this answer














          Faced this problem today and this is what worked for me.



          Make sure your device module is psmouse by running,



          lsmod | grep psmouse


          if its not, find the relavant module name.



          $ cd /lib/systemd/system-sleep/
          $ sudo vi fixtouchpad


          then paste and save the following



          #!/bin/bash
          [ "$1" = "post" ] && exec modprobe psmouse
          [ "$1" = "pre" ] && exec rmmod psmouse
          exit 0


          This will reload your psmouse module after resuming. Replace 'psmouse' with your module name.



          Be sure to make the script executable



          sudo chmod +x fixtouchpad






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Oct 5 '18 at 9:38









          abu_bua

          3,25681026




          3,25681026










          answered Sep 8 '18 at 9:36









          imeshU

          111




          111

























              0














              I was having similar issues with 18.04 and they actually got worse since upgrading to 18.10. I have a Logitech "unifying receiver" that has both a mouse and keyboard paired with it. When resuming from sleep, fairly often either the mouse or the keyboard no longer work. I don't remember suffering these issues with 17.10...



              What just fixed it for me was:



              for mod in hid_logitech_hidpp hid_logitech_dj usbhid; do
              sudo rmmod $mod && sleep 3
              sudo modprobe $mod
              done


              (not sure what the various modules are for but they looked like good candidates). I used my laptop's integrated keyboard to type this. If the approach works, I might consider @imeshU's approach to hook this into the System-D sleep/resume process.






              share|improve this answer


























                0














                I was having similar issues with 18.04 and they actually got worse since upgrading to 18.10. I have a Logitech "unifying receiver" that has both a mouse and keyboard paired with it. When resuming from sleep, fairly often either the mouse or the keyboard no longer work. I don't remember suffering these issues with 17.10...



                What just fixed it for me was:



                for mod in hid_logitech_hidpp hid_logitech_dj usbhid; do
                sudo rmmod $mod && sleep 3
                sudo modprobe $mod
                done


                (not sure what the various modules are for but they looked like good candidates). I used my laptop's integrated keyboard to type this. If the approach works, I might consider @imeshU's approach to hook this into the System-D sleep/resume process.






                share|improve this answer
























                  0












                  0








                  0






                  I was having similar issues with 18.04 and they actually got worse since upgrading to 18.10. I have a Logitech "unifying receiver" that has both a mouse and keyboard paired with it. When resuming from sleep, fairly often either the mouse or the keyboard no longer work. I don't remember suffering these issues with 17.10...



                  What just fixed it for me was:



                  for mod in hid_logitech_hidpp hid_logitech_dj usbhid; do
                  sudo rmmod $mod && sleep 3
                  sudo modprobe $mod
                  done


                  (not sure what the various modules are for but they looked like good candidates). I used my laptop's integrated keyboard to type this. If the approach works, I might consider @imeshU's approach to hook this into the System-D sleep/resume process.






                  share|improve this answer












                  I was having similar issues with 18.04 and they actually got worse since upgrading to 18.10. I have a Logitech "unifying receiver" that has both a mouse and keyboard paired with it. When resuming from sleep, fairly often either the mouse or the keyboard no longer work. I don't remember suffering these issues with 17.10...



                  What just fixed it for me was:



                  for mod in hid_logitech_hidpp hid_logitech_dj usbhid; do
                  sudo rmmod $mod && sleep 3
                  sudo modprobe $mod
                  done


                  (not sure what the various modules are for but they looked like good candidates). I used my laptop's integrated keyboard to type this. If the approach works, I might consider @imeshU's approach to hook this into the System-D sleep/resume process.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Dec 18 '18 at 16:54









                  sxc731

                  31128




                  31128

















                      protected by Community Dec 18 '18 at 17:02



                      Thank you for your interest in this question.
                      Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                      Would you like to answer one of these unanswered questions instead?



                      Popular posts from this blog

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

                      Mangá

                       ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕