Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#55137 - [chromium] Shift key is not released on Chromium JS

Attached to Project: Arch Linux
Opened by Peter (protake) - Monday, 14 August 2017, 08:53 GMT
Last edited by Evangelos Foutras (foutrelis) - Thursday, 24 August 2017, 15:40 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

So, I reported this upstream, but apparently it isn't a Chromium bug:
https://bugs.chromium.org/p/chromium/issues/detail?id=754166

I have no idea which update this could be related to.
For the record, I'm using GNOME as DE. The bug occurs with all extensions disabled.
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Thursday, 24 August 2017, 15:40 GMT
Reason for closing:  Fixed
Additional comments about closing:  gtk3 3.22.19-1
Comment by Peter (protake) - Thursday, 24 August 2017, 08:51 GMT
This bug still exists and simply breaks some webapps completely. It also affects other keys besides shift. They keyup event is simply not executed properly. I'd be nice if anyone could at least confirm this bug.
Comment by Evangelos Foutras (foutrelis) - Thursday, 24 August 2017, 15:09 GMT
Can confirm on Xfce (without a compositor, if that matters); there are no keyup events for either Ctrl or Shift, using the following code:

var log_event = function(event) {
console.log(event)
}
document.addEventListener('keydown', log_event)
document.addEventListener('keyup', log_event)

It is also reproducible with Chrome (instead of Chromium) but only on Arch. For some reason, it works fine on Ubuntu (16.04.3 and 17.04).
Comment by Evangelos Foutras (foutrelis) - Thursday, 24 August 2017, 15:39 GMT
Turns out this was a bug in GTK+ 3.22.18; upgrading to 3.22.19 which just hit [extra] fixes it.

Upstream bug was: https://bugzilla.gnome.org/786519

Loading...