I wasn't able to login to my FC3 box as a standard user only root.
I could just make out a CRITICAL error flash up on screen for a very small amount of time (way too quick to read).
In the end I managed to pause and read it using 'scroll lock' (after many, many attempts i've got to say).

I tried adding a log that logged *.* but the error didn't show up.
( I added '*.* /var/log/all in syslog.conf' )

Is there a way to log 'on screen' errors to file?

thanks in advance

Skunkburner

These errors probably log in somewhere. You just have to figure out what is causing the errors, to find where they are logged. X errors are in your home folder under xsession_errors or something a like.

Have a look at the log files in /var/log. There are several you can look at with the cat command.

I guess 'script' is what you want. ???
Everything on screen will be stored to file. Default is ./typescript.

It defintely isn't in /var/log I had already checked that ( I tried adding a log that logged *.* but the error didn't show up. )
there was a reference to it - Just not the error message itself.

>> I guess 'script' is what you want. ???

Thats so very nearly what I wanted! : (

it does log 'on screen' errors - if your logged in, the error I was seeing was at the login prompt (init 3)

btw if run 'script' then change to another user session on the same box (ie alt-ctrl-F2 or whatever) it crashes X - so no joy that way either.

Thanks anyway kaz2100.

I am sure that you have tried "dmesg".

Uh, dmesg will only show you what you saw at startup. To save it to a logfile,
Try:
--Abid Kazmi

I've got some idea (maybe just idiot)

What happens if
#1, you startup your comp with single user mode.
#2, try to set up some sort of log, script can be one of them
#3, try to execute rc scripts one by one manually (manually follow init 3 process)
#4, try to figure out what goes wrong.

or

By the way, file/directory permissions (owner,group) are not messed up.

Dude, that's extreme. It's not that big of a problem.

--Abid Kazmi

How would you know - you didn't post the original problem. At least kaz2100s suggestion is a possible solution not some little troll.

Thanks Kaz2100

abid go troll somewhere else