When a problem shows up somewhere in Chromium OS's UI layer, there are a few components that could be to blame. With a little sleuthing, it's often possible to narrow things down.
Soon after the kernel comes up, the
Hopefully not too long after that, the
After X is running, the UI task starts
Once Chrome has started successfully, it creates a few windows. Most noticeably, it creates a new background with some information (time, battery, network, etc.) in its upper right corner. If this window never appears, it probably means that Chrome didn't start successfully. You can check if this is the problem by looking at the session manager log, Chrome's log at
If the window manager fails to start, you'll probably still see Chrome's login windows onscreen, but they'll be jumbled all over the place instead of arranged correctly. The window manager's output before the user has logged in is spread between the UI task's log (before it knows whether the user is logged in or not) and
isn't logged in).
After the user types their password and hits enter, Chrome displays a spinner on top of the user entry. If the password was correct, Chrome unmaps the login windows and gets to work setting things up for the user's session. The window manager continues displaying the login windows onscreen until Chrome has mapped the first browser window. If the system appears to be stuck in this state for a long time, it probably means that Chrome is crashing; see the information about Chrome in the next section.
Once the user has logged in, Chrome and the window manager switch to new log files located within the user's encrypted home directory: Chrome starts writing to
If Chrome or the window manager crash, the session manager will notice and try to restart them. Depending on the nature of the crash, the processes may write a helpful message to their log files before getting restarted (which will cause them to start new log files; you should able to find the older versions alongside the new ones). Crash dumps may also be written to
X can also die. If this happens, you'll get booted back to the login prompt as well, and there should be a message about the crash in