(In reply to comment #12) > I got this too, but this was already there before I updated to the 3.8.0 > kernel. So I think it has nothing to do with this problem. Thanks for letting me know. I may know an already opened bug about it...