It seems this also affects Xenial (16.04 LTS); see also the duplicate bug #1748889. Is there a chance to get this bug also nominated for and fixed in Xenial? Or should a separate bug report deal with Xenial?
It seems this also affects Xenial (16.04 LTS); see also the duplicate bug #1748889. Is there a chance to get this bug also nominated for and fixed in Xenial? Or should a separate bug report deal with Xenial?