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 435325 - Excess verbosity
Excess verbosity
Status: RESOLVED DUPLICATE of bug 455120
Product: atk
Classification: Platform
Component: gail
1.18.x
Other Linux
: Normal normal
: ---
Assigned To: Li Yuan
Li Yuan
Depends on:
Blocks: 461710
 
 
Reported: 2007-05-02 21:56 UTC by Sven Arvidsson
Modified: 2007-07-30 08:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18

Attachments
Proposed fix (877 bytes, patch)
2007-07-28 19:07 UTC, Wouter Bolsterlee (uws) 		none Details | Review
Proposed fix, part 2 (487 bytes, patch)
2007-07-28 19:11 UTC, Wouter Bolsterlee (uws) 		none Details | Review

Description Sven Arvidsson 2007-05-02 21:56:52 UTC 
[ Forwarded from http://bugs.debian.org/284248 ]

"Every Gtk+ application prints two lines to stdout on startup:

  Bonobo accessibility support initialized
  GTK Accessibility Module initialized

grep indicates that the first one comes from libgail-gnome.so, and the
second one from libgail.so (both in /usr/lib/gtk-2.0/modules/).

Please disable these messages as they are annoying and serve no useful
purpose to a regular user."
Comment 1 Wouter Bolsterlee (uws) 2007-07-28 19:07:17 UTC 
Created attachment 92608 [details] [review]
Proposed fix

Yes, these messages keep annoying me as well. Please apply the attached (trivial) patch to get rid of the console spew. Thanks!
Comment 2 Wouter Bolsterlee (uws) 2007-07-28 19:08:09 UTC 
(or set patch status to "commit now"... it's fine to do it myself)
Comment 3 Wouter Bolsterlee (uws) 2007-07-28 19:11:46 UTC 
Created attachment 92609 [details] [review]
Proposed fix, part 2

And this one is for the bonobo message.
Comment 4 Li Yuan 2007-07-29 04:01:35 UTC 
I think we just make application only print the messages when GNOME_ACCESSIBILITY=1, as you can see in the code. Can you still see these messages in the lastest gnome2.19 when you don't set GNOME_ACCESSIBILITY?
Comment 5 Li Yuan 2007-07-29 04:20:25 UTC 
I would mark this bug as a duplicate of bug  455120, please tell me if the fix is not satisfy you.
Comment 6 Li Yuan 2007-07-29 04:20:53 UTC 

*** This bug has been marked as a duplicate of 455120 ***
Comment 7 Wouter Bolsterlee (uws) 2007-07-29 18:36:24 UTC 
GNOME_ACCESSIBILITY is automatically turned on on my setup (jhbuild does it). Regardless of this env var programs should not show so much debug stuff.
Comment 8 Li Yuan 2007-07-30 02:11:19 UTC 
Why GNOME_ACCESSIBILITY is automatically turned on by jhbuild? If it want to start applications with A11Y support, the official way is to set gconf key. GNOME_ACCESSIBILITY should only be turned on by A11Y developers who want to see these messages.
Comment 9 Wouter Bolsterlee (uws) 2007-07-30 08:24:54 UTC 
I opened bug #461710 to address this issue.