Since dbus is not started via gnome-session, any process that dbus launches is not accessible.
This is because gnome-session looks in gconf to see if accessibility is enabled and sets GTK_MODULES
accordingly before it launches dbus. As you guys mentioned, gnome-session will not launch dbus if it has already been started.
A good example is notification-daemon, any notification bubble that it pops up is completely inaccessible, so a screen reader user in Edgy will never find out that her battery is about to run out, before it is too late.
I am not very familiar with Ubuntu conduct in these cases, but is there a chance a fix could be pushed to Edgy users?
Just another thought,
Since dbus is not started via gnome-session, any process that dbus launches is not accessible.
This is because gnome-session looks in gconf to see if accessibility is enabled and sets GTK_MODULES
accordingly before it launches dbus. As you guys mentioned, gnome-session will not launch dbus if it has already been started.
A good example is notification- daemon, any notification bubble that it pops up is completely inaccessible, so a screen reader user in Edgy will never find out that her battery is about to run out, before it is too late.
I am not very familiar with Ubuntu conduct in these cases, but is there a chance a fix could be pushed to Edgy users?
Cheers!