As much as I appreciate being able to refer to xerrs.log when something has really gone wrong in any Puppy, it seems to me that, a lot of times, xerrs.log is just an "automatic grouch".

A few examples :

It complains when you use an older GTK theme that this or that parameter in the theme file is not valid anymore, that parameter x has now been replaced with parameter y, or what have you.

If your gnome-mplayer is not configured properly, it sends you a vdpau (nvidia) message, even if your video card is a radeon card.

It sends you kde error messages, even if you don't have KDE installed.

BK's / don570's report-video is logged there even if you don't ask for it.

It's never satisfied with the syntax you use for "kill".

There are many aspects to this, not the least being the perception among new users that this or that Puppy is full of errors. There was also this time when a fellow user jumped on my back like a mountain lion because I had not included enough "black hole" messages (>/dev/null 2>&1) in my code.

So, to maintain my self-esteem as well as in the interest of having a nicely humming Puppy:

What are the utilities that send messages to xerrs.log ?

How can one make theses utilities just sensitive enough to catch real errors, so that we do not confuse errors with regular system reports?

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum