Announcement

Collapse
No announcement yet.

Mouse stops working every timer after waking from standby

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Mouse stops working every timer after waking from standby

    As the title says, every time I wake my computer from standby, my mouse doesn't work and I have to unplug-and re-plug my mouse. The mouse is the Roccat Tyon and I am running Kubuntu 14.10 64 bit.

    #2
    I used to experience this some years back, but not recently
    I used to affect me more if my mouse was plugged in to my keyboard USB port, but not if it was plugged to the motherboard USB ports
    Also it didn't usually happen until after installing the proprietary nvidia driver
    kubuntu 20.10

    Comment


      #3
      Do you have other meece to try? - The simplest solution could well be to use a different mouse. The full solution probably involves messing with power scripts.

      USB mouse, I presume. Wired or wireless? If wireless, bluetooth or other?

      Is it the same if you suspend to disk (hibernate) as well as suspend to RAM?
      I'd rather be locked out than locked in.

      Comment


        #4
        My mouse is wired. I will test other mice very soon, as for suspending to disk, what is the command for that? KDE only has a power menu option for suspending to RAM.

        Comment


          #5
          It is just this mouse that causes the issue.

          Comment


            #6
            How keen are you to solve this problem for this specific mouse?

            Might be worth starting with lsusb output with this mouse plugged in and with a different mouse.

            Originally posted by Kirov123 View Post
            as for suspending to disk, what is the command for that? KDE only has a power menu option for suspending to RAM.
            Hibernation is disabled by default. If you want to enable it, you need a page like this for your version: https://help.ubuntu.com/12.04/ubuntu...hibernate.html
            I'd rather be locked out than locked in.

            Comment


              #7
              I would very much like to solve this issue. I tested the hibernate command, it doesn't work fully, as chrome was not saved, however, my mouse did continue to work. I also ran
              Code:
              lsusb
              after restoring from standby before unplugging and re-plugging my mouse, and it did show my mouse in the list. I am running the Nvidia drivers, my of searching bug reports shows that these things may be related.

              Comment


                #8
                Ignore hibernation for now!

                Post the output of lsusb with the problematic mouse and then with one that works.
                I'd rather be locked out than locked in.

                Comment


                  #9
                  This is lsusb with the problem mouse before making it work:
                  Code:
                  Bus 002 Device 004: ID 0930:a001 Toshiba Corp. 
                  Bus 002 Device 003: ID 18e3:9106 Fitipower Integrated Technology Inc 
                  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
                  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
                  Bus 001 Device 005: ID 050d:705a Belkin Components F5D7050 Wireless G Adapter v3000 [Ralink RT2571W]
                  Bus 001 Device 004: ID 1e7d:2e4a ROCCAT 
                  Bus 001 Device 003: ID 046d:c24d Logitech, Inc. 
                  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
                  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
                  (the mouse is the one called ROCCAT)

                  after making the mouse work, lsusb returns this:
                  Code:
                  Bus 002 Device 004: ID 0930:a001 Toshiba Corp. Bus 002 Device 003: ID 18e3:9106 Fitipower Integrated Technology Inc 
                  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
                  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
                  Bus 001 Device 005: ID 050d:705a Belkin Components F5D7050 Wireless G Adapter v3000 [Ralink RT2571W]
                  Bus 001 Device 004: ID 1e7d:2e4a ROCCAT 
                  Bus 001 Device 003: ID 046d:c24d Logitech, Inc. 
                  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
                  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
                  and running lsusb with a different mouse returns this:
                  Code:
                  Bus 002 Device 004: ID 0930:a001 Toshiba Corp. Bus 002 Device 003: ID 18e3:9106 Fitipower Integrated Technology Inc 
                  Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
                  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
                  Bus 001 Device 005: ID 050d:705a Belkin Components F5D7050 Wireless G Adapter v3000 [Ralink RT2571W]
                  Bus 001 Device 009: ID 046d:c019 Logitech, Inc. Optical Tilt Wheel Mouse
                  Bus 001 Device 003: ID 046d:c24d Logitech, Inc. 
                  Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
                  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
                  Last edited by Kirov123; Mar 09, 2015, 11:00 PM.

                  Comment

                  Working...
                  X