This is a known bug in earlier versions of enblend, though I thought it was fixed for the final 3.2 release.
Upgrading to enblend-4.0 should fix it.
This is a known bug in earlier versions of enblend, though I thought it was fixed for the final 3.2 release.
Upgrading to enblend-4.0 should fix it.