Did this issue not happen in prior releases? Do you happen to know if there was an earlier Raring kernel that did not exhibit this bug?
Did this issue not happen in prior releases? Do you happen to know if there was an earlier Raring kernel that did not exhibit this bug?