Just confirmed that the fix did not, in fact, make it into 5.3.2 release. For anybody experiencing this issue, you have to either compile from source with the fix applied as mentioned above, or wait for 5.4 release.
Just confirmed that the fix did not, in fact, make it into 5.3.2 release. For anybody experiencing this issue, you have to either compile from source with the fix applied as mentioned above, or wait for 5.4 release.