[gdm-list] at-spi-registryd not starting automatically in gdm [was multiple at-spi...]

[Francesco Fumanti <francesco fumanti gmx net>]

Hello,


At 12:08 PM -0500 8/28/07, Brian Cameron wrote:
> You mention you are using Ubuntu.  Others on Ubuntu have complained about
> this problem.  Do you not see this?
>
>   http://bugzilla.gnome.org/show_bug.cgi?id=440948

The problem does not occur on my setup. In fact, I am using gdmlogin 
with Assistive Technology activated without a problem on Ubuntu 7.10 
due for October (it is the version under development). I am even 
using it under 7.10 with onboard and mousetweaks.

As I also have a partition with the current 7.04 version of Ubuntu, I 
tried to start gdmlogin with Assistive Technology enabled. It works 
also.


Please, consider that I am working remotely; but I assume that it is 
not what is making the difference. Could it be the following?
http://bugzilla.gnome.org/show_bug.cgi?id=457998




> > I have been told that the automatic start of at-spi-registryd in 
> > ubuntu has probably been disabled on purpose because of 
> > incompatibilities with certain hardware.
>
> This seems badly broken to me.  What incompatibilities?  Are there
> bugs filed about these issues?  I assume that Ubuntu doesn't disable
> starting at-spi-registryd in the user's session.  If it works okay
> in the session, how does hardware issues create problems for GDM
> only?

Sorry, my assertion of at-spi-registryd being probably disabled on 
purpose was not correct; here is what Sebastien Bacher replied to me 
on the ubuntu-desktop mailing list; Sebastien Bacher is the 
maintainer of the desktop for ubuntu:

At 11:26 AM +0200 8/29/07, Sebastien Bacher wrote:
>  > On my setup and on another persons setup (I am talking about gutsy; I
> >  have not checked for feisty), at-spi-registryd does not run when I
> >  enable Assistive Technology in the Login Window preferences panel.
>
> That looks like a gdm bug then, we don't patch it to not run the
> registry
>
>
> >  Consequently, could anybody please confirm to me that
> >  at-spi-registryd is disabled by default during gdm in Ubuntu (I am
> >  not talking about the gnome session at the moment), even if Assistive
> >  Technology is enabled?
>
> There is no change over upstream there, if there is an issue it's likely
> coming from the upstream code.

Moreover, the fact that at-spi-registryd starts automatically in 
Ubuntu 7.04 could be seen as a confirmation of that fact; I just 
checked it. (I am using normally Ubuntu 7.10)

Apart from the developer of mousetweaks, I have not got another 
confirmation yet, that the problem also occurs on other computers 
running ubuntu...


I have searched syslog for an error regarding at-spi-registryd; but 
could not find anything. But that may also be due because I don't 
really know what to look for. (I have debug enabled in gdm)

Should at-spi-registryd be started by gdm or by gdmlogin?


If you have some ideas about how to narrow down the problem, please 
don't hesitate. I would say to first check whether gdm/gdmlogin tries 
to start at-spi-registryd...


I will file a bug against gdm in Ubuntu shortly.


Francesco

PS: Meanwhile, I suspect the XEVIE error that I mentioned in a 
previous email is due to the fact that I tried to start it with a 
terminal remotely through X and my local X server does not offer the 
necessary lib. (at-spi-registryd does start automatically in the 
gnome session, and also by a dwell gesture in the gdm session)