Comment 7 for bug 292912

Revision history for this message
Collin Stocks (collinstocks) wrote :

I called dmesg once, then closed and opened the screen to cause the problem, then called dmesg again. There were no new messages the second time I called it, so whatever is causing the problem did not cause a driver to output an error message.