Re: Debug output etc, cluttering the terminal
Ben Hutchings <firstname.lastname@example.org> writes:
> On Sun, 2010-08-15 at 17:02 +0100, Neil Williams wrote:
>> Most of the stuff in ~/.xsession-errors which has been mentioned here,
>> are exactly these kind of assertion failure errors:
>> (gnome-power-manager:2346): GLib-GObject-WARNING **: value "-nan" of
>> type `gdouble' is invalid or out of range for property `percentage' of
>> type `gdouble'
>> (polkit-gnome-authentication-agent-1:2468): GLib-CRITICAL **:
>> g_once_init_leave: assertion `initialization_value != 0' failed
>> Those are BUGS. It might not cause symptoms now but it is still
>> relevant to how other bugs in that application are triaged. The
>> upstream code needs to be fixed to check these values before passing
>> them to the relevant function.
> I mostly agree with this. These are warnings, not simply debug
> information, and the application author should fix them. However, each
> specific warning should only be printed once, since that's enough to
> indicate the existence of the bug.
The problem is that those bugs are not going to be fixed, not in a
stable release and often not for years in the developement release. At
least I've seen those GLib-CRITICAL warnings for years now in some apps.
The app works so I, as user, simply don't care. Some developers also
seem to not care and software is released with those errors. The checks
in glib seem good enough to handle such cases sanely so maybe the glib
could be shut up about them for stable releases (or where users just
don't care). Maybe something like setting GLIB_BE_SILENT or so if
recompiling the lib silent is out of the question.