Could someone affected by this issue please file a RC bug against
at-spi2-core to help others be informed about the bug and avoid
upgrading the package if possible?
Sorry I had too many other commitments today to be able to investigate
and figure out a packaging workaround if needed.
Thank you,
J
Well, I manually grabbed a newer ORCA, but still whether its 46.2 or 47.1,
seemingly same results here, as I am getting evolution warnings along with
something about gst scanner. I did ask on an ORCA list, but some of their
responses were I should dich the console for 2weeks-and-just use ORCA. I
On Thu, Aug 8, 2024 at 1:05 PM Jason J.G. White wrote:
> On 8/8/24 09:32, Jérémy Prego wrote:
> > I don't know if this is the right way to report my bug, but I
> > discovered that updating the atspi2 stack to version 2.53.1-1 prevents
> > orca from starting with a python error :
> Try upgrading Or
On 8/8/24 09:32, Jérémy Prego wrote:
I don't know if this is the right way to report my bug, but I
discovered that updating the atspi2 stack to version 2.53.1-1 prevents
orca from starting with a python error :
Try upgrading Orca as well, as the problem may have been fixed upstream.
On 8/8/24 15:32, Jérémy Prego wrote:
Hello,
I don't know if this is the right way to report my bug, but I discovered
that updating the atspi2 stack to version 2.53.1-1 prevents orca from
starting with a python error :
$ orca
Traceback (most recent call last):
File "/usr/bin/orca", line 50, i
Hello,
I don't know if this is the right way to report my bug, but I discovered
that updating the atspi2 stack to version 2.53.1-1 prevents orca from
starting with a python error :
$ orca
Traceback (most recent call last):
File "/usr/bin/orca", line 50, in
from orca import script_mana
6 matches
Mail list logo
