**This issue might occur in different versions too.I've only mentioned versions I've tried**

It would be helpful if you can provide us with a sample test file to reproduce this issue.

This happens to me as well immediately upon upgrade from Kubuntu 13.10 to 14.04.

Dell Latitude E6510, intel graphics. 

Broken in unstable (36) and beta (35).  Works in stable (34).

Would love a fix as Aura is beautiful!

How do I provide a sample test file?

I am having the same issue.  If you launch from a console, the error that appears during every key press is:

[5921:5921:0414/154323:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel

Ah, interesting!

Same problem in dartium 34:
https://code.google.com/p/dart/issues/detail?id=17987

Thanks for the link to this in the Dartium thread. This error has hit the regular ubuntu updates just two days before release. Right now Chromium is unusable.

System: Up to date Kubuntu 14.04 64bit

Could this be related to 349163?

Yes, it looks like the same issue to me, both lxde and kde are qt-based, I believe, which is the common denominator. It could have something to do with the qt/gtk compatibility theming.

Ah, I think i made a mistake in my earlier comment, Lubuntu with LXDE is planned to switch to QT in 14.10.

Same problem. Also i noticed after the update to Kubuntu 14.04, the look and feel of chromium changed. So could be something with GTK Theme used under KDE?

Same problem here on Kubuntu 14.04 / Version 34.0.1847.116 Ubuntu 14.04 aura (260972)

Kubuntu 14.04 - Chromium Version 34.0.1847.116 Ubuntu 14.04 aura (260972)

Here's an odd thing. The upgrade to 14.04 had messed with my keyboard language settings. I have restored them back to a UK layout, and now Chromium appears to be behaving itself.

I think indeed that fixed it for me as well (#14). 

No language changes will fix it for me,

It's broken with 
ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel

Keypushes work ONLY if you give about 200ms between keys and ONLY push one key a ta  time.

Nice bug.

You are right; after a restart it is happening again.

[4075:4075:0418/173157:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel

Seeing the same issue with a PS/2 keyboard. Kubuntu 14.04 and Chromium 34.0.1847.116 Ubuntu 14.04 aura.

Just upgraded to 14.04 from 13.10 and dead keyboard.  Read in askubuntu (from google search) kill IBus and it works.  However, this is not the proper solution if I have to do that each time my lappy starts :/

IBus -> IME label

yukishiino@, could you please look at this? Seeing a lot of reports of this now that we're in beta. (Also, is this a dupe of  issue 349163  with different repro?)

I'm having this issue too with Chromium using KDE, Gnome and Cinnamon. Usually I can type in the address bar, but then once I try to type in a textarea, it prevents me from typing anything else until I type something in another window and come back.

Killing IBus does seem to fix it. Thanks #19!

Same problem , kubuntu 14.04 chrome and Chromium

Seems that Canonical enabled Aura in Chromium 34 in their Ubuntu 14.04 package. It's too early IMO. Official Google Chrome 34 is released with Aura disabled and we are now working hard to enable Aura in Chromium/Chrome 35.

If you are suffering from this issue on *ubuntu 14.04, type "about:version" in the URL bar and check the version number. If it looks like "Version 34.* Ubuntu 14.04 aura", please try Google Chrome beta (ver. 35) or dev (ver. 36) to see if the issue still persists or not. It's great help for us.
http://www.chromium.org/getting-involved/dev-channel#TOC-Linux

I upgraded to Kubuntu 14.04 (do-release-upgrade over the existing 13.10). After this the Chromium Version 34.0.1847.116 Ubuntu 14.04 aura (260972) had the issue. Using Lenovo X61s laptop with English and Finnish keyboard mappings.

Now using Chrome Version 34.0.1847.116, which works fine. 

I was pleased to see that (after an lengthy time) my settings were restored from Google sync service to Chrome. Bookmarks, passwords, addons etc. This is how services should work. 

Seems quite similar to  Issue 349163 .  Can anyone reproduce this issue with Chrome 35 or 36?  The latest is best.

 Issue 364826  has been merged into this issue.

These are Google builds.

Works OK - Version 34.0.1847.116
Has Problem - Version 35.0.1916.47 beta aura
Has Problem - Version 36.0.1941.0 dev aura

Per other suggestions, I removed iBus and this fixed the problem in all of these versions.  The gdk_window_set_user_time error no longer appears in the console window and the function is correct.

Hello,
I have the same issue.
I notice the actions with the mouse are good, but nothing work on the keyboard (letters, numbers,) exept the arrows and the function keys (F1).
Sometimes, the letters are functionning while the mouse is not used, but i do not understand how it appears.
this is my versions : 
kubuntu 14.04
chromium : 
Chromium	34.0.1847.116 (Build de développement 260972) Ubuntu 14.04 aura
Système d'exploitation	Linux 
Blink	537.36 (@170605)
JavaScript	V8 3.24.35.22
Flash	(désactivée)
Agent utilisateur	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/34.0.1847.116 Chrome/34.0.1847.116 Safari/537.36
Ligne de commande	 /usr/lib/chromium-browser/chromium-browser --enable-pinch --flag-switches-begin --flag-switches-end
Chemin d'accès exécutable	/usr/lib/chromium-browser/chromium-browser
Chemin d'accès au profil	/home/tymop/.config/chromium/Default
Variantes	24dca50e-455c9cca
ca65a9fe-91ac3782
5e29d81-f23d1dea
246fb659-3a9ae350
f296190c-65255996
4442aae2-6e597ede
ed1d377-e1cc0f14
75f0f0a0-d7f6b13c
e2b18481-6754d7b7
e7e71889-4ad60575

 Issue 363921  has been merged into this issue.

Running Kubuntu 14.04 coming from 13.10 via dist-upgrade

not working--Version 34.0.1847.116 chromium
not working--Version 35.0.1916.47 chrome beta
not working--Version 36.0.1941.0 chrome dev 

back to firefox for now

I cannot reproduce the issue on a really fresh installation image of Ubuntu 14.04.

Most of reports seem coming from upgrades from 13.xx.  What will happen when you remove ~/.config/ibus ?  What values do you have in the following environment variables?

GTK_IM_MODULE
XMODIFIERS

What output do you get when you run `locale` command?

I've started running into this with Chrome 35 on Debian/sid (no desktop environment).
I need IBUS so I can't kill it as a workaround.

Deleting ~./config/ibus makes no difference, after ibus is restarted.

Mine was an upgrade from 13.10 to 14.04.

GTK_IM_MODULE=xim
XMODIFIERS=@im=ibus

gridley@merlin:~$ locale
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=

Mine is also upgrade from 13.10 to 14.04. I might have done an earlier upgrade from 12.10 or even 12.04 before, but don't remember it anymore.

GTK_IM_MODULE = xim
XMODIFIERS = @im=ibus

LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

After removing $HOME/.config/ibus/
$ chromium-browser 
[19724:19724:0422/214825:ERROR:content_settings_pref_provider.cc(520)] Invalid pattern strings: ,*
[19724:19724:0422/214825:ERROR:content_settings_pref_provider.cc(402)] Invalid pattern strings: ,*
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[19724:19816:0422/214829:ERROR:download.cc(109)] PostClientToServerMessage() failed during GetUpdates
[19724:19724:0422/214843:ERROR:browser_main_loop.cc(240)] Gdk: gdk_window_set_user_time called on non-toplevel

Same issue on dell latitude e5500

GTK_IM_MODULE=xim
XMODIFIERS="@im=ibus"

LANG=en_US.UTF-8
LANGUAGE=en_US
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Same as #36. I think my fresh install was on 10.10, but not sure.

I have this problem as well. I am running a upgraded version of Kubuntu 14.04. I find that switching windows will some times allow you to type in Chromium again.

uname -a
Linux ______ 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
GPU: NVIDIA GeForce GTX 480
Drive: 331.38

Chromium	34.0.1847.116 (Developer Build 260972) Ubuntu 14.04 aura
OS	Linux 
Blink	537.36 (@170605)
JavaScript	V8 3.24.35.22
Flash	(Disabled)
User Agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/34.0.1847.116 Chrome/34.0.1847.116 Safari/537.36
Command Line	 /usr/lib/chromium-browser/chromium-browser --enable-pinch --flag-switches-begin --ignore-gpu-blacklist --flag-switches-end
Executable Path	/usr/lib/chromium-browser/chromium-browser
Profile Path	/home/______/.config/chromium/Default
Variations	24dca50e-837c4893
ca65a9fe-91ac3782
5e29d81-f23d1dea
246fb659-6754d7b7
f296190c-75cb33fc
4442aae2-4ad60575
ed1d377-e1cc0f14
75f0f0a0-a5822863
e2b18481-bca011b3
e7e71889-4ad60575

Thanks for the reports.

Seeing everyone reported GTK_IM_MODULE=xim, I'm now able to reproduce the issue with GTK_IM_MODULE=xim.  The root cause seems the same as  Issue 351230  and the fix https://codereview.chromium.org/243143002/ will solve this issue.  Now working on it.

and how a normal mid-user like me should know how to use the patches there, couldn't find any intructions..... also tried Chrome 35 Beta and 36 Dev on Lubuntu 14.04 and the problem still persists.......

Kill iBus if that's an option for you.

Killing iBus might work for some, but at this moment there is plenty of new Linux users, who have been advised to switch to*ubuntu after the death of Windows XP. As new users, they don't have the skills to find this bug report page. 

They will not kill iBus, neither do I who have been working with Unix/Linux systems for couple of decades. 

Things either work or not. This release was something which was not tested well. 

It would be interesting to know how many people were affected of this bug and if it only affected the people who did an upgrade from earlier *ubuntu versions to 14.04.

Here's the thing, I'm kind of new to linux world. I had th earlier version of lubuntu, I did the upgrade, got the keyboard bug, killed the iBus, it fixed the problem, but not satifying because it has to be done after each reboot. 

Then installed again with the new version... still the same. Saw the patch thing but don't know how to use it. I tried to reinstall chromium, but not better. Hope that help. 

(eeepc 1005 ha)

Another option of a work-around: Use IBus instead of XIM.

gnome-control-center -> Language Support -> Keyboard input method system: ibus

and/or

export GTK_IM_MODULE=ibus
export XMODIFIERS=@im=ibus

in your login shell configuration.

I have the same issue either using chromium or chrome in lubuntu 14.04, 
fresh install, 10 computers have the same problem.

Anybody who is using just the standard keyboard and does not need support for alternate languages/keyboards can just remove the ibus pacakage (sudo apt-get remove ibus) and reboot. 

but I'm using Spanish input, does this affect my experience?

I'm using a french keyboard on a lubuntu 14.04 freshly installed on my eepc 1005 ha. The trick explained in post #49 work like a charm. 

I just added the following lines at the end of my .profile file:

export GTK_IM_MODULE=ibus
export XMODIFIERS=@im=ibus

Geekwork's suggestion worked here.  In Synaptic, marked ibus for removal, agreed to remove the lubuntu-desktop package (just a meta package - your desktop is not affected). Reboot and Chromium works fine again.

I have the same problem on a fresh install of Lubuntu 14.04.
Chromium version: 34.0.1847.116 Ubuntu 14.04 aura (260972)
The keyboard layout is Hungarian.

After removing lubuntu-desktop metapackage the "text keys" work but the arrows, backspace and delete don't.

Removing ibus and killing ibus-daemon fixed it for me.  Good enough for me
for now, not good enough in the general case :-).

Killing ibus helps with the issue, but then I cannot write some czech characters, ň for example. It writes ˇn instead. I haven't seen these problems since 90's on Mrkvosoft OS :D

Does anybody know when do the update will be available in the ubuntu deposite ?

@58, We do not maintain the Ubuntu chromium-browser packages. Ubuntu's M34 package had aura turned on, our's (Google's) did not.

A work around would be to actually install Google Chrome (www.google.com/chrome). Chrome's M34 was GTK+ (though our M34 will be the last GTK+ based one; our M35 will be aura based).

------------------------------------------------------------------
r266651 | piman@chromium.org | 2014-04-28T20:49:26.258241Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/base/ime/input_method_auralinux.cc?r1=266651&r2=266650&pathrev=266651
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/aura/window_targeter.cc?r1=266651&r2=266650&pathrev=266651
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/libgtk2ui/x11_input_method_context_impl_gtk2.cc?r1=266651&r2=266650&pathrev=266651
   M http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/ui/libgtk2ui/x11_input_method_context_impl_gtk2.h?r1=266651&r2=266650&pathrev=266651
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/events/event_constants.h?r1=266651&r2=266650&pathrev=266651
   M http://src.chromium.org/viewvc/chrome/trunk/src/ui/events/x/events_x.cc?r1=266651&r2=266650&pathrev=266651

linux-aura: Supports Compose key with XIM.

Supports Compose key with XIM and makes .XCompose settings effective with Linux Aura build.

BUG= 351230 , 360388 
TEST=Done manually.  Tested with GTK_IM_MODULE=xim XMODIFIERS=@im=none and ~/.XCompose with custom contents.
R=erg@chromium.org, sadrul@chromium.org

Review URL: https://codereview.chromium.org/243143002
-----------------------------------------------------------------

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/73749e6aec0682f0e5534c98691421318d7285c7

commit 73749e6aec0682f0e5534c98691421318d7285c7
Author: piman@chromium.org <piman@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date: Mon Apr 28 20:49:26 2014 +0000

linux-aura: Supports Compose key with XIM.

Supports Compose key with XIM and makes .XCompose settings effective with Linux Aura build.

BUG= 351230 , 360388 
TEST=Done manually.  Tested with GTK_IM_MODULE=xim XMODIFIERS=@im=none and ~/.XCompose with custom contents.
R=erg@chromium.org, sadrul@chromium.org

Review URL: https://codereview.chromium.org/243143002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@266651 0039d316-1c4b-4281-b951-d872f2087c98

can anyone confirm this on dev channel?

approved for  http://crbug.com/349163 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/483459e9a5e77f2564b75fff27126310c5c2e1b5

commit 483459e9a5e77f2564b75fff27126310c5c2e1b5
Author: erg@chromium.org <erg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date: Tue Apr 29 21:58:52 2014 +0000

Merge 266651 "linux-aura: Supports Compose key with XIM."

> linux-aura: Supports Compose key with XIM.
> 
> Supports Compose key with XIM and makes .XCompose settings effective with Linux Aura build.
> 
> BUG= 351230 , 360388 , 349163 
> TEST=Done manually.  Tested with GTK_IM_MODULE=xim XMODIFIERS=@im=none and ~/.XCompose with custom contents.
> R=erg@chromium.org, sadrul@chromium.org
> 
> Review URL: https://codereview.chromium.org/243143002

TBR=piman@chromium.org,yukishiino@chromium.org

Review URL: https://codereview.chromium.org/260573002

git-svn-id: svn://svn.chromium.org/chrome/branches/1916/src@266967 0039d316-1c4b-4281-b951-d872f2087c98

------------------------------------------------------------------
r266967 | erg@chromium.org | 2014-04-29T21:58:52.347861Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/chrome/browser/ui/libgtk2ui/x11_input_method_context_impl_gtk2.cc?r1=266967&r2=266966&pathrev=266967
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/chrome/browser/ui/libgtk2ui/x11_input_method_context_impl_gtk2.h?r1=266967&r2=266966&pathrev=266967
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/ui/events/event_constants.h?r1=266967&r2=266966&pathrev=266967
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/ui/events/x/events_x.cc?r1=266967&r2=266966&pathrev=266967
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/ui/base/ime/input_method_auralinux.cc?r1=266967&r2=266966&pathrev=266967
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/ui/aura/window_targeter.cc?r1=266967&r2=266966&pathrev=266967

Merge 266651 "linux-aura: Supports Compose key with XIM."

> linux-aura: Supports Compose key with XIM.
> 
> Supports Compose key with XIM and makes .XCompose settings effective with Linux Aura build.
> 
> BUG= 351230 , 360388 , 349163 
> TEST=Done manually.  Tested with GTK_IM_MODULE=xim XMODIFIERS=@im=none and ~/.XCompose with custom contents.
> R=erg@chromium.org, sadrul@chromium.org
> 
> Review URL: https://codereview.chromium.org/243143002

TBR=piman@chromium.org,yukishiino@chromium.org

Review URL: https://codereview.chromium.org/260573002
-----------------------------------------------------------------

 Issue 349163  has been merged into this issue.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/40d952e06441d909c2305745b883c68dc996d04c

commit 40d952e06441d909c2305745b883c68dc996d04c
Author: erg@chromium.org <erg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date: Tue Apr 29 22:20:21 2014 +0000

Revert 266967 "Merge 266651 "linux-aura: Supports Compose key wi..."

Compile failure:
../../ui/events/x/events_x.cc: In function ‘int {anonymous}::GetEventFlagsFromXKeyEvent(XEvent*)’:
../../ui/events/x/events_x.cc:172:51: error: ‘IsKeypadKey’ was not declared in this scope

> Merge 266651 "linux-aura: Supports Compose key with XIM."
> 
> > linux-aura: Supports Compose key with XIM.
> > 
> > Supports Compose key with XIM and makes .XCompose settings effective with Linux Aura build.
> > 
> > BUG= 351230 , 360388 , 349163 
> > TEST=Done manually.  Tested with GTK_IM_MODULE=xim XMODIFIERS=@im=none and ~/.XCompose with custom contents.
> > R=erg@chromium.org, sadrul@chromium.org
> > 
> > Review URL: https://codereview.chromium.org/243143002
> 
> TBR=piman@chromium.org,yukishiino@chromium.org
> 
> Review URL: https://codereview.chromium.org/260573002

TBR=erg@chromium.org

Review URL: https://codereview.chromium.org/253183002

git-svn-id: svn://svn.chromium.org/chrome/branches/1916/src@266978 0039d316-1c4b-4281-b951-d872f2087c98

------------------------------------------------------------------
r266978 | erg@chromium.org | 2014-04-29T22:20:21.408175Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/chrome/browser/ui/libgtk2ui/x11_input_method_context_impl_gtk2.cc?r1=266978&r2=266977&pathrev=266978
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/chrome/browser/ui/libgtk2ui/x11_input_method_context_impl_gtk2.h?r1=266978&r2=266977&pathrev=266978
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/ui/events/event_constants.h?r1=266978&r2=266977&pathrev=266978
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/ui/events/x/events_x.cc?r1=266978&r2=266977&pathrev=266978
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/ui/base/ime/input_method_auralinux.cc?r1=266978&r2=266977&pathrev=266978
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/ui/aura/window_targeter.cc?r1=266978&r2=266977&pathrev=266978

Revert 266967 "Merge 266651 "linux-aura: Supports Compose key wi..."

Compile failure:
../../ui/events/x/events_x.cc: In function ‘int {anonymous}::GetEventFlagsFromXKeyEvent(XEvent*)’:
../../ui/events/x/events_x.cc:172:51: error: ‘IsKeypadKey’ was not declared in this scope

> Merge 266651 "linux-aura: Supports Compose key with XIM."
> 
> > linux-aura: Supports Compose key with XIM.
> > 
> > Supports Compose key with XIM and makes .XCompose settings effective with Linux Aura build.
> > 
> > BUG= 351230 , 360388 , 349163 
> > TEST=Done manually.  Tested with GTK_IM_MODULE=xim XMODIFIERS=@im=none and ~/.XCompose with custom contents.
> > R=erg@chromium.org, sadrul@chromium.org
> > 
> > Review URL: https://codereview.chromium.org/243143002
> 
> TBR=piman@chromium.org,yukishiino@chromium.org
> 
> Review URL: https://codereview.chromium.org/260573002

TBR=erg@chromium.org

Review URL: https://codereview.chromium.org/253183002
-----------------------------------------------------------------

------------------------------------------------------------------
r266994 | erg@chromium.org | 2014-04-29T23:39:31.069407Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/chrome/browser/ui/libgtk2ui/x11_input_method_context_impl_gtk2.cc?r1=266994&r2=266993&pathrev=266994
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/chrome/browser/ui/libgtk2ui/x11_input_method_context_impl_gtk2.h?r1=266994&r2=266993&pathrev=266994
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/ui/events/event_constants.h?r1=266994&r2=266993&pathrev=266994
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/ui/events/x/events_x.cc?r1=266994&r2=266993&pathrev=266994
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/ui/base/ime/input_method_auralinux.cc?r1=266994&r2=266993&pathrev=266994
   M http://src.chromium.org/viewvc/chrome/branches/1916/src/ui/aura/window_targeter.cc?r1=266994&r2=266993&pathrev=266994

Merge 266651 "linux-aura: Supports Compose key with XIM."

Hopefully this will go better with the r264257 dependency merged...

> linux-aura: Supports Compose key with XIM.
> 
> Supports Compose key with XIM and makes .XCompose settings effective with Linux Aura build.
> 
> BUG= 351230 , 360388 
> TEST=Done manually.  Tested with GTK_IM_MODULE=xim XMODIFIERS=@im=none and ~/.XCompose with custom contents.
> R=erg@chromium.org, sadrul@chromium.org
> 
> Review URL: https://codereview.chromium.org/243143002

TBR=piman@chromium.org

Review URL: https://codereview.chromium.org/253233002
-----------------------------------------------------------------

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/310f2cb709c682216749e2e05935c5f29a04e870

commit 310f2cb709c682216749e2e05935c5f29a04e870
Author: erg@chromium.org <erg@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Date: Tue Apr 29 23:39:31 2014 +0000

Merge 266651 "linux-aura: Supports Compose key with XIM."

Hopefully this will go better with the r264257 dependency merged...

> linux-aura: Supports Compose key with XIM.
> 
> Supports Compose key with XIM and makes .XCompose settings effective with Linux Aura build.
> 
> BUG= 351230 , 360388 
> TEST=Done manually.  Tested with GTK_IM_MODULE=xim XMODIFIERS=@im=none and ~/.XCompose with custom contents.
> R=erg@chromium.org, sadrul@chromium.org
> 
> Review URL: https://codereview.chromium.org/243143002

TBR=piman@chromium.org

Review URL: https://codereview.chromium.org/253233002

git-svn-id: svn://svn.chromium.org/chrome/branches/1916/src@266994 0039d316-1c4b-4281-b951-d872f2087c98

this is in beta now, i'd love for people to pls try and let us know if it's fixed.

Cool.  Beta works for me now.

Working in beta for me. Thanks.

 Issue 351230  has been merged into this issue.

Assuming it's fixed.

Hello, I have the same issue with a 105 key keyboard where dedicated "í" not working only in Chromium and didn't worked with actual beta nor dev/unstable. I've tried to modify the .profile file in my ~/ but just not worked even after a restart too. I cannot remove the iBus package because I really want to use my langual settings on my keyboard.

Update: after removing the ibus package there's no effect after system restart. I've able to use öüópőúéáű but not "í" on its place, just by Altgr+J. Don't know what is this even if I'm a programmer since 1993...

Kubuntu 14.04 here, upgraded from 13.04 by apt-get dist-upgrade. Sorry for I late.

Thanks for the report.  Your issue seems identical to  Issue 363037 , and it's already been addressed.  I hope we can ship the fix to version 36, and probably 35, too.

Same problem, I'm running Lubuntu 14.04 LTS

paeschli@paeschli-desktop:~$ uname -a
Linux paeschli-desktop 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:31:42 UTC 2014 i686 i686 i686 GNU/Linux
paeschli@paeschli-desktop:~$ head -n1 /etc/issue
Ubuntu 14.04 LTS \n \l
paeschli@paeschli-desktop:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04 LTS
Release:	14.04
Codename:	trusty
paeschli@paeschli-desktop:~$ chromium-browser --version
Chromium 34.0.1847.116 Ubuntu 14.04 aura

Chromium	34.0.1847.116 (Build de développement 260972) Ubuntu 14.04 aura
Système d'exploitation	Linux 
Blink	537.36 (@170605)
JavaScript	V8 3.24.35.22
Flash	(désactivée)
Agent utilisateur	Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/34.0.1847.116 Chrome/34.0.1847.116 Safari/537.36
Ligne de commande	 /usr/lib/chromium-browser/chromium-browser --enable-pinch --flag-switches-begin --flag-switches-end
Chemin d'accès exécutable	/usr/lib/chromium-browser/chromium-browser
Chemin d'accès au profil	/home/paeschli/.config/chromium/Default
Variantes	24dca50e-c4e4c5f
ca65a9fe-91ac3782
5e29d81-f23d1dea
246fb659-6bdfffe7
f296190c-e00d173c
4442aae2-6bdfffe7
ed1d377-e1cc0f14
75f0f0a0-e1cc0f14
e2b18481-6e3b1976
e7e71889-e1cc0f14

@80:

> Chromium        34.0.1847.116 (Build de développement 260972) Ubuntu 14.04 aura

This is not a supported build. Our M-34 builds did not have aura enabled. I suspect you are using Canonical's packages. Please report bugs in Ubuntu's package to Launchpad.

(As this bug is marked Fixed, I suspect you can fix your problems by going to www.google.com/chrome and downloading the official packages.)

+1 for #48, works like a treat. When can we expect a proper bug fix?

#48 doesn't work for me, I still have non deadkey characters functional in chrome,14.04 still allows dead key input throughout the system, just chrome which rejects a different keyboard layout. 

It's too long time and I still cannot use chromium at all on notebook (Dell Latitude, updated Kubuntu 14.04), I have to use other browsers ...
Verze 34.0.1847.116 Ubuntu 14.04 aura (260972)

Ok, I see note #81 ...
Thx.

https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1307648 (and duplicates)

Same problem here when I upgraded to Ubuntu 14.04...

Computer: Dell Latitude E5500 (french belgian keyboard)
Distribution: Ubuntu 14.04
Chromium version: 34.0.1847.116

I'm using Official Chrome 35.0.1916.153-1 under Lubuntu 14.04 64 bits. The keyboard suddenly stopped working only in chrome. Other apps (like firefox, where I'm writing this) works fine. Switching input method as #41 only worked for some keystrokesd :(

I can help to debug if needed. The error seems to be hard to reproduce, because this started to happen after 1 hour using the netbook and writing on a google doc under 3g connection.

Same here after upgrade with version 34.0.1847.116 Ubuntu 14.04 aura (260972)

HW: Thinkpad T430u

This is also happening in fresh 14.04 64b's installations, in my case both Chrome and Chromium, and Ubuntu Kylin.

As #86 says, is doesn't happen inmediately. I've been using Chromium for some hours, and when stopped working I installed Chrome, which also worked for 1 day.

Lubuntu 14.04, fresh instalation,, chromium keyboard is dead.

Uninstalling ibus fixed it for me:

sudo apt-get remove ibus

Also, make sure, if you don't want to reboot for this to take effect, to shutdown ibus in the GUI. It is the keyboard thing that should sit in your tray.

I confirm that uninstalling ibus and killing the ibus processes fixed it for me too. Lubuntu 14.04 32bit & Chromium 34 Aura version

Same here, uninstalling ibus (and reboot) did the trick. Also fixed keyboard issues in other (gtk+) applications, like LibreOffice and Inkscape.

Hi there,
I am a old man just start to learn computer. Could someone kindly teach me
how to uninstalling ibus.
Thank You.

takmak...@gmail.com : in case you didn't catch it from earlier in the thread, assuming you're running ubuntu (or something in the family) open a terminal (should be somewhere in your start menu) and run the command  `sudo apt-get remove ibus`  (minus the quotes, followed by the enter key) and follow any prompts.

There are probably easier ways for your given linux distribution- some kind of software package manager or something graphical- you may need your local linux geek to have a look as systems can vary quite a bit.


To the thread in general: unfortunately ibus is required for lubuntu. Until there is a chromium-specific fix for this I know of at least a few dozen close acquaintances who have simply switched to firefox on Linux.

Also, to illuminate the bug's behavior just a bit more: chromium _does_ occasionally capture some keyboard events- maybe 5% or so. Something else seems to eat up the rest of them- and like others have reported usually it doesn't seem to happen when chromium is first launched for the first time on the system- takes some amount of activity first.

It just happened to me
Lubuntu 14.04.1 
Chrome 38.0.2125.111(64bit)
Downloaded and installed from Google.

Ubuntu 14.10
Chrome 38.0.2125.111 (64-bit)

I uninstalled ibus and seems to work for now. Fingers crossed.

Same issue for me, chrome or chromium.

Version 38.0.2125.122 (64-bit)
Ubuntu: 14.10

I can't deinstall ibus 'cause it will remove unity-control-center.

I was getting the same log message before and after uninstalling ibus but after uninstalling I seem to be able to type again. I was also getting the same problem with Chrome Beta.

[29624:29624:1124/210046:ERROR:browser_main_loop.cc(209)] Gdk: gdk_window_set_user_time called on non-toplevel

Ubuntu 14.10 x64 (fresh install)
Chrome Stable Version 39.0.2171.65 (64-bit)

SAme issue, Ubuntu 14.10, Chrome 39.0.2171.95 (64-bit)

Same error here (only on one notebook among other devices with Ubuntu 14.10)
`ibus restart` helps (at least for a while, haven't tested for longer)

After experiencing very similar problems in Inkscape (when entering text), I started using https://fcitx-im.org/ last week (instead of ibus). No issues so far.

Another solution is to simply stop using IBUS and install a different Keyboard input method such as uim or fcitx. This worked well for me on Lubuntu 14.4.1

Just install through terminal and set as default input method.

Version 39.0.2171.95 (64-bit)

Lubuntu 14.04.1 on a Thinkpad X61s

I didn't seem to have this problem when I was using regular Ubuntu 14.04.

I installed Lubuntu 3 days ago, and have had this problem twice. Browser works for quite a while, hours, but then stops working and must be restarted. 

EDIT: 'sudo ibus restart' does resolve the problem.

[1436:1436:0113/214908:ERROR:browser_main_loop.cc(209)] Gdk: gdk_window_set_user_time called on non-toplevel

Removing ~/.xinputrc solves the problem for me.

Fixed thanks to: https://code.google.com/p/chromium/issues/detail?id=367103#c101

Version 39.0.2171.99 (64-bit)
Ubuntu 14.10 on a Vostro 1310

'sudo ibus restart' solves the problem for just a few minutes of intensive keyboard use, then the problem happens again.

Disabled ibus on Language Support (Ubuntu Settings). Let's see how it goes.

I have a fresh install of ubuntu 14.10 and i also am encountering an error with keyboard input in chrome from my experience it happens only with facebook but facebook is the only page i type this much directly into i write alot into 'notepad' first and copy paste to avoid accidentally prematurely sending a post am testing other sites now   there is a 'patch like fix' i have found by disabling the repeat button press if held option in keyboard settings it restores control faster when this error happens for some reason i am no expert just a windows poweruser/sys admin wanting to migrate to linux/open source it could be something as simple as 1 less trigger/event to load idk

I'm experimenting the same issue in a fresh install ubuntu 14.10 (like the previous user) in facebook, evernote, and in any website. Actually, I can't write in the address bar.

I have the same problem. It started when I upgraded chrome browser from 36 and forward. Today I use 40.0.2214.111 (64-bit). I have no problem when using other programs. For example, I opened LibreOffice and typed for a couple of minutes. Then I openend a document in chrome (drive) and started to type. After 10 second it stopped working. I went back to see if libre was effected and could still type there. I opened google docs via firefox and it works. I tried with newest chromium (got a new update just before typing here) and I just opened a document a 2 seconds later I couldn't type. And of course I can't type in other tabs url boxes, nor any text boxes at all either in chrome or chromium.

I have to turn of the browsers and wait a few second then restart them, and I can use them as usually, as long as I don't open drive / doc and try to work.


My system:
Ubuntu 14.10 (64-bits)
cpu: Intel® Pentium(R) Dual CPU T2390 @ 1.86GHz × 2 
graphic: Intel® 965GM 

Chrome: 40.0.2214.111 (64-bit)
Chromeium: Version 40.0.2214.94 Ubuntu 14.10 (64-bit)

I rarely got this issue so i didn't pay much attention to it. Now i am trying to edit a small Document in Drive and the keyboard is blocked after several keystrokes, reproducible. I am not sure if this is related (what chrome says):

../../third_party/tcmalloc/chromium/src/free_list.h:118] Memory corruption detected. 
[17691:17691:0208/144333:ERROR:gpu_process_transport_factory.cc(514)] Lost UI shared context.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[18185:18185:0208/134333:ERROR:gles2_cmd_decoder.cc(10748)] [.Compositor-0xbd4ffc40]GL ERROR :GL_INVALID_OPERATION : glConsumeTextureCHROMIUM: invalid mailbox name
[18185:18185:0208/134333:ERROR:gles2_cmd_decoder.cc(6309)] [.Compositor-0xbd4ffc40]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering or is not 'texture complete'

This is Ubuntu 14.04 here, Chrome 40.0.2214.93

I've been experiencing the same issue with a fresh install of Ubuntu 14.10. I'm using Chrome 40.0.2214.111 (64-bit). It happens until I close all instances of chrome (even background) and open it again.

Disabling iBus made the issue to go away entirely for me.

Same for me as #115  Disabling iBus made the issue to go away entirely for me a month or two ago.

Recent Lubuntu systems:  Click LXDE bird (pseudo start menu icon) > Preferences > Language Support > Remind Me Later > Keyboard input method system: none (change from IBus to none) > Close

I had a problem with entering text on Chrome and I came to this thread... I am not entirely sure if this is the same issue I was having, but I killed the process "chrome" and it worked... Just go to the terminal, type "top", and it will give you a list of all of your processes... Find the number for your process called "chrome" (there are a lot of them if you have extensions and other things of that sort... Just find the one that has the biggest memory chunk), then type "k" and it will ask you to type the number of the process you want to kill... Type the number for chrome and press ENTER twice... In a little while, Chrome should be completely dead and you can restart it with the text working again...

i had never encountered this bug before but i am getting this regularly this last few days with this version:

Version 40.0.2214.111 Ubuntu 15.04 (64-bit)

killing chrome fixes the problem. one of the seeming triggers seems to be rapidly repeatedly hitting the backspace key, i am not sure if this has something to do with the backspace key otherwise triggering the 'back one page' event or not. i should also note that another seemingly associated bug with text input that occurs intermittently is a keypress input lag and sub-second input speed causing disordering of the order of output of keys. i type fast, 60-80wpm, and i also get this problem not just with chromium but also with the search box in the gnome 3 shell clutter overview app. it's probably unrelated but may not be, as i see mention of ibus, that this is also associated in its occurrance for me with a lockup of the network-manager service, which i have found recently on patchy wifi reception can cause the network manager to refuse to reconnect after an indeterminate number of attempts and amount of time with connection dropping and reconnecting.

Constant issues with this on 14.10 and Chrome Version 40.0.2214.93 (64-bit)

I used to have constant issues with this (see my messages above). I had to
re-install my OS and Chromium because of other reasons.  I am on default
settings (IBus enabled). I don't have any problems for some reason.

I hadn't installed Ubuntu 14.10.1. I installed Ubuntu 14.10 because I was
lazy and I had it on a flash. I am not getting any freezes even with the
iBus on.

Same as #122 for me, too.

I know technically this is a Chromium board, but in theory it applies here too.
I have the same issue on Lubuntu 14.10 using Google Chrome Stable and Vivaldi Preview, this issue doesn't arise using Firefox, however I generally prefer to use Chromium or WebKit based browsers.

I noted it happened to me when I edited an element style from the dev tools. I was editting some keys for a selector from a highlighted element, then I tried to add a new one, in my case it was font-size, then the next one I tried to add triggered the bug. From this moment, no keyboard inputs were listened to by any "current" chrome process. Another interesting thing is that if I open a new chrome window from my desktop (without closing the previous), it will work well, but then if I close the bugged chromium windows and keep the new one open, if I use ctrl+shift+t once to reopen the window with all its tabs it will be bugged just as before, it seems to corrupt the session until ALL of the chromium processes are killed and restarted.

Upgrade to 14.10 Ubuntu, and latest Google Chrome stable, unresponsive keyboard. Try this easy fix. I downloaded Google Chrome beta, keyboard functional. The end. 

Note: also, latest Google Chrome beta. 

Happening here on a coworker's machine. 5th-gen i3, 8GB RAM, Ubuntu 14.10 64-bit. 

After using Chrome for a few minutes, all keyboard input stops working in Chrome, including in web pages and in the omnibar. Completely exiting Chrome then restarting alleviates the issue temporarily, but it happens soon after. She noticed it happening more often when using Google Docs.

Switching Ubuntu's system-wide input method from "IBus" to "none" it seems to have gone away, a workaround I found here: http://askubuntu.com/questions/457541/unable-to-type-anything-on-chromium

Not sure that's an acceptable long-term solution, but it seems to work for now.

The "break the iBus" chang seems to work for me as well. So, who threw Chromium under the iBus? (Sorry, couldn't resist!) 

I have this problem in Windows 10 tech preview

I also installed Google Chrome Beta. It works!

I'm running chromium 41.0.2272.76 on lubuntu 14.04. The bug is still around. Killing Ibus solves it, but that is an awkward solution.

Same issue here, on 14.04 / Chrome Version 42.0.2311.135 (64-bit). Typing is impossible at times. Restarting Chrome will fix the issue, but hardly an ideal solution, just like disabling IBus.

I have this problem on Windows 7 64bit.
Chrome: 42.0.2311.152
When I enable...
Pepper Flash: 17.0.0.188: Text is NOT visible in inputfield.
Adobe Flash: 17,0,0,188 : Text IS visible in inputfield.
I cannot fix this issue, restarting does not help.
Since this windows version and the latest players are pretty common, this could be a huge problem. :(

export GTK_IM_MODULE=ibus
export XMODIFIERS=@im=ibus
chromium-browser

Wow.  Has been reported for over a year and no fix?!  The same is happening to me.  Although I get the input back after typing a few characters on the Windows 10 touchscreen keyboard then going back to chrome.  Quickest way I could find.

Is this going to get fixed?  Or am I going to uninstall the browser?

This occurs for me on Ubuntu LTS under XFCE for months.  For me, it is always triggered by the screensaver/screenlock.  When I unlock the system, I cannot enter text.  

The workaround that consistently works for me is to simply minimize a Chrome window, and then restore it.  I am then able to use the keyboard.

#137:

> Wow.  Has been reported for over a year and no fix?!

The bug has already been fixed. If you are experiencing a similar issue, a year after a bug that was already marked fixed, on a different operating system (note the bug is marked OS-Linux and you are talking about Windows 10) that didn't even exist when this bug was fixed, then there's an exceedingly good chance you're experiencing an *entirely different bug*.

We don't re-open old bugs when people experience similar symptoms. Please file a new bug report and provide details about your specific case.

#138: It sounds like there's a problem with XFCE not sending keyboard input to Chrome. It doesn't sound like something we could address on our side.

#140: mgiuca, that seems reasonable.  Interestingly, Chrome is the only application for which this occurs.  All others applications happily accept input.  Only Chrome requires the minimize-unminimize sequence.  I will try to narrow it down further, and will open a new bug if the Chromium team would need to look at it further.

#141: There was(or is?) a problem that Chrome doesn't receive a key-up event when you lock the screen with explicitly hitting Ctrl+Alt+L or something like that because hitting the key combination makes the screen saver active, i.e. it makes Chrome inactive, so there is no chance for Chrome to receive the key-up event for the key combination.  IIRC, we had(or have) this problem on Mac.  I don't know if this is the case on Linux, too.

Anyway, I'd recommend to file a new issue separately.

+cc: shuchen@ who is the current owner of text input.

Someone said the problem has been fixed? No. I am using Windows 7 (latest) and Chrome (latest) and experience regular keyboard lock-ups perhaps once a day. 

#143, please see comment #139 above. It seems you are experiencing a different bug on a different OS (this one was Linux specific and was fixed). If you are still experiencing similar symptoms please file a separate bug and provide details about your case.

hi

im on lubuntu 
Linux 3.19.0-33-generic #38~14.04.1-Ubuntu SMP Fri Nov 6 18:17:28 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 
i didnt make any distro upgrade.. it first was clean 14.04.0

running chromium-browser, just installed from repo CLI install
Version 34.0.1847.116 Ubuntu 14.04 aura (260972)

in my case chromium stops taking keystrokes ~ 5-6 seconds after i open it; sometimes comes back.. bug present inside incognito also
from the upper posts.. its not clear to me in which version and distro it was fixed; at the moment i use minimize/restore window workaround

i would like to reopen this bug

Version 34.0.1847.116 is too old.  Current stable version is 51.
I'd recommend to try the latest version.

If you see any issue with the latest version, please open a new bug.  This bug is also too old.

seems i was on lubuntu 14.04.3 with updates(security and updates lists) disabled due to constant nagging of firefox updates.. chromium 34.0.1847.116 being the only available option inside repo..

i enabled them and now happily running 14.04.4 3.19.0-64-generic #72~14.04.1-Ubuntu SMP Fri Jun 24 17:59:48 UTC 2016 x86_64 x86_64 x86_64 and chromium 51.0.2704.79 Ubuntu 14.04 (64-bit)

might be an old bug.. but i just stumble upon it..
ty for your time