GNOME Bugzilla – Bug 683491
Keyboard inactive after adding signature in email
Last modified: 2012-09-11 14:42:23 UTC
When I select a signature in the list of signatures I have created, for it to appear at the end of the email message I write, then the keyboard becomes unresponsive: I cannot type anything in the message, I cannot use keyboard shortcuts in the New message window, etc. Keyboard becomes also unresponsive in some other windows/ dialog of evolution (this part is harded to predict), but the most consistant (and annoying) bug is on the New message window. Some weird workarounds make the keyboard work back again, for instance any one of the following: - copy/paste some text in the message (with the mouse only) - add PGP or mime signature or encryption - click any item in the list of encoding (uncluding the currently active one) - Click on the "File" menu (menu of the New message window or of the main Evolution window: both work). [that's the fastest, but last one I found) However, when keyboard is back, selecting another signature makes the bug return. I run Ubuntu 11.04 with both Gnome and KDE (I normally use KDE). Mayeul Kauffmann
Sorry, I run Ubuntu 12.04 (not 11.04).
Thanks for a bug report. Could you run gtk3-demo, and test there with standard combo boxes, please? It seem to me that you are facing bug #679220.
Hi Milan, Thanks a lot for the link to bug #679220! Bug #679220 described the same problem but triggered from a different action, namely: "4) In the From: field select another account" (so I did not find that bug while searching before reporting). However, the test you suggest gives the following errors, along with a behaviour similar as in the other bug: ~$ gtk3-demo Gtk-Message: Failed to load module "canberra-gtk-module" (gtk3-demo:8222): Gtk-CRITICAL **: gtk_device_grab_remove: assertion `GDK_IS_DEVICE (device)' failed (gtk3-demo:8222): Gtk-CRITICAL **: gtk_device_grab_remove: assertion `GDK_IS_DEVICE (device)' failed Also, what Ferry says in the other bug works here too: "I use oxygen-gtk and found that switching to QtCurve the problem goes away." Well, you find "QTCurve" in a bunch of places in KDE's System settings, so what worked is: System settings > Application appearance > GTK+ Appearance > Widget style: QTCurve Then: Apply Thanks again! (had been a nightmare for several weeks!) Cheers, Mayeul *** This bug has been marked as a duplicate of bug 679220 ***