GNOME Bugzilla – Bug 679220
Keyboard stuck
Last modified: 2012-09-11 14:42:23 UTC
This bug occurs when using kwin as window manager (kubuntu flavor) and is easily reproducible on either upgrades and new installs of Kubuntu Precise. I haven't tried if it also occurs with Unity or Gnome. There are other ways to trigger the bug but the easiest way is the following. 1) In Evolution you need at least 2 e-mail accounts (mine are both of the imapx type) 2) Create an empty new e-mail 3) Type some text in the body 4) In the From: field select another account 5) Try to continue typing in the body At this point the keyboard doesn't respond. You can copy/paste text using the mouse. 6) To work around: right-click in the body, select input method , switch to None or Simple 7) You can now type again. Annoying bug and new to Precise / Evolution 3.2.3 Ferry ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sat Jun 23 21:29:03 2012 InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= TERM=xterm LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to precise on 2012-05-10 (43 days ago)
Thanks for a bug report. That combo is a standard gtk3 GtkComboBox, and this doesn't occur in Gnome, thus I believe this is KDE issue. As a prove, install gtk3-devel and run gtk3-demo. When you run its Combo boxes demo, and just change item from one to another, then you get the same issue. Please report this to KDE, if they do not have it filled yet.
In Ubuntu I found the gtk3-demo in package gtk-3-examples. In the comboboxes example I find: - I can't type in the Editable box at all - In the String IDs box behavior is exactly as I Evolution: get's stuck when switching one of the Stock icons/ Where are we? box, after switching input method it works again. I use oxygen-gtk and found that switching to QtCurve the problem goes away. SO I think the problem is probably in oxygen-gtk. Thanks, Ferry
Thanks for the testing. I agree with the possibility of this being caused by oxygen-gtk. Do you know upstream for oxygen-gtk? It will be helpful to let them know for sure.
Yes, reported as https://bugs.kde.org/show_bug.cgi?id=303762 And already found to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=299121 Ferry
Ah, and the workaround in #299121 (edit in the gtk css file) does solve the issue.
*** Bug 677970 has been marked as a duplicate of this bug. ***
*** Bug 683491 has been marked as a duplicate of this bug. ***