After installation of 13.2 ~/.xsession-errors file is going wild. I have red several posts about it but nevertheless, I think this should not happen. We have journal now, tmpfs, i don’t know what and - expensive SSD-s. I really don’t need my disk filling up with constant info that X can not read some UTF8 character or that indexer can not access some irrelevant file.
When programs explicitly log errors, those may go to the journal.
However, many programs just write unexpected error reports to “stderr” (file descriptor 2). If you run a program from the command line, those will appear in your command prompt session. For graphic programs, “stderr” is redirected so that its output goes to “.xsession-errors” or similar file. Usually people only look at that if they are investigating a problem.
Maybe you should browse through that file, and see if you can identify the program that is producing too much error output. Maybe it was compiled with debug flags.
For me, the file is “.xsession-errors-:0”. It currently is around 74K in size, after being logged in for around 15 hours. I suppose that’s a bit much, but not enough to be a significant problem.
On my system this happens whenever power management puts it to sleep. When it wakes up again there’s a humongous .xsession-error file using 99% of the disk. I think it has something to do with the display being turned off.
That probably removes the directory entry for the file, but leaves the file on disk (without a directory entry) still using space and still filling up until you logout from your desktop session.
On 2015-06-22 06:56, nrickert wrote:
>
> jlturriff;2716270 Wrote:
>> Right now I have a little cron job scheduled that looks for such a file
>> and erases any it finds.
>
> That probably removes the directory entry for the file, but leaves the
> file on disk (without a directory entry) still using space and still
> filling up until you logout from your desktop session.
They are presumably in one or more X config files.