This bug was fixed in the package linux - 2.6.24-24.56
---
linux (2.6.24-24.56) hardy-proposed; urgency=low
[Stefan Bader]
* Rebuild of 2.6.24-24.54 with 2.6.24-24.55 security release applied
linux (2.6.24-24.54) hardy-proposed; urgency=low
[Andy Whitcroft]
* SAUCE: do not
** Tags added: hw-specific
--
control key "stuck" after resume on Dell 1420n
https://bugs.launchpad.net/bugs/213988
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.u
Accepted linux into hardy-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: linux (Ubuntu Hardy)
Please set the development release task appropriately for SRUs, closing
karmic one. Otherwise they will stay around indefinitively.
Adding missing hardy task as well.
** Also affects: linux (Ubuntu Hardy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Fi
** Description changed:
+ SRU Justification:
+
+ Impact: This bug causes keyboard to spew garbage on resume and might
+ cause it to go into an unknown state as reported by the bug reporter
+
+ Fix: This patch that is upstream since 2.6.26 (and is contained in
+ Intrepid and Jaunty)
+
+ ---
+
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
control key "stuck" after resume on Dell 1420n
https://bugs.launchpad.net/bugs/213988
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Amit Kucheria (amitk)
--
control key "stuck" after resume on Dell 1420n
https://bugs.launchpad.net/bugs/213988
You received this bug notification because you are a m
> "There are also times when I get no response to keyboard or mouse input at
> all after a resume."
>
> That bug appears to be different, though, as it isn't fixed by this patch.
> (After another 4-5 resumes, I *have* hit that bug again with the patch
> applied, but still haven't seen the cont
"There are also times when I get no response to keyboard or mouse input
at all after a resume."
That bug appears to be different, though, as it isn't fixed by this
patch. (After another 4-5 resumes, I *have* hit that bug again with the
patch applied, but still haven't seen the control-key problem
patch is available in upstream (2.6.26).
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
control key "stuck" after resume on Dell 1420n
https://bugs.launchpad.net/bugs/213988
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
I've also now tested with the above attached patch applied to 2.6.24-21,
and it appears to fix the problem (I've been unable to reproduce the
problem after 8 more suspend-resume cycles).
Could someone apply this? It's a simple patch, and already in upstream
2.6.26 (so I'll mark this bug confirmed
I'd be interested to see how things work with this patch applied to
2.6.24-21, as I don't recall this problem with earlier kernels. Will
post results if I get a chance to try it.
--
control key "stuck" after resume on Dell 1420n
https://bugs.launchpad.net/bugs/213988
You received this bug notifi
I found the attached commit in upstream, applied it to 2.6.24-19.41.
Six suspend/resume cycles haven't shown the problem yet. I'll continue
testing.
(By the way, the kernel my machine was actually running most recently
was 2.6.24-21, not 2.6.24-19, but an apt-get source of linux-
image-2.6.24-21-
Similar problem...
Ubuntu Hardy, 2.6.24-21 (2.6.24.21.23)
Dell Inspiron E1505 laptop
Occasionally on resume from suspend to RAM, my keyboard gets stuck in
repeat. The repeated key doesn't seem to be related to any keys I
press; for instance, I could press '5' and get a repeating 'm'. A
second s
Starting xev and placing my mouse in it before suspend, then watching
what happens on keypresses after resume, what I see is that after some
resumes, if the first key I press is the left control key, I see that
reported as *two* KeyPress events, the first for Control_R, the second
for Control_L. T
There are also times when I get no response to keyboard or mouse input
at all after a resume. I don't know if that's the same bug or not. In
that situation, pressing the power key does still bring up the
suspend/hibernate/etc. menu (though it's no use without other keys or
the mouse working), and
16 matches
Mail list logo
