Alright, well so far it isn't sounding like an X bug. Perhaps an error in plymouth, or even could be kernel issues. Closing the X task, and leaving the plymouth task open for further investigation.
Alright, well so far it isn't sounding like an X bug. Perhaps an error in plymouth, or even could be kernel issues. Closing the X task, and leaving the plymouth task open for further investigation.