Summary: | gnome-extra/at-spi-1.30 built with --enable-relocate breaks other tools | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pacho Ramos <pacho> |
Component: | [OLD] GNOME | Assignee: | GNOME Office (OBSOLETE) <gnome-office+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | cornicx, covici, marek.bartosiewicz, nerdboy |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pacho Ramos
2010-06-12 16:59:38 UTC
This is caused by at-spi being built with "--enable-relocate" (In reply to comment #1) > This is caused by at-spi being built with "--enable-relocate" > And then, version in tree doesn't use that option *** Bug 314781 has been marked as a duplicate of this bug. *** *** Bug 323841 has been marked as a duplicate of this bug. *** yeah i can confirm this too... noc cuhce use avaibale [I] gnome-extra/at-spi Available versions: (1) 1.24.1!t 1.26.0!t 1.28.1!t (~)1.30.1!t{tbz2} (~)1.30.1!t{tbz2}[1] {debug doc test} Installed versions: 1.30.1(1)!t{tbz2}[1](13:06:48 14.06.2010)(-debug -doc -test) Homepage: http://developer.gnome.org/projects/gap/ Description: The Gnome Accessibility Toolkit [1] "gnome" /usr/portage/local/layman/gnome afaik this is a problem with the new accessibility modules not being compatible with the older ones and was already reported. Anyway this won't be a problem with 2.32 as looks that upstream has defaulted to relocate and modules will likely be adapted to this in the next stable cycle Fixed in 2.32 1.32.0-r1 enables relocation again and breaks all :S *** Bug 382759 has been marked as a duplicate of this bug. *** *** Bug 386571 has been marked as a duplicate of this bug. *** (In reply to comment #9) > 1.32.0-r1 enables relocation again and breaks all :S The fixes are not too complicated: change "import pyatspi" by "import pyatspi_corba" The problem is how to change it "easily", I mean: $ grep -r "import pyatspi" * inside orca sources show a ton of files to change: 1. Should I generate a bug patch with each change? 2. Could I put in ebuild a sed/grep call to to the same? Any ideas welcome as I think we need to keep --enable-relocate if we want at-spi:2 unmasked (In reply to comment #12) [...] > 1. Should I generate a bug patch with each change? [...] bug -> big Yes we need to keep this enabled to have at-spi:1 and at-spi:2 coexisting which is required if you want accessibility for anything gnome2 based while running gnome3 Looks like only orca is affected and it will be solved once orca-3 is unmasked, then, this isn't as major problem as it seemed :) newer orca is unmasked |