Log in sceen does not respond to keyboard password input

[nvsoar]

Trusty Tahr daily, 32 bit; three separate machines of diffent make and vintage; same behavior. Mouse input inactive except in top panel - able to pull up onscreen keyboard and log in; after which operations appear normal.

w8@w8-ion:~$ lsb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
w8@w8-ion:~$

Package is that which contains log in screen

nvsoar

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity-greeter 14.04.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic i686
ApportVersion: 2.13.1-0ubuntu2
Architecture: i386
Date: Sat Jan 25 06:20:31 2014
ExecutablePath: /usr/sbin/unity-greeter
InstallationDate: Installed on 2014-01-22 (3 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140121)
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/false
Signal: 5
SourcePackage: unity-greeter
StacktraceTop:
 atspi_dbus_connection_setup_with_g_main () from /usr/lib/i386-linux-gnu/libatspi.so.0
 atspi_set_main_context () from /usr/lib/i386-linux-gnu/libatspi.so.0
 ?? () from /usr/lib/i386-linux-gnu/libatk-bridge-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libatk-bridge-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
Title: unity-greeter crashed with signal 5 in atspi_dbus_connection_setup_with_g_main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1237569, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[nvsoar (nvsoar)]

Added - Rebooted following initial report - no response to keyboard or onscreen keyboard. Hardware keyboard then responded following deactivation and reactivation of onscreen keyboard entry on one character.

Unable to comment on duplicate status - this report submitted since keyboard input was unresponsive. If this is a "crash" then the submission could well be a duplicate.

nvsoar