Just ran into this exact problem today in 16.10, so problem still exists. Thanks, Reuben, your workaround in comment #3 got me back up and running again.
Just ran into this exact problem today in 16.10, so problem still exists. Thanks, Reuben, your workaround in comment #3 got me back up and running again.