[Bug 461710] New: Do not set GNOME_ACCESSIBILITY environment variable.

[jhbuild (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=461710

  jhbuild | general | Ver: unspecified
           Summary: Do not set GNOME_ACCESSIBILITY environment variable.
           Product: jhbuild
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: general
        AssignedTo: jhbuild-maint at gnome.bugs
        ReportedBy: wbolster at gnome.org
         QAContact: jhbuild-qa-maint at gnome.bugs
                CC: chpe at gnome.org, pkg-gnome-
                    maintainers at lists.alioth.debian.org,
                    william.walker at sun.com, wbolster at gnome.org
 BugsThisDependsOn: 435325
     GNOME version: Unspecified
   GNOME milestone: Unspecified


This bug is based on bug 435325#8, in which Li Yuan (atk developer) states:

> 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.

So, I think jhbuild should not set GNOME_ACCESSIBILITY=1.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=461710.