What is the status for this bug for upcoming Xenial? Is it resolved or is the workaround still necessary?
What is the status for this bug for upcoming Xenial? Is it resolved or is the workaround still necessary?