I have a similar problem on a 4.15.0-20-generic kernel. Is there a new bug for this since this one has been marked invalid?
I have a similar problem on a 4.15.0-20-generic kernel.
Is there a new bug for this since this one has been marked invalid?