Red Hat Bugzilla – Bug 848037
Mouse doesn't work after suspend.
Last modified: 2013-08-01 13:22:00 EDT
Description of problem:
I have cordless optical mouse, USB, Logitech. When I turn on computer after suspend mouse doesn't work, cursor is at the point where it was while computer go suspend and doesn't move when i move the mouse.
Version-Release number of selected component (if applicable):
I don't know.
Steps to Reproduce:
My motherboard is ga p41t-d3p.
[savpether@DT-Piotr ~]$ lsusb
Bus 001 Device 002: ID 054c:01bd Sony Corp. MRW62E Multi-Card Reader/Writer
Bus 004 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I have the same issue after upgrading to kernel 3.5.2-1.fc17.x86_64. I have a Logitech combined receiver which handles both the wireless keyboard and mouse.
Bus 001 Device 012: ID 046d:c513 Logitech, Inc. MX3000 Cordless Desktop Receiver
After suspend the keyboard portion works, but the mouse does not. If you remove the receiver and re-plug it, then everything works again.
Previous kernel 3.4.6-2.fc17 did not exhibit such behaviour and the mouse did work after suspend.
"If you remove the receiver and re-plug it, then everything works again."
Ye, it works for me, until I suspend computer again :D
Someone already knows something about this bug? Extremely kept making life ...
Yesterday I updated kernel, the bug still exists.
This is still going on an not resolved. 3.4.6 is working fine so must be a regression....
This issue was reported on Launchpad and a patch was produced by Kevin Daughtridge (since sent upstream).
Is it possible to include the following patch until kernel 3.6 is packaged?
(In reply to comment #7)
> This issue was reported on Launchpad and a patch was produced by Kevin
> Daughtridge (since sent upstream).
> Is it possible to include the following patch until kernel 3.6 is packaged?
No. Also, it's not fixed in 3.6 either.
The same comment as made in comment #11 of the lauchpad bug applies here. Once it is in an upstream tree, we'll cherry pick it from there. It will probably get included in a stable tree as well if it is a regression in 3.5.
Version 3 of the patch seems to be doing best thus far:
OK, this went upstream as:
Author: Kevin Daughtridge <email@example.com>
Date: Thu Sep 20 12:00:32 2012 -0700
HID: keep dev_rdesc unmodified and use it for comparisons
I've asked the input maintainer to include it in stable. Until then, I'll get it backported in Fedora.
Please try this scratch kernel after it finishes building. It includes the mentioned commit.
I have the same problem... additional info:
1) I have the option set to disable the mouse while typing (System Settings/mouse)
2) I am using the touchpad on an old 15" MacBook Pro (old machine version 4,1)
p.s., the mouse DOES work when I plug in a USB mouse even when my touchpad pointer is frozen. I think the touchpad is then unfrozen after that.
(In reply to comment #12)
> p.s., the mouse DOES work when I plug in a USB mouse even when my touchpad
> pointer is frozen. I think the touchpad is then unfrozen after that.
p.s., p.s. I can no longer produce the error. I tried combinations of enabling and disabling the "disable the mouse while typing" option and the touchpad scrolling options, but the mouse/touchpad pointer is no longer freezing after suspend. I am not sure if I updated Fedora after I last observed the problem, but I had installed Fedora 17 only last week and did not update yum for a couple days.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.