14 Nov
2008
14 Nov
'08
12:13 a.m.
On Thu, 2008-11-13 at 22:14 +0000, Ted.Harding@manchester.ac.uk wrote:
This will make .xsession-errors into a file with zero bytes in, and it will be there when it's next looked for (i.e. when you start X). Again, I'm assuming that your troubles below may have been due to .xsession-errors being missing (or otherwise messed up)
Also I wonder if perhaps the orphaned file was due to something madly writing to .xsession-errors after the inode was deleted. Hence the fsck error, if whatever was in an error state didn't exit properly on the shutdown it wouldn't have closed the now orphaned file it was writing too.