Errors scroll by too fast to read. Which log files should I check?

[kortsen]

I have started getting about a dozen errors scrolling by when I boot. It seems to be just about when X is starting. All I can catch is that each one starts with

Networkmanager: <debug> . . . . .

Which log files should I look in, or how do I pause the boot process so I can stop and read them?

BTW: System seems to run fine in spite of this.

[kubicle]

Re: Errors scroll by too fast to read. Which log files should I check?

I have started getting about a dozen errors scrolling by when I boot. It seems to be just about when X is starting. All I can catch is that each one starts with

Networkmanager: <debug> . . . . .

You can start ksystemlog to browse several system logs graphically.

dmesg

Is a useful CLI command (for most situations) to view log messages. (pipe with 'grep' to search, 'tail' to view last and 'less' to browse, 'dmesg | less', for example

BTW: System seems to run fine in spite of this.

Generally <debug> level messages are not errors and are usually part of the normal function of the process. Although it doesn't hurt to check what they are about (out of curiosity if nothing else).

[stealthbanana]

Re: Errors scroll by too fast to read. Which log files should I check?

also
/var/log/syslog
/var/log/messages

have a poke out in /var/log most everything will be logged there so you can get the errors, good way of learning about the system.