Hi,
The file po/Makefile.in.in is not included with the Orca sources and should be
generated by the build. I deleted it and the package wouldn't build. I fixed
the build by adding to the rules file
override_dh_auto_configure:
NOCONFIGURE=1 ./autogen.sh
dh_auto_configure
Just wan
On Mon, Sep 2, 2019, at 5:12 PM, Samuel Thibault wrote:
> Hello,
>
> thom...@fastmail.cn, le lun. 02 sept. 2019 12:30:11 -0400, a ecrit:
> > The file po/Makefile.in.in is not included with the Orca sources
>
> ?
> It is:
>
> $ tar tf orca-3.32.0.tar.xz | grep Makefile.in.in
> orca-3.32.0/po/M
On Tue, Sep 3, 2019, at 3:58 AM, Samuel Thibault wrote:
> thom...@fastmail.cn, le lun. 02 sept. 2019 19:16:02 -0400, a ecrit:
> > On Mon, Sep 2, 2019, at 5:12 PM, Samuel Thibault wrote:
> > > thom...@fastmail.cn, le lun. 02 sept. 2019 12:30:11 -0400, a ecrit:
> > > > The file po/Makefile.in.in i
I just did a fresh install of testing with the Mate desktop and standard system
utilities. I notice that after logging in it takes a very long time for Orca to
start. When I go to shut down and then restart, it shows at-spi-bus-launcher
as not responding and i strongly suspect this probably is
Hi,
I did a Debian install on a machine where there would previously be no speech
with Debian for the past few months and it worked fine. I used the sid DI daily
build with firmware to install bullseye. Thanks to Samuel and all others who
fixed this.
For those not in the know, dbus-broker is a reimplementation of the dbus-daemon.
I am very interested in this subject when it comes to the accessibility bus. I
have done two types of tests on debian. This requires building the broker from
source and rebuilding at-spi2-core. Used cpu was an 8550u.
On Sun, Oct 6, 2019, at 10:05 PM, thom...@fastmail.cn wrote:
> I just did a fresh install of testing with the Mate desktop and
> standard system utilities. I notice that after logging in it takes a
> very long time for Orca to start. Can anyone reproduce this or is it just
> me?
Turns out its
Hi,
I have followed the discussion on the orca list lately and the conflicts around
GTK 4 accessibility. I guess without getting into the drama of it all, I would
just like to ask those who are knowledgeable if they think we will have Linux
accessibility going into the future. I guess the issue
On Fri, Nov 8, 2019, at 3:21 AM, Devin Prater wrote:
> I would definitely recommend the Mac. You’ll still be able to run free
> software, in an environment like Unix. Optionally, if you use the command
> line, check out https://github.com/tspivey/tdsr
>
> It isn’t as powerful as Fenrir or Spe
I just tried it. I logged in and couldn't get Orca to start. Some dialog was on
the screen about choosing a window manager by default. Maybe if you get past
that, you can start Orca. I thought OpenBox was the default Window Manager but
I guess they let you choose. Ubuntu documentation on a quick
lightdm-gtk-greeter now has an official method to start it. I think using this
in Debian could have some benefits because it would allow blind users to start
and stop the screen reader regardless of whether it was enabled a install time.
From what I can tell, the first change that would need to
11 matches
Mail list logo
