Haven’t seen this once since upgrading to 16.04 back in April, so I’m pretty sure the issue has been fixed. Yay!