No, it doesn't. The kernel was updated to 4.13.0-32-generic, and this still has the bug, I believe the 4.13.0-21 might have it also.
No, it doesn't.
The kernel was updated to 4.13.0-32-generic, and this still has the bug, I believe the 4.13.0-21 might have it also.