I am running version 15.10.5.

I upgraded from 15.10.1.  I was speculating as to why the fix wouldn't be in place for my 15.10.5 installation. 

I postulated that upgrading may have caused the fix to NOT be included or in effect.

Do you know the status of this problem?  Has it been verified as fixed? 

-tom