thanks for all the replies - too much to take in all at once, but I'll revisit the .xsession-errors file again in a couple of days, right now there's only half a dozen lines in it. didn't feel inclined to check out it's contents yesterday as i presumed there'd be quite a lot in it!

and this learner will be sticking to kde for now. it's interesting that the linux community seems to be divided between the kde and gnome camps. if i change now, in a month or 2 there'll be someone saying kde is better...

anyway, today i'm glad to have sorted yesterday's problem. i have plenty more . . . happy to say i'm managing to slowly answer the questions i have through googling, man pages, rute, experimenting and breaking, reinstalling, luck, and this forum (both posting and reading).

these days i am spending at least a quarter of my home computer time in linux (even if many of my emails come from windows), and this will only get larger and larger as i work my way through all the mysteries and intracacies of an operating system that is both very similar yet very different to one i have already "mastered".

thanks again to you all.
roger


steve wrote:

steve wrote:

Christopher Sawtell wrote:

On Tue, 25 May 2004 22:54, steve wrote:


Roger Searle wrote:


[EMAIL PROTECTED] roger]# find /home -mtime -1 -size +10240k | xargs ls -ld


[ snip ]


then to konqueror to see that .xsession-errors is 8.3GB  !!!
so...
rm .xsession-errors

Thanks for the help finding this. The obvious question now being: what
was causing that? Presumably it's going to grow again.


Yes, It is.



You're going to have to read _all_ of it to find that out (:


^^

.xsession_errors is usually filled by Konqueror. Time to move over to gnome? It's much more mature than kde.

Steve


Sory to follow up on my own post... very bad form I know. I've just run up2date on my Fedora 1 machine, and it's found a load of kde updates. Maybe there are similar available for you on Mandrake?? Every little helps!

Steve


Not necessarily, the command;-

tail -f .xsession-errors
will allow you to watch the tail of the file as it grows. ( CTRL-S and CTRL-Q ) allow you to stop and start the flood of text.


There will probably be a meaningful message or three in there.

/usr/sbin/lsof | grep '.xsession-errors'
will also tell you which programs have .xsession-errors open.









Reply via email to