Hi Bill, Because the crash occurs for a simple at-spi program (a callback for some at-spi events), I can say (for sure) that bug is not in gnopernicus. I really think it is in at-spi/corba/etc. For me, as gnopernicus maintainer is harder to say where the problem is than it is for you, as at-spi maintainer.
I am saying a simple at-spi program, because gnopernicus with the patch previously attached is a simple at-spi tester which registers a callback for some events and displays some information for each. Remus On Mon, 2005-09-19 at 13:28, Bill Haneman wrote: > Remus, all: > > The output you sent does not contain anything that indicates to me that > at-spi is responsible for this problem. In fact, the output doesn't > display any clear information as to the cause of the issue at all, as > far as I can see. > > Bill > > remus draica wrote: > > >Hi, > > > >>From those logs, seems that the connection with X dies for some reasons. > >Because at-spi is responsible with this, it is an at-spi bug. The patch > >I sent to you (the one for gnopernicus) prevents gnopernicus to do > >something. It only shows some information for every event. > > > >Bill, what do you think about this bug? In the attachment are 2 files: > > 1. patch- a patch for gnopernicus to display information for every > >event received by gnopernicus. After displaying, the callback return > >(the original gnopernicus code is not executed). > > 2. gnopernicus.log - the output with this patch. > > > >Daniel, thanks for your help. > > > >Remus > > > > > > _______________________________________________ Gnome-accessibility-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-accessibility-devel
