desktop-packages team mailing list archive

[Karlt <857153@xxxxxxxxxxxxxxxxxx>]

(In reply to Trevor Saunders (:tbsaunde) from comment #49)
> well, the firstthing that comes to mind is arranging for build machines and
> test machines to have GNOME_ACCESSIBILITY set, do we have an idea how hard
> this is?

It would be good to ensure there is a session bus, because we'd like to test the dbus code.  Perhaps DBUS_SESSION_BUS_ADDRESS is not set because of the way our testing connects to the existing gnome session.  Or perhaps the CentOS 5.0 machines are just too old to have a session bus running.  On these systems the GConf code can provide information on whether accessibility is enabled.
If the test slaves were fine on comment 39's landing and it was only build machines that had failure, then that might be because the tests slaves are running a newer OS, one likely to have a DBus session, and DBUS_SESSION_BUS_ADDRESS may be set there.

You might need to ask someone from releng how our build/test slave
starts up and whether that inherits environment variables from the gnome
session.

If you only need accessibility enabled for accessibility tests then it
probably makes sense to set GNOME_ACCESSIBILITY in the Makefile command
that runs the accessiblity tests.

> I'd expect though that in the vast majority of cases  that there is a
> session and this is not relavent. Karl would you  object if I merge that
> change set?

No I would not object.  Please add a comment to explain why the
DBUS_SESSION_BUS_ADDRESS environment variable is there though.

The situation with dbus when it can't connect to a session bus is
unfortunate, and perhaps something worth avoiding anyway, if we can.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/857153

Title:
  Needs to get accessibility settings from GSettings

Status in The Mozilla Firefox Browser:
  Confirmed
Status in “firefox” package in Ubuntu:
  Triaged
Status in “firefox” source package in Oneiric:
  Triaged
Status in “firefox” source package in Precise:
  Triaged

Bug description:
  Luke mentioned to me in Dublin that the screen reader doesn't work
  with Firefox when accessibility is enabled. This is because Firefox is
  still using GConf to check if accessibility is enabled, when it really
  needs to be using GSettings. I've just realized this is still the
  case, so I assume that the screen reader still won't work by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/857153/+subscriptions