Willie Walker wrote:
Please refer to http://bugzilla.gnome.org/show_bug.cgi?id=524263, I made a patch which hopefully can fix the dialog problem. It checks if the IOR is really set to the root window if timeout.On my laptop I sometimes encounter the AT-SPI registry not started dialogue after invoking startx from the shell. So far as I can tell, there seems to be no means of closing this dialogue, and proceeding with the loading of theGnome desktop, from the keyboard.Yeah - it comes up in the upper left corner of the screen and you need to push your mouse there in order to give it focus since no window manager is running at the time. Kind of a pain, but once there, I *think* you can interact with the dialog via the keyboard. There are also other dialogs that appear, such as when you login as root or into a failsafe session, that have similar issues.I've thought about proposing a solution to these, such as forcing the dialog to appear in the center of the display, which is where the mouse comes up when the X server starts, or forcing a mouse move over the window. Not really quite sure if anyone would be interested in implementing these, but I'd really like to see something done. I really don't like using the mouse. :-)This is a timing issue. From what I discovered via a Web search, gnome-session waits for 5 seconds before concluding that the registry hasn't started, then presents this dialogue. On my laptop, possibly due to the slowness of the harddrive, this timeout, I suspect, sometimes expires.Li recently did some work in this space. I've CC'd him so he can comment.
Li