After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 707421 - Improve handling of warnings and criticals
Improve handling of warnings and criticals
Status: RESOLVED DUPLICATE of bug 622441
Product: mutter
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2013-09-03 20:58 UTC by Giovanni Campagna
Modified: 2018-02-05 09:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Improve handling of warnings and criticals (6.65 KB, patch)
2013-09-03 20:58 UTC, Giovanni Campagna
none Details | Review

Description Giovanni Campagna 2013-09-03 20:58:09 UTC
Instead of squash everything into "window manager warnings",
let the glib log framework handle Mutter (and other) warnings.
META_USE_LOGFILE support is preserved by rerouting warnings
in our domain.
This way we get process name and PID, nice CRITICAL/WARNING/ERROR
instead of a number, and the ability for plugins to override
the log handler. For example gnome-shell uses this to output
a JS backtrace.
Comment 1 Giovanni Campagna 2013-09-03 20:58:13 UTC
Created attachment 254019 [details] [review]
Improve handling of warnings and criticals
Comment 2 Colin Walters 2013-09-03 21:05:47 UTC
Review of attachment 254019 [details] [review]:

Welcome to the club!  https://bugzilla.gnome.org/show_bug.cgi?id=622441  =)
Comment 3 Giovanni Campagna 2013-09-03 21:09:48 UTC
I know, I was already in the club:
https://bugzilla.gnome.org/show_bug.cgi?id=637573

But the world is different now, metacity is dead, half of the libraries are not covered by that log handler, and we have JS backtraces in the shell.
Comment 4 Jonas Ådahl 2018-02-05 09:31:02 UTC
Going to close this as a duplicate of 622441 to have less of the same task in the list.

*** This bug has been marked as a duplicate of bug 622441 ***