Who should I address this xerrs.log to? [SOLVED]

Please post any bugs you have found
Post Reply
Message
Author
musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

Who should I address this xerrs.log to? [SOLVED]

#1 Post by musher0 »

Hi guys.

The attached would put anyone in a grouchy mood...

A 250 k error log created in approx. one hour -- on the xenialPup k-4.1 32-bit I
whipped up yesterday.

Ok remove 10 k because I am using a nice, but older, non updated, GTK-2 theme.
(cafeconleche if you want to know)

For the rest, (don't) enjoy the read.

The best thing to do would be to return the apps to the devs for a refund, but
open source / GPL stuff don't work that way.

On the Puppy side, how complicated is it to ad

Code: Select all

2>/dev/null
at the end of the command line in every g.dd..n defaultschmurf file in /usr/local/bin?

If I was your prof, I'd give you guys an F. Geez.

BarryK put the xerrs.log system and file in Puppy for a reason.
Look at it! Use it! Learn! :evil:
Attachments
xerrs.log.zip
!%?&@(...
(9.79 KiB) Downloaded 152 times
Last edited by musher0 on Mon 23 Oct 2017, 16:31, edited 1 time in total.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

Sailor Enceladus
Posts: 1543
Joined: Mon 22 Feb 2016, 19:43

#2 Post by Sailor Enceladus »

Hi musher0,

I'm also trying your Xenialpup 7.0.6. After 1 hour and 18 minutes my xerrs.log is 26K, but I probably didn't explore as many things as you did. It looks like almost all of the things in my xerrs.log related to GLib, I get these kinds of warnings mostly in many programs (geany, leafpad, palemoon, hexchat, netmon_wce, clipit, retrovol, gtkdialog, yaf-splash, etc.):

Code: Select all

GLib-GObject-WARNING **: Two different plugins tried to register 'GLibProxyResolver'.

GLib-GObject-CRITICAL **: g_type_add_interface_dynamic: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed

GLib-GIO-WARNING **: Tried to register an extension of the type (null) to extension point gio-proxy-resolver. Expected type is GProxyResolver.
I didn't explore if other puppies give these error message less or if this is normal noise yet. Attached my xerrs.log as well.
Attachments
xerrs.log.tar.gz
(2.49 KiB) Downloaded 188 times

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#3 Post by musher0 »

Thanks, Sailor.

Yep, there's a big concordance between your xerrs.log and mine.

The Glib is probably not an exact fit. I read on another site for construction of a
Linux distro (I can't remember which), that they had to rebuild the Clib for it to
match the finished distro?

Could that be it? But I don't know anything about C, I don't know how to solve
those errors.

What I've been doing is throwing errors in the void (2>/dev/null) in the case of
the defaultschmurf files in /usr/local/bin. It's only cosmetic, until someone
offers a better solution.

BFN.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#4 Post by musher0 »

Hello all.

I did a bit more research on the subject, which now leads me to think that this is an
ubuntu feature. Not a bug, and on ubuntus only.

A search on ask.com offers as targets mostly ubuntu forums threads, and the more
experienced ubuntu-ers there point out that these messages are warnings, not errors,
and to basically "move on, people, there is nothing of interest to see here."

I checked if petihar's Triton (a TahPup-6.0.5 derivative) arboured a similar behavior,
and it does, although to a lesser degree. So I guess such "error"-reporting is
intentional on the part of the ubuntu developers.

The DPupStretch's xerrs.log is much cleaner by comparison. If some message is
added to it, there is indeed a problem or a bug.

The moral of this story could be: "if you're the nervous type, don't go for the ubuntu
Pups?" Which would be a shame. But now at least I know why so many messages
pile up in the ubuntu Pups xerrs.log file and not in the DPupStretch's one.

BFN.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#5 Post by musher0 »

Hello people.

I finally found a general solution.

It is in script /usr/bin/xwin, line 161 (on the xenialPup;
probably a different line number on other Pups)

Simply change the end of the line from
2>&1
to
2>/dev/null.
#-----------------------------------------------------------------------
/usr/bin/xinit /root/.xinitrc -- -br -nolisten tcp > /tmp/xerrs.log 2>/dev/null
# BarryK's original ending: 2>&1 #### Edit by musher0, Oct. 23, 2017
#-----------------------------------------------------------------------
# BarryK's original ending: 2>&1 #### Edit by musher0, Oct. 23, 2017
# 2>/dev/null will send the error reports to never-never land, and you
# will have an almost clean xerrs.log. If you notice something fishy going
# on on your system, do not hesitate to restore BarryK's original ending.

This effectively deactivates error-reporting to xerrs.log. Only the messages
normally emitted by the apps will now be registered in xerrs.log. XArchive's list of
compression engines, for example, but not the Glib or Gobject warnings, etc.

IHTH. Peace can finally be with us! ;)
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

Post Reply