Now I'm sure gdm isn't filling up my .xsession-errors.
Instead this is a screenlets issue. When a screenlet is configured to start automatically after login, no logfile is specified and its log messages are added to the .xsession-errors file and not to their destinated ones.
I'm not a Pyhton man but perhaps autostarted screenlets should log into /dev/null since some of them are producing many log messages in a short period of time.
Now I'm sure gdm isn't filling up my .xsession-errors.
Instead this is a screenlets issue. When a screenlet is configured to start automatically after login, no logfile is specified and its log messages are added to the .xsession-errors file and not to their destinated ones.
I'm not a Pyhton man but perhaps autostarted screenlets should log into /dev/null since some of them are producing many log messages in a short period of time.