-----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.
Tested in Ubuntu 9.10, all updates applied -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkuRa2oACgkQybLrVJs+Wi7RvACfXsywn9A/TD6vuxdsIbo3ovyQ 8bwAn1G83OH6o72nuOm5/XuDRGkdjP1q =WVru -----END PGP SIGNATURE----- -- Ubuntu-accessibility mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
