On Sat, Mar 06, 2010 at 07:36:58AM EST, Jacob Schmude wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi > I can confirm that it seems to be a timing issue as to when notify-osd > starts. I've never had it stop working in a session, but in the sessions > where it does not send events to at-spi, killing and respawning it seems > to take care of the problem in every instance I've tested so far. > Lucid users, is this fixed there or still happening? If it's still > happening then the startup sequence should probably be modified so that > notify-osd always starts up after accessibility support is ready. I > understand starting services in parallel, but some services if > applicable should start before any others.
In lucid, this should not be a problem. There have been a lot of tweaks done to improve the desktop startup speed, one of which is for notify-osd to be started only when its needed, and since accessibility comes up very very early in the session, all notifications should be accessible from the get go. Luke -- Ubuntu-accessibility mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
