I am having the same issue. This looks like a duplicate of #814982 which already references a patch that seems to solve the issue.