[Bug 71932] Re: AT_SPI_REGISTRY not started at session startup [feisty]

2010-06-23 Thread sterios prosiniklis
*** This bug is a duplicate of bug 73517 *** https://bugs.launchpad.net/bugs/73517 2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 08:03:28 UTC 2010 x86_64 GNU/Linux I get this set of error messages for pretty much everything ... Solved, worked around with gconftool-2 -s --type=bool /desktop/gno

[Bug 71932] Re: AT_SPI_REGISTRY not started at session startup [feisty]

2010-01-03 Thread SwaJime
*** This bug is a duplicate of bug 73517 *** https://bugs.launchpad.net/bugs/73517 Still looking to see how to fix this ... I get this set of error messages for pretty much everything ... # gnome-volume-control-applet --display=":0" (gnome-volume-control-applet:10259): atk-bridge-WARNING **:

[Bug 71932] Re: AT_SPI_REGISTRY not started at session startup [feisty]

2009-12-29 Thread SwaJime
*** This bug is a duplicate of bug 73517 *** https://bugs.launchpad.net/bugs/73517 I'm getting this same error from "sudo nm-applet" I don't see what this has to do with the "duplicate" yelp bug other than that it has the same error message. $ sudo nm-applet (nm-applet:3700): atk-bridge-WARN

[Bug 71932] Re: AT_SPI_REGISTRY not started at session startup [feisty]

2009-11-30 Thread Mel
*** This bug is a duplicate of bug 73517 *** https://bugs.launchpad.net/bugs/73517 I was wondering if this bug is also affecting Thunderbird loading remote share folders? When I run: thunderbird -jsconsole >From the console I get an error as such: (gecko:3119): atk-bridge-WARNING **: AT_SPI

[Bug 71932] Re: AT_SPI_REGISTRY not started at session startup [feisty]

2006-12-04 Thread Jouni Mettala
*** This bug is a duplicate of bug 73517 *** ** This bug has been marked a duplicate of bug 73517 yelp broken on Feisty: CRITICAL **: AT_SPI_REGISTRY was not started at session startup. -- AT_SPI_REGISTRY not started at session startup [feisty] https://launchpad.net/bugs/71932 -- ubuntu-bu

[Bug 71932] Re: AT_SPI_REGISTRY not started at session startup [feisty]

2006-11-16 Thread Che Guevara
Upstream bug http://bugzilla.gnome.org/show_bug.cgi?id=345428 -- AT_SPI_REGISTRY not started at session startup [feisty] https://launchpad.net/bugs/71932 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 71932] Re: AT_SPI_REGISTRY not started at session startup [feisty]

2006-11-16 Thread Che Guevara
Today's udpdates changed things a bit. When you log in there's a message saying that adaptive something (whatever at-spi support can't be loaded, so a session without support for it will be loaded, but it still bails out -- AT_SPI_REGISTRY not started at session startup [feisty] https://launchpad

[Bug 71932] Re: AT_SPI_REGISTRY not started at session startup [feisty]

2006-11-15 Thread Thomas Wolfe
sorry for multiple comments, damn links2 not showing my comments after i posted them. Anyhow, I just uninstalled (apt-get remove at-spi) and it got rid of a few other packages but after you remove it you can login and use your desktop. (guess the at_spi stuff is for disabled people). -- AT_SPI_R

[Bug 71932] Re: AT_SPI_REGISTRY not started at session startup [feisty]

2006-11-15 Thread Che Guevara
Confirmed Errors: ** (gnome-session:5070): CRITICAL **: AT_SPI_REGISTRY was not started at session startup. WARNING **: IOR not set. ** ERROR **: Could not locate registry aborting... -- AT_SPI_REGISTRY not started at session startup [feisty] https://launchpad.net/bugs/71932 -- ubuntu-bugs mai

[Bug 71932] Re: AT_SPI_REGISTRY not started at session startup [feisty]

2006-11-15 Thread Thomas Wolfe
Fedora is having the same problem, basically gnome-session 2.17.2 now starts the registry and sometimes it does not start. -- AT_SPI_REGISTRY not started at session startup [feisty] https://launchpad.net/bugs/71932 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.co

[Bug 71932] Re: AT_SPI_REGISTRY not started at session startup [feisty]

2006-11-15 Thread Thomas Wolfe
after searching for AT_SPI_REGISTRY in yahoo it seems fedora's dev team also just updated to gnome-session 2.17.2 and I guess now gnome-session starts AT_SPI_REGISTRY again I cannot paste the link, but it looks like they have not really gotten it fixed yet either. Anyone know how I could go about