Testing the latest daily of raring and attempting to use Orca for installation shows that everything still works properly, so at-spi2-core doesn't require a session manager, I think its just trying to find one.
Given the new world order with GTK3 and at-spi, we no longer need to explicitly launch at-spi2 in ubiquity-dm, since GTK now launches at-spi2 via the use of libatk-bridge. I wonder if these messages go away if the at-spi2 loading code from ubiquity-dm is removed.
Testing the latest daily of raring and attempting to use Orca for installation shows that everything still works properly, so at-spi2-core doesn't require a session manager, I think its just trying to find one.
Given the new world order with GTK3 and at-spi, we no longer need to explicitly launch at-spi2 in ubiquity-dm, since GTK now launches at-spi2 via the use of libatk-bridge. I wonder if these messages go away if the at-spi2 loading code from ubiquity-dm is removed.