Bug 678322 - keyboard stucks after wakeup from suspend to RAM
Summary: keyboard stucks after wakeup from suspend to RAM
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-17 15:32 UTC by Marcus Moeller
Modified: 2012-06-13 14:01 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-13 14:01:57 UTC
Type: ---


Attachments (Terms of Use)

Description Marcus Moeller 2011-02-17 15:32:22 UTC
When I close the lid of my laptop, the system suspends, but after resume the keyboard stucks in X and on console. Tested on F15 Alpha TC2 Desktop with GNOME 3.

Comment 1 Chuck Ebbert 2011-02-18 23:26:23 UTC
Can you get SSH access to the machine when it fails like that? And can you look in the logs to see if there are any error messages during resume? See bug 676446, which may be a similar problem. If you can get remote access, try the workaround from that bug.

Comment 2 Marcus Moeller 2011-02-28 20:31:23 UTC
Dear Chuck.

Sorry, the mentioned woraround does not fix my issue. Also with stucked, I do not mean it does not work at all but it's getting kind of slow and does not accept all inputs directly.

Besides that, touchpad is also stucked, which means if you do not move the cursor for a while and restart moving it, it hangs for 3-5 seconds.

The keyboard problem is also noticable on virtual consoles.

Greets
Marcus

Comment 3 Marcus Moeller 2012-06-13 14:01:57 UTC
Works in F17


Note You need to log in before you can comment on or make changes to this bug.