I verified that there are no reports for this issue on https://errors.ubuntu.com/problem/c7ba5238c01adbb8a245dfc02bac9633a362ea44 for 17.04 after the 3.22.7-0ubuntu3.17.04.2 update. On 17.10, we haven't gotten any new reports of this bug since early May.
This issue is also a bit odd because it's already been fixed now in 16.04 LTS and 16.10 so let's not delay this fix further in 17.04.
I verified that there are no reports for this issue on https:/ /errors. ubuntu. com/problem/ c7ba5238c01adbb 8a245dfc02bac96 33a362ea44 for 17.04 after the 3.22.7- 0ubuntu3. 17.04.2 update. On 17.10, we haven't gotten any new reports of this bug since early May.
This issue is also a bit odd because it's already been fixed now in 16.04 LTS and 16.10 so let's not delay this fix further in 17.04.