Re: AT_SPI_REGISTRY

[Janina Sajka]

I'm not sure, but it seems to me that gnumeric shouldn't be looking for
at-spi if accessibility isn't enabled. You could turn it on and restart
X just to see if that clears things up.

PS: If the meaning of this is that gnumeric is finally building in a11y
support, that certainly makes me glad.

But then I could be way off base on all of this.

Janina

Marcel J.E. Mol writes:
> After installing rawhide(-extras) x86-64 on my laptop I get the following
> when starting gnumeric:
> % gnumeric
>
> Bonobo accessibility support initialized
> GTK Accessibility Module initialized
>
> ** (gnumeric:17572): CRITICAL **: AT_SPI_REGISTRY was not started at session startup.
>
> ** (gnumeric:17572): WARNING **: IOR not set.
>
> ** ERROR **: Could not locate registry
> aborting...
> Bonobo accessibility support initialized
> GTK Accessibility Module initialized
>
> ** (gnome_segv2:17573): CRITICAL **: AT_SPI_REGISTRY was not started at session startup.
>
> ** (gnome_segv2:17573): WARNING **: IOR not set.
>
> ** ERROR **: Could not locate registry
> aborting...
> Bonobo accessibility support initialized
> GTK Accessibility Module initialized
>
> ** (gnome_segv2:17574): CRITICAL **: AT_SPI_REGISTRY was not started at session startup.
>
> ** (gnome_segv2:17574): WARNING **: IOR not set.
>
> ** ERROR **: Could not locate registry
> aborting...
>
> and around another 100 more of these, ending with
> Xlib: connection to ":0.0" refused by server
> Xlib: Maximum number of clients reached
>
> (gnome_segv2:17682): Gtk-WARNING **: cannot open display:
>
> And no gnumeric starting up.
> Something similar happens when running the 32-bit firefox (to be able to
> see some flash sites). 64-bit firefox strarts up fine.
> Scanning google or lists did not give any clues...
>
> I'm running kde if that matters.
>
> Any idea?
>
> -Marcel
>
> -- 
> fedora-devel-list mailing list
> [e-mail]
> https://www.redhat.com/mailman/listinfo/fedora-devel-list