Arch Linux - problems and resolutions

@toadie yes I check the logs, there was nothing sospicious, that line was written in log many times every seconds, journalctl was silent, and grep did not filtering nothing.

Btw I found the problem and I was able to fix it:
The problem was the custom compositor Picom (this package) that is not updated for a while now and it’s becoming obsolete.
All I did was disabling the compositor, check the size of ~/.xsession-errors file that was stable and at that point I was sure and I launch the command yay -Rnf picom, followed by removing picom startup script.
After all of that all my system went ok and ~/.xsession-errors file size is now tiny, I will miss a bit the fancy window composition :] but in the end who cares.

Btw I was pretty sure it was not a bug in xfwm because I did not found any recent google result and my problem was too specific.

Sorry guys if I wasted a bit of your time but thanks for your help, I really appreciated.

2 Likes