walterramjet, the 5 bug was indeed still present in your kernel
version (4.2.0-36.*). For the 4.2.0 kernel series, it was fixed in
version 4.2.0-42.49 as noted in comment #59 here, so running a regular
system software update is probably what you need to do.
However, its confusing that you
Earlier posts say this bug was fixed in linux 4.4.0-30.49. My system
has been fine since then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5 automatically pressed on some
i forgot to add, i am running linux-image-4.2.0-36-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5 automatically pressed on some Logitech wireless keyboards
To manage
I have been having the same problem ever since I got my K800 wireless keyboard.
example: 5. etc
I am using Ubuntu 16.10
please help. I dont know what to do
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Viktor.
Following my post #65...
I've been running kernel 4.4.0-47-generic for a week now and the problem has
not come up once.
So for my part, the kernel update has fixed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Greetings Geoffrey,
I'm running the latest Mint (18) and I did not see issues with my K520 keyboard
so far.
I'm using the kernel that comes (I guess 4.4) with the release.
So I guess updating the kernel to the latest should definitely help.
The patch was released with 4.4.0-31.50 as I see.
--
I'm experiencing this on a K350 keyboard, on 4.4.0-21-generic kernel
(fresh install of Linux Mint 18 Sarah / Ubuntu 16.04 LTS).
I usually see the problem after changing windows by clicking on one in
the panel. As the new window takes focus, the ...555's start
flying.
Another curious
I'm also experiencing this bug on a K350 keyboard on Ubuntu 16.10. It's
been a problem on and off for a few years with this same keyboard
though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
This bug was fixed in the package linux - 3.2.0-106.147
---
linux (3.2.0-106.147) precise; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1597109
[ Upstream Kernel Changes ]
* HID: core: prevent out-of-bound readings
- LP: #1579190
-- Kamal Mostafa
This bug was fixed in the package linux - 3.2.0-106.147
---
linux (3.2.0-106.147) precise; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1597109
[ Upstream Kernel Changes ]
* HID: core: prevent out-of-bound readings
- LP: #1579190
-- Kamal Mostafa
This bug was fixed in the package linux - 3.13.0-92.139
---
linux (3.13.0-92.139) trusty; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1597060
[ Josh Boyer ]
* SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
This bug was fixed in the package linux - 3.19.0-65.73
---
linux (3.19.0-65.73) vivid; urgency=low
[ Ben Romer ]
* Release Tracking Bug
- LP: #1596631
[ Josh Boyer ]
* SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP:
This bug was fixed in the package linux - 4.2.0-42.49
---
linux (4.2.0-42.49) wily; urgency=low
[ Ben Romer ]
* Release Tracking Bug
- LP: #1597053
[ Josh Boyer ]
* SAUCE: UEFI: acpi: Ignore acpi_rsdp kernel parameter when module
loading is restricted
- LP:
This bug was fixed in the package linux - 4.4.0-31.50
---
linux (4.4.0-31.50) xenial; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1602449
* nouveau: boot hangs at blank screen with unsupported graphics cards
(LP: #1602340)
- SAUCE: drm: check for
This fix will appear in the next normal automatic kernel update for
15.10 (which currently scheduled for July 18 -- my previous estimate was
off by one week).
However, that kernel is available in the "-proposed" archive right now,
so if you don't want to wait for the normal update you can install
I have this issue with an MK710 on Ubuntu 15.10
Glad there is a fix. Sorry I am not clear. Will this be in an automatic
update for 15.10 or should I manually update the kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, I forgot that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5 automatically pressed on some Logitech wireless keyboards
To manage notifications about this bug go to:
The fix was already present in the Yakkety kernel (since the fix in
mainline Linux v4.6, upon which Yakkety is currently based).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5
I notice that there's no mention of a yakety release. Is that
deliberate?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5 automatically pressed on some Logitech wireless
Excellent!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5 automatically pressed on some Logitech wireless keyboards
To manage notifications about this bug go to:
Tim: Correct, there is no need to also test 4.4.0-30.
Given that we've had no further reports of this problem, we'll now
consider it to be verified as fixed in the -proposed kernels. Those
kernels are scheduled to be released via standard -updates within the
next week.
** Tags removed:
I assume I don't have to test 4.4.0-30 as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5 automatically pressed on some Logitech wireless keyboards
To manage notifications
This bug was fixed in the package linux - 4.4.0-30.49
---
linux (4.4.0-30.49) xenial; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1597897
* FCP devices are not detected correctly nor deterministically (LP: #1567602)
- scsi_dh_alua: Disable ALUA
I have had no further problems when using the proposed kernel, so it
works for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5 automatically pressed on some Logitech wireless
Kamal - thanks for the clarification.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5 automatically pressed on some Logitech wireless keyboards
To manage notifications about
Thanks for posting the handy instructions, Tim.
It isn't really necessary for all previously affected users to post
"positive" results (since they will necessarily be inconclusive anyway).
As long as we get at least a couple of folks (including myself) to
report no further instance of the problem
On xenial I found it easiest to:
- add the proposed repository via 'Software and Updates', in the
'Developer Options' tab, tick the 'pre-released updates' box
- using synaptic, reload the repos, mark all upgrades, and then tick
only the 4 'linux-..' kernel items to get version 4.4.0.29.
- I
Affected users: As noted above, the kernel versions available in the
-proposed include this fix now. Since the problem can't be positively
verified, we'll consider the problem "verified" as long as we do not get
any reports to the contrary in the next few days.
So, if you install the -proposed
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.
If verification is not done by 5 working days
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from
The "out of the normal cycle" kernel versions released yesterday were
for a security fix, and so do _not_ include the fix for this bug.
The "normal cycle" kernel versions that we're preparing this week _do_
include this fix. A note will be posted here as soon as those kernels
reach the -proposed
I just looked at the change log at the today's kernel (4.4.0-28) and the
fix for this bug is not listed in the change log.
When, oh my, just when is it going to be released? Please! This is very
annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
A new Xenial kernel was released today (28/6/16) - 4.4.0-28. Is the fix
in that version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5 automatically pressed on some Logitech
I'm having the same issue. I'm on Xubuntu 16.04 and using logitech k800.
The only way to stop the issue is by logging out of the desktop. I'll be
trying the patched kernel today. I hope it works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Darren, the fix is scheduled to be released in all affected Ubuntu
versions in the near future and a note will be posted here at that time.
In the meantime, the Xenial (amd64) test kernel indicated in Comment #16
should offer you some relief.
--
You received this bug notification because you are
Thanks for the fix, where can I apply it now? Ubuntu Xenial. In 2
hours this bug has happened no less than 20 times. Everything is
currently updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Kamal, Thanks very much for taking the time to explain this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5 automatically pressed on some Logitech wireless keyboards
To manage
Tim, its essentially the same reason that we saw the problem manifest in
some Wily and Xenial kernel versions, then seem to disappear in the next
kernel version, only to return again in some future version:
The bug, which definitely existed all the way back through Precise, was
that the driver
Is there an obvious reason why users of trusty never had this problem
before, even though the fix seems to apply to many versions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Wily)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Vivid)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Trusty)
Status:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Precise)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Vivid)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Wily)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Wily)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug notification because
Summary of test kernel results: All users of the test kernel have
reported that it does appear to eliminate the 5 problem.
I will get the fix patch ([mainline] 50220de HID: core: prevent out-of-
bound readings) into the pipeline for all affected Ubuntu kernels, and a
note will be posted
As I said, "I was using the patched kernel, with no problems". I was
away for a few days so have probably only run 4.4.0-22-generic
#40+lp1579190 for 4 or 5 days in all, so far without seeing the problem,
but it is transient.
4.4.0-24 didn't display the fault for a couple of days, and then did
Hi Tim Passingham (tim-8aw3u04umo),
the new kernel you installed (4.4.0-24) will definitely produce the issue as it
does not contain the patch.
Please clarify if you where also able to reproduce the issue with
4.4.0-22-generic #40+lp1579190.
--
You received this bug notification because you
Sorry, I should have explained better. I was using the patched kernel,
with no problems. When the 24 update came up for installation a few
days ago I thought I would try it, so I did. Today that newer version
still showed the same problem, so I have reverted to the patched version
(by using
Hi Tim Passingham (tim-8aw3u04umo),
you are not using the patched kernel.
The patched is: 4.4.0-22-generic #40+lp1579190
And you are using: 4.4.0-24
What might have happened is that you installed the patched kernel and then you
updated Ubuntu and 4.4.0-24 was installed and set as the default
4.4.0-24-generic #43-Ubuntu SMP just failed for me as well.
I had installed it a few days ago and it was OK, but just went wild
again with repeating 5's. It may be a coincidence, but I
also was using Thunderbird at the time.
I shall revert to the patched version.
--
You received
4.4.0-24-generic #43-Ubuntu SMP just failed. I went to reply to a
thunderbird email. 5's went wild. #40+lp157919 is still
okay.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
I am still testing #40+lp1579190 and have not experienced 555's
yet but on an install of the new linux mint 18 Beta I have upped from
the default 4.4.0-21-generic to 4.4.0-24-generic #43-Ubuntu SMP and have
had no incidents of 555's in the 2 days I have had it installed.
Will continue
U1604-MATE:~$ uname -a
Linux U1604-MATE 4.4.0-22-generic #40+lp1579190 SMP Fri Jun 3 15:50:59 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
I have been running the patched kernel for a couple of days now. The
555's have totally ceased. I was experiencing the 5's frequently
daily prior to the
I have just installed the patched version. I had to remove both 4.6 and
also the 4.4.0 signed image (which was broken by the install of the
patched version).
I'll report either way in a week or 2 (or sooner if the bug appears
again).
--
You received this bug notification because you are a
I've built a test kernel for Ubuntu Xenial 16.04 (amd64) which comprised of
4.4.0-22.40 plus:
[mainline] 50220de HID: core: prevent out-of-bound readings
The test kernel is here (most users will only need to 'dpkg -i' install
the linux-image-4.4.0...deb):
Doug, you added the tag 'kernel-fixed-upstream' but I don't think we
have hard evidence of that at this point. Was your tagging based only
on Viktor's reports that it hasn't happened (yet) on a 4.6 kernel, or is
there more information elsewhere?
Viktor, your result with 4.6 is promising!
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5 automatically pressed
Still not able to reproduce this with 4.6 kernel series.
It is very likely that this issue is already fixed there.
Any chance this could be backported to the xenial kernel as this is an LTS
release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Ubuntu 15.10 and 16.04, Keyboard K520.
I buy new keyboard and receiver and it's don't fix my problem.
I never seen this bug on Windows and Ubuntu 15.04 on same host.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have been having the same problem ever since I got my K800 wireless
keyboard. Ubuntu 15.10 - it happens also when the keyboard is turned
off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
I also get this behaviour with my Logitech K520 keyboard and unifying
receiver, on Ubuntu 16.04 and on 15.10 before that.
I'm currently running
4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64
x86_64 GNU/Linux
The same bug has been reported on the RedHat bug tracker:
I'm running the latest and greatest Kubuntu though:
4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64
x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
I'm using a Logitech K20 wireless keyboard and it randomly repeats
5.
After an event the fist key pressed (no matter which key) is not recognized.
It is pretty annoying especially when writing a text or while programming.
Does not happen under Windows (same computer).
--
You
I'm using 4.6.0 rc6 since about a week and haven't experienced this issue since
then.
I would treat this as an evidence though. Will be continuing testing with the
4.6 kernel series.
Installed the kernel from here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/
--
You received
I am experiencing this on a Logitech K350
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5 automatically pressed on some Logitech wireless keyboards
To manage notifications about
freeze/hang forever, the pc gets stuck and it does not recover, i have
to hard reboot it. I could not see the freeze synced with the 5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Yes I WladyX I get freezes, but IIRC this is always how it was on Linux since I
use it. :)
Are the freezes happening to you at the same same time the 5 key is repeated?
Joseph Salisbury, yes I can try the latest upstream kernel.
Will let you know the results.
--
You received this bug
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.6 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
I also get freezes/hangs, may be unrelated, do you get them too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579190
Title:
Key 5 automatically pressed on some Logitech wireless keyboards
To
73 matches
Mail list logo
