For documentation purposes, this issue is likely a duplicate of bug 1802021, fixed in kernel 4.15.0-47.50.
For documentation purposes, this issue is likely a duplicate of bug 1802021, fixed in kernel 4.15.0-47.50.