Also the link in comment #30 is NOT related to this bug. It's the wrong hardware generation. You need to open a new bug.
Also the link in comment #30 is NOT related to this bug. It's the wrong hardware generation. You need to open a new bug.