GNOME Bugzilla – Bug 329407
unable to find a11y registry when running yelp from jhbuild shell
Last modified: 2007-02-10 17:41:41 UTC
Not sure what's going on here. Backtrace was generated from '/opt/gnome2/bin/yelp' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1229752096 (LWP 8958)] [New Thread -1285887056 (LWP 8971)] [New Thread -1277494352 (LWP 8970)] [New Thread -1269101648 (LWP 8969)] [New Thread -1260708944 (LWP 8968)] [New Thread -1252262992 (LWP 8960)] [New Thread -1238910032 (LWP 8959)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 65805
Thread 1 (Thread -1229752096 (LWP 8958))
Reproducing this on Mandriva Cooker with Yelp 2.13.4 package from gpwgnome.osknowledge.org.
Seems like your system config is hosed somehow. Does the at-spi-registryd show us in the process table? Can other apps find it?
I have heard reports that this problem is affecting users "without accessibility enabled", which does not make sense to me at all (since the relevant code is in the atk-bridge which only gets loaded with assistive technology support ON). What's up there?
I have heard reports that this problem is affecting users "without accessibility enabled", which does not make sense to me at all (since the relevant code is in the atk-bridge which only gets loaded with assistive technology support ON). Looks like something in the mozilla execution environment that prevents it from finding the at-spi-registryd... maybe the mozilla env isn't able to do bonobo activation because it's not looking for the .server files in the right place?
So here's the skinny on this: I can only reproduce when I'm running a gnome 2.12 session, open gnome-terminal and do a "jhbuild shell" which adds /opt/gnome2/bin/ to my path, and /opt/gnome2/lib to the LD_LIBRARY_PATH among other things. I have accessibility disabled in this session. When I actually boot into a fresh jhbuild of gnome 2.14 I don't see this problem happening. The a11y patch that DonS applied causes this issue as it did not happen before the patch. Since there was one duplicate/similar issue reported in this bug I pulled the patch because there's no way to tell how many people are affected.
Yes, my patch did cause this, although as I said, I suspect darker forces at work here. I filed [1] downstream. Basically, when I try logging into ubuntu (Dapper - the latest devel branch) with accessibility enabled, I get the same error. I can get around this by disabling accessibility but yelp still crashes when run. I know this isn't just me [2] and comment #1 suggests this is more than a Ubuntu problem. As with Brent, if I log into a fresh jhbuild session (as of the end of January) instead of the default ubuntu session, I don't see this problem, so it may be a downstream problem. [1] https://launchpad.net/distros/ubuntu/+source/gnome-session/+bug/30248 [2] https://lists.ubuntu.com/archives/ubuntu-devel/2006-February/015277.html [3] https://lists.ubuntu.com/archives/dapper-changes/2006-January/005654.html
Problem with pulling Don's patch is that pulling it regresses some a11y functionality. The jhbuild setup where the bug manifests seems like it only bites developers, not end-users. I suspect something weird with libraries, maybe some piece of bincompat has gotten broken and an obsolete library is somehow getting pulled in in this specific situation? Or perhaps the problem is that in the case you describe, there end up being two instances of the a11y daemons/registry/etc. running for the same userid (which I believe we don't currently support!). There's still no way I can evaluate this since I cannot, so far, reproduce it.
I've done a full reinstall of Dapper. I'm still testing it out, but I can't seem (at the moment) to reproduce this problem. I'll keep trying though.
Aparently this has now been fixed in Ubuntu. Matthew East has tested yelp 2.13.4 and it now works. This seems to be a distro / build-of-at-spi problem. Can re re-commit the patch?
re-committed. Where is the bug about this in Ubuntu?
For reference, the bug report in ubuntu was the one I mentioned earlier: https://launchpad.net/distros/ubuntu/+bug/30248 Which is against at-spi as it was affecting more than Yelp.
*** Bug 381992 has been marked as a duplicate of this bug. ***
*** Bug 397485 has been marked as a duplicate of this bug. ***
*** Bug 403743 has been marked as a duplicate of this bug. ***