xsession-errors bloated humongous [Solved]

[galen]

My .xsession-errors is bloating to the max, 13GB [all free space]
I had plugged in an unsupported scanner via USB
and the errors file went ballistic

How can I stop the system from bloating the errors file?
symlink to /dev/null ?
any config file that can reduce the errors?

[l0dr3]

My .xsession-errors is bloating to the max, 13GB [all free space]
I had plugged in an unsupported scanner via USB
and the errors file went ballistic

How can I stop the system from bloating the errors file?
symlink to /dev/null ?
any config file that can reduce the errors?

On my dev-boxes with debug-enabled apps, i manage such situations the 'logrotate-way'
https://unix.stackexchange.com/a/565825

HTH l0dr3

[TTwrs]

This is the way I do it, plus an alternate...

redirect ~/.xsession-errors to /tmp/.xsession-errors
change in /etc/X11/Xsession ...
ERRFILE=$HOME/.xsession-errors
-to-
ERRFILE=/tmp/.xsession-errors

alternatively, to just start anew with each boot
change in /etc/X11/Xsession ...
exec >>"$ERRFILE" 2>&1
-to-
exec >"$ERRFILE" 2>&1

[CharlesV]

Not sure if this has anything to do with it.. but since updating this morning (updates from day before or yesterday).. my .xsession-errors has been logging the same error up to 20 errors per second.

I have never seen this before.

(Thunar:6575): GVFS-WARNING **: 11:57:51.506: can't init metadata tree /home/charge/.local/share/gvfs-metadata/home: open: Permission denied

[l0dr3]

Not sure if this has anything to do with it.. but since updating this morning (updates from day before or yesterday).. my .xsession-errors has been logging the same error up to 20 errors per second.

I have never seen this before.

(Thunar:6575): GVFS-WARNING **: 11:57:51.506: can't init metadata tree /home/charge/.local/share/gvfs-metadata/home: open: Permission denied

I haven't updated for today, but MXPI shows:

The following packages will be upgraded:
conky-toggle-mx (23.03.01 => 23.11.01)
:

Last time i had such a xsession-errors FLOODING, it was 'conky' :strange:

I'll 'full-upgrade' now .. lets see what happens ...

greetz l0dr3

EDIT#1: even before the 'full-upgrade' - on a OOTB setup of MX 23.1 w#o any specials or debug-enabled apps installed (and w#o the 'logrotate-patch' mentioned above) ...

... my ~/.xsession-errors is ~ 2G!!! after UpTime of 5d : Thats unusual

mostly flooded by message:

[ 49359.91 ] error 143 BadPicture request 139 minor 8 serial 238151122: "RenderBadPicture (invalid Picture parameter)"

[CharlesV]

I had a long list of stuff to update, but the fix on these was simple. Moved two files to a back up folder. ( home and root files in ~/local/share/gvfs-metadata/ out of there. )

Quite a few posts saying these are not needed and only cause issues. Not sure, but that stopped the log flood.

Might be a good thing for OP to check.

[l0dr3]

rebooted ...

[ 28.48 ] error 143 BadPicture request 139 minor 8 serial 36066: "RenderBadPicture (invalid Picture parameter)"
[ 28.58 ] error 143 BadPicture request 139 minor 8 serial 36097: "RenderBadPicture (invalid Picture parameter)"
[ 28.60 ] error 143 BadPicture request 139 minor 8 serial 36128: "RenderBadPicture (invalid Picture parameter)"
[ 28.62 ] error 143 BadPicture request 139 minor 8 serial 36159: "RenderBadPicture (invalid Picture parameter)"
[ 28.68 ] error 143 BadPicture request 139 minor 8 serial 36190: "RenderBadPicture (invalid Picture parameter)"
[ 28.68 ] error 143 BadPicture request 139 minor 8 serial 36219: "RenderBadPicture (invalid Picture parameter)"
[ 28.72 ] error 143 BadPicture request 139 minor 8 serial 36248: "RenderBadPicture (invalid Picture parameter)"
:

WTH!? is going on here

l0dr3

BTW: I DISABLED conky before reboot!!

EDIT#1: OMG! my ~/.xsession-errors.old is ~ ...

-rw------- 1 fide3 fide3 1890027361 Nov 21 21:38 .xsession-errors.old

Thre must be some serious issue, that has nothing to do w#todays updates

forget about this - i wasn't aware that i had NO LOGROTATE CLEANING active on that box

[l0dr3]

rebooted ...

[ 28.48 ] error 143 BadPicture request 139 minor 8 serial 36066: "RenderBadPicture (invalid Picture parameter)"
[ 28.58 ] error 143 BadPicture request 139 minor 8 serial 36097: "RenderBadPicture (invalid Picture parameter)"
[ 28.60 ] error 143 BadPicture request 139 minor 8 serial 36128: "RenderBadPicture (invalid Picture parameter)"
[ 28.62 ] error 143 BadPicture request 139 minor 8 serial 36159: "RenderBadPicture (invalid Picture parameter)"
[ 28.68 ] error 143 BadPicture request 139 minor 8 serial 36190: "RenderBadPicture (invalid Picture parameter)"
[ 28.68 ] error 143 BadPicture request 139 minor 8 serial 36219: "RenderBadPicture (invalid Picture parameter)"
[ 28.72 ] error 143 BadPicture request 139 minor 8 serial 36248: "RenderBadPicture (invalid Picture parameter)"
:

WTH!? is going on here

OK - the reason for that specific .xsession-errors flooding (~10 lines/second !!) on only this one dedicated real-steel MX-Box was:

COMPTON

This is the box, i had all compositing disabled, bcof serious problems with TigerVNC server, when compositing (esp.: compton) was enabled.
I've done this by selecting with 'MX Tweak|Compositor::(None)',
BUT: i forgot to disable the 'Session and Startup|Application Autostart::Compton (X Compositor)'

After a 'pkill -i compton', the above error-flooding stopped immediately !
After disabling loading at session startup - all is quiet again now

I'll do some further test and enable xfvwm-compositor temporarily, to see if the flooding starts again, what then would IMO indicating a problem in/with X11/Mesa
and/or the graphics driver
and/or the TigerVNC capture driver
:

greetz l0dr3

[Uweles]

I also had the problem with Xsession and could solve it!

viewtopic.php?t=75293

[galen]

configuring errors to go to /tmp
and
USB port is erratic
solved issue