After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 712718 - Keyboard input doesn't work in any text field since upgrading to Mac OS X 10.9
Keyboard input doesn't work in any text field since upgrading to Mac OS X 10.9
Status: RESOLVED DUPLICATE of bug 710943
Product: GIMP
Classification: Other
Component: User Interface
unspecified
Other Mac OS
: Normal critical
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-11-20 00:09 UTC by Carl
Modified: 2013-11-20 09:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Carl 2013-11-20 00:09:14 UTC 
Overview:
Keyboard input doesn't work at all when trying to type text into a text field, nothing is printed, but instead keyboard shortcuts perform in background windows rather than the focused window.

Steps to Reproduce:
Open a graphics file, go to Image > Canvas Size...
In either the Height or Width fields, select and type "1".
(there are many other examples)

Actual Results:
The "1" digit doesn't print, but instead the image in the other window zooms to 100%.  Any other digit acts similarly.  Also occurs in the Save Image... dialog window.  I can't rename a file because typing a key on the keyboard will not print inside the text field.

Expected Results:
Text should appear in the in-focused text field, and shouldn't act as keyboard shortcuts in unfocused windows.

Build Date & Platform:
GIMP 2.8.4 on Mac OS 10.9
Macbook Air 2012 model, upgraded to Mavericks, with US keyboard.

Additional Builds and Platforms:
GIMP 2.8.2 on Mac OS 10.9
Comment 1 Michael Schumacher 2013-11-20 09:39:39 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 710943 ***