Re: at-spi registry not working on my system at all



You can try to build at-spi with "--enable-xevie=no" to disable XEVIE. And make sure at-spi-registryd locate in the right directory (depends on your drstro) by "--libexecdir="

Regards,
Li

John covici wrote:
How do I find out -- the answer to your question -- sorry for the
newbie question.

on Tuesday 01/13/2009 Li Yuan(Li Yuan Sun COM) wrote
 > Hi John,
> > Seems your at-spi-registryd isn't started. Is you at-spi-registryd built > with XEVIE but X doesn't load that extension? > > Regards,
 > Li
> > > John covici wrote:
 > > Hi.  I have a gentoo system using kernel 2.6.27-gentoo-r4 and gnome
 > > 2.24 components and I cannot get at-spi registry to work on my system
 > > at all.  The user in question definitely has accessibility enabled,
 > > but here is the .xsession errors I get -- some of these are due to me
 > > having to shutdown the X server, but otherwise here is the output.
 > >
 > > /etc/X11/gdm/Xsession: Beginning session setup...
 > > /etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent --
 > > /usr/bin/seahorse-agent --execute gnome-session
 > >
 > > (seahorse-agent:28193): atk-bridge-WARNING **: AT_SPI_REGISTRY was not
 > > started at session startup.
 > >
 > > (seahorse-agent:28193): atk-bridge-WARNING **: IOR not set.
 > >
 > > (seahorse-agent:28193): atk-bridge-WARNING **: Could not locate
 > > registry
 > > Xlib:  extension "XEVIE" missing on display ":0.0".
 > > SESSION_MANAGER=local/ccs.covici.com:/tmp/.ICE-unix/28193
 > > ** Message: another SSH agent is running at:
 > > /tmp/ssh-dDtiV28193/agent.28193
 > > 1230985346.768587 Session manager: disconnected...
 > > Window manager warning: Failed to read saved session file
 > > /home/martin/.config/metacity/sessions/default0.ms: Failed to open
 > > file '/home/martin/.config/metacity/sessions/default0.ms': No such
 > > file or directory
 > > Window manager warning: xserver doesn't have 'fixed' font.
 > > 03/01/2009 07:22:29 Autoprobing TCP port
 > > 03/01/2009 07:22:29 Autoprobing selected port 5900
 > > 03/01/2009 07:22:29 Advertising authentication type: 'No
 > > Authentication' (1)
 > > 03/01/2009 07:22:29 Advertising security type: 'No Authentication' (1)
 > > Failed to play sound: Sound disabled
 > > Window manager warning: Could not create directory
 > > '/home/martin/.config/metacity': No such file or directory
 > > Window manager warning: Could not create directory
 > > '/home/martin/.config/metacity/sessions': No such file or directory
 > > Window manager warning: Could not open session file
 > > '/home/martin/.config/metacity/sessions/27b81cf17-f5e7-461d-8600-51b2069c19d6.ms'
 > > for writing: No such file
 > > or directory
 > >
 > > (gnome-panel:28270): Gtk-WARNING **: gtk_widget_size_allocate():
 > > attempt to allocate widget with width -5 and height 24
 > > The program 'nautilus' received an X Window System error.
 > > This probably reflects a bug in the program.
 > > The error was 'BadName (named color or font does not exist)'.
 > >   (Details: serial 201 error_code 15 request_code 45 minor_code 0)
 > >   (Note to programmers: normally, X errors are reported
 > >   asynchronously;
 > >    that is, you will receive the error a while after causing it.
 > >    To debug your program, run it with the --sync command line
 > >    option to change this behavior. You can then get a meaningful
 > >    backtrace from your debugger if you break on the gdk_x_error()
 > >    function.)
 > > The application 'gnome-session' lost its connection to the display
 > > :0.0;
 > > most likely the X server was shut down or you killed/destroyed
 > > the application.
 > > The application 'vino-server' lost its connection to the display :0.0;
 > > most likely the X server was shut down or you killed/destroyed
 > > the application.
 > > Window manager warning: Lost connection to the display ':0.0';
 > > most likely the X server was shut down or you killed/destroyed
 > > the window manager.
 > > The application 'gnome-panel' lost its connection to the display :0.0;
 > > most likely the X server was shut down or you killed/destroyed
 > > the application.
 > > The application 'vino-server' lost its connection to the display :0.0;
 > > most likely the X server was shut down or you killed/destroyed
 > > the application.
 > > Window manager warning: Could not find display for X display
 > > 0x9e4bb48, probably going to crash
 > > Bug in window manager: IO error received for unknown display?
 > > The application 'gnome-panel' lost its connection to the display :0.0;
 > > most likely the X server was shut down or you killed/destroyed
 > > the application.
 > > The application '<unknown>' lost its connection to the display :0.0;
 > > most likely the X server was shut down or you killed/destroyed
 > > the application.
 > > The application 'gnome-session' lost its connection to the display
 > > :0.0;
 > > most likely the X server was shut down or you killed/destroyed
 > > the application.
 > >
 > > Another user of the system gdm-session will not start at all, although
 > > no messages are given.
 > >
 > > This has stumped me, so any assistance would be appreciated.
 > >
> >



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]