Enter key not working on gmail search bar when using a non-US keyboard layout (chrome)

Bug #1814784 reported by borninbronx
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Some week ago I started to have issue with Gmail, in Chrome.

When I write something in the search bar it autocomplete, but then I hit "ENTER" and nothing happens.

I know, this doesn't sound like an Ubuntu issue, but I don't give up on me, I'll show you why I think it is.

I thought this was an issue with Gmail website, but after a couple of weeks without any change I decided to investigate.

If I change the layout of my keyboard from "US, with italian letters" to "US" the Enter key works without any problem.

When I change it back to "US, with italian letters" it stop working again.

ENTER key works everywhere else, even inside Gmail website, which makes the issue even weirder.

I'm not alone in this as you can read here:
https://askubuntu.com/questions/1112847/enter-button-does-not-send-message-in-whatsapp-gmail-web-clients-on-18-04-1-lts

and here (on Firefox apparently):
https://bugzilla.mozilla.org/show_bug.cgi?id=1423693

Apparently many people experiencing this with whatsapp webchat too, I don't use it so I don't know.

I've tried with Firefox too: the Gmail search apparently works, but when you login pressing enter after writing the password has no effect, you need to click the button (or change keyboard layout)

I've no idea what is causing this, it's probably a mixture of website issue and Linux / Gnome / Ubuntu issue: but I know none of my coworker with Mac and Windows are experiencing any issue on any browser, so I think the problem is mainly an issue with Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
Uname: Linux 4.15.0-44-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 5 15:50:08 2019
InstallationDate: Installed on 2018-10-20 (107 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
borninbronx (daniele-segato) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, but it's not a bug in the settings UI component (gnome-control-center), if other softwares work fine then it's probably a but in chrome and firefox (or a component they use which GNOME doesn't use or not the same way), reassigning to firefox since chrome isn't free software nor on launchpad

affects: gnome-control-center (Ubuntu) → firefox (Ubuntu)
Revision history for this message
borninbronx (daniele-segato) wrote :

Hi Sebastien,

I know it isn't gnome-control-center but I tried to follow Reporting Bugs guide on the "Filing a general bug against no particular package", which got me no-where: when I run the only option that makes sense is "Other problem" and it just give you an alert that you need to specify the pid of something.
So I provided a package name to be able to file the bug.

I picked Control Center cause it's the place where you set up your keyboard layouts.

I don't think Firefox has anything to do with the issue here.

It is more likely an issue with the keyboard input method system (through iBus) implementation.

Hope you can reproduce the issue.

Revision history for this message
borninbronx (daniele-segato) wrote :

Hi, I just wanna say this issue stopped happening shortly after i filed the bug.

I still think it was a mixture of linux key press handling and website code. And since I'm not sure which side fixed it I can't be sure this won't still happen on some other website.

Revision history for this message
Olivier Tilloy (osomon) wrote :

Thanks for following up Daniele. Closing the bug now, feel free to re-open if the issue happens again.

Changed in firefox (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.