Comment 5 for bug 2067307

I'm a bit of a novice, and it would have taken a bit more advanced terminal skills than I have, but I did find out it was using the older of two (0,31 vs 0,35) lowlatency kernels. I did a reboot, and in advanced settings switched to the newest kernel, and that seems to have fixed the issue. Thank you for the suggestion.