@flipvb
The main issue is not that this bug exists and that it is not the fault of Canonical. The issue is that the 16.04 stable HWE LTS stack rolled to 4.10 despite this bug being known and being critical, with 16.04.3 not even released yet.
@flipvb
The main issue is not that this bug exists and that it is not the fault of Canonical. The issue is that the 16.04 stable HWE LTS stack rolled to 4.10 despite this bug being known and being critical, with 16.04.3 not even released yet.