This was fixed in 2014. Given Xenial pulls a 2015+ version from upstream, this should be fixed, so marking it as such.
This was fixed in 2014. Given Xenial pulls a 2015+ version from upstream, this should be fixed, so marking it as such.