Re: Can grub be made to talk?

[am_dxer]

On Tue, Jul 23, 2019, at 1:06 PM, Martin McCormick wrote:

>   I absolutely hate what I call "press and pray" in which
> the silent world prevails and you count button presses in the
> silence and hope and pray that nothing weird happens.
> 
>   Failing speech, I know grub can be configured to work
> through a serial port if one exists at the time grub is needed.

I remember a long time ago when I used Open Suse, they had this thing where you 
could press f9 and it would play speech through the pc speaker of the items in 
the boot menu. It would probably be possible to have a script that created 
small wav files based on grub boot menu items using espeak-ng. This would 
likely be a good start and much easier than getting actual sound devices 
working. Modern sound cards require many complex things like pin configuration 
before anything works. The kernel has files with many individual hardware 
devices and their pin configs to make sure this all works properly. I would 
imagine that initializing a modern sound card would be a difficult project to 
get working in grub.

Re: Orca not reading some punctuation when espeak-ng is used I found so far less than and greater than

[am_dxer]

I will set up a VM in Qemu for testing this sometime this week. I don't want to 
experiment with Espeak-ng and Speech Dispatcher on my main system in case 
speech is lost for some reason since I am totally blind. With any luck, I will 
be able to bisect this. Thanks.

On Mon, Apr 16, 2018, at 4:48 AM, Alex ARNAUD wrote:
> Hello am_dxer,
> 
> I suspect a bug on the speech-dispatcher side or on espeak-ng side. 
> Could it be possible for you to investigate this issue?
> 
> Best regards,
> Alex.
> 
> Le 16/04/2018 à 05:56, am_d...@fastmail.fm a écrit :
> > When using Espeak-ng, Orca doesn't read < or > for me when punctuation is 
> > set to all. I didn't have this problem when using standard Espeak. This can 
> > be reproduced when reading by line or word. I tested in Firefox and Pluma. 
> > The punctuation setting is on the speech tab of Orca's preferences. This is 
> > using Debian testing.
> > 
> 

Orca not reading some punctuation when espeak-ng is used I found so far less than and greater than

[am_dxer]

When using Espeak-ng, Orca doesn't read < or > for me when punctuation is set 
to all. I didn't have this problem when using standard Espeak. This can be 
reproduced when reading by line or word. I tested in Firefox and Pluma. The 
punctuation setting is on the speech tab of Orca's preferences. This is using 
Debian testing.

Re: Mate Upstream Keyboard Shortcuts Unbound in Debian

[am_dxer]

Including the Mate list. I probably should have done that to begin with.

On Sat, Mar 10, 2018, at 8:42 AM, am_d...@fastmail.fm wrote:
> Hi,
> From the bug you sent, I was able to determine where the keyboard shortcuts 
> are being overridden in Debian. See 
> https://anonscm.debian.org/git/pkg-mate/mate-desktop-environment.git/tree/debian/10_mate-common.gschema.override.
> Looking at that file, we can see this. switch-windows-
> all='Tab'
> On a ifferent Linux distrobution that is using vanilla mate, we can see 
> this through gsettings.
> 
> gsettings get org.mate.Marco.global-keybindings switch-windows-all
> 'disabled'
> 
> gsettings get org.mate.Marco.global-keybindings switch-panels
> 'Tab'
> 
> So it appears Debian is reassigning the keyboard shortcut Control+Alt
> +Tab from switch-panels to switch-windows-all. This is in the master 
> branch of packaging so I don't think there is a change for this in Sid. 
> I know that we have some Debian Mate maintainers that are also upstream 
> Mate developers so maybe if this is desired for some reason, it could be 
> pushed upstream instead. I just think it helps everyone's sanity if we 
> can keep keyboard shortcuts consistant across distrobutions if possible.
> 
> On Sat, Mar 10, 2018, at 2:16 AM, Alex ARNAUD wrote:
> > Le 09/03/2018 à 19:51, am_d...@fastmail.fm a écrit :
> > > Hello,
> > > I noticed that the shortcut to switch between panels in a popup 
> > > (Control+Alt+Tab is unbound in Debian in the latest testing. I was not 
> > > sure if this was done for some reason or if this might be a bug? It seems 
> > > bound in other Linux's but maybe it conflicts with something I am not 
> > > aware of in Debian. I tried to look around a bit but couldn't find anyone 
> > > speaking about this in previous discussions.
> > > 
> > 
> > Hello am_dxer,
> > 
> > A fix for this bug has been pushed to Debian Sid this week. You'll see 
> > it in the next week on Debian testing. Another fix has been made for 
> > ctrl+alt+tab to work correctly but I'm not sure if a release with the 
> > fix has been publish yet.
> > 
> > More details here: https://github.com/mate-desktop/marco/issues/118
> > 
> > Best regards,
> > Alex.
> > 
> 

Re: Mate Upstream Keyboard Shortcuts Unbound in Debian

[am_dxer]

Hi,
>From the bug you sent, I was able to determine where the keyboard shortcuts 
>are being overridden in Debian. See 
>https://anonscm.debian.org/git/pkg-mate/mate-desktop-environment.git/tree/debian/10_mate-common.gschema.override.
Looking at that file, we can see this. switch-windows-all='Tab'
On a ifferent Linux distrobution that is using vanilla mate, we can see this 
through gsettings.

gsettings get org.mate.Marco.global-keybindings switch-windows-all
'disabled'

gsettings get org.mate.Marco.global-keybindings switch-panels
'Tab'

So it appears Debian is reassigning the keyboard shortcut Control+Alt+Tab from 
switch-panels to switch-windows-all. This is in the master branch of packaging 
so I don't think there is a change for this in Sid. I know that we have some 
Debian Mate maintainers that are also upstream Mate developers so maybe if this 
is desired for some reason, it could be pushed upstream instead. I just think 
it helps everyone's sanity if we can keep keyboard shortcuts consistant across 
distrobutions if possible.

On Sat, Mar 10, 2018, at 2:16 AM, Alex ARNAUD wrote:
> Le 09/03/2018 à 19:51, am_d...@fastmail.fm a écrit :
> > Hello,
> > I noticed that the shortcut to switch between panels in a popup 
> > (Control+Alt+Tab is unbound in Debian in the latest testing. I was not sure 
> > if this was done for some reason or if this might be a bug? It seems bound 
> > in other Linux's but maybe it conflicts with something I am not aware of in 
> > Debian. I tried to look around a bit but couldn't find anyone speaking 
> > about this in previous discussions.
> > 
> 
> Hello am_dxer,
> 
> A fix for this bug has been pushed to Debian Sid this week. You'll see 
> it in the next week on Debian testing. Another fix has been made for 
> ctrl+alt+tab to work correctly but I'm not sure if a release with the 
> fix has been publish yet.
> 
> More details here: https://github.com/mate-desktop/marco/issues/118
> 
> Best regards,
> Alex.
> 

Mate Upstream Keyboard Shortcuts Unbound in Debian

[am_dxer]

Hello,
I noticed that the shortcut to switch between panels in a popup 
(Control+Alt+Tab is unbound in Debian in the latest testing. I was not sure if 
this was done for some reason or if this might be a bug? It seems bound in 
other Linux's but maybe it conflicts with something I am not aware of in 
Debian. I tried to look around a bit but couldn't find anyone speaking about 
this in previous discussions.

Re: Firefox from Debian Experimental repo not funcioning correctly with Orca but same version from Mozilla prebuilt functions correctly

[am_dxer]

I should add that I was running the Firefox 57 Beta from Experimental
previously so the problem occurred with the upgrade to 58.

On Fri, Nov 24, 2017, at 11:21 AM, am_d...@fastmail.fm wrote:
> I noticed that when launchin Firefox 58 from the Debian experimental
> repo, Orca only says "frame" and does not speak any other information.
> When I download a prebuilt version of Firefox 58 Beta 4 from Mozilla, it
> functions correctly with Orca. I was just wondering if anyone else can
> reproduce this. I am running an up to date version of Buster as of the
> time I am sending this message.
> 

Firefox from Debian Experimental repo not funcioning correctly with Orca but same version from Mozilla prebuilt functions correctly

[am_dxer]

I noticed that when launchin Firefox 58 from the Debian experimental
repo, Orca only says "frame" and does not speak any other information.
When I download a prebuilt version of Firefox 58 Beta 4 from Mozilla, it
functions correctly with Orca. I was just wondering if anyone else can
reproduce this. I am running an up to date version of Buster as of the
time I am sending this message.

Re: Sound Parameters on Net Installer? Need speech for accessibility

[am_dxer]

On Thu, Oct 12, 2017, at 07:24 PM, Samuel Thibault wrote:
> Hello,
> 
> am_d...@fastmail.fm, on mar. 10 oct. 2017 10:32:19 -0400, wrote:
> > I have found that for some reason the Debian sound board selector prompt
> > does not work on some Broadwell machines.
> 
> Ok.
> 
> > I copied the asound.conf generated by the Arch Linux sound board
> > selector to a flash drive and used that to do my Debian install.
> 
> And did it work?
> 
I was able to use the arch asound.conf to do the install once I coppied
it to the running debian installer and restarted espeakup
The card that emits sound is the one called   1 [PCH]:
HDA-Intel - HDA Intel PCH
> > It would be interesting to know what Arch is doing differently.
> 
> I had a look at the scripts Jude pointed to, they use very different
> approaches to enumerating devices, so just comparing won't provide
> hints.
> 
> Could you report what is requested on
> 
> https://wiki.debian.org/accessibility#Debian_installer_accessibility
> 
> from your Broadwell system so we have better insight as to what it looks
> like in there?
cat /proc/asound/cards
  0 [HDMI   ]: HDA-Intel - HDA Intel HDMI
   HDA Intel HDMI at 0xf121 irq 50
  1 [PCH]: HDA-Intel - HDA Intel PCH
   HDA Intel PCH at 0xf1214000 irq 49
29 [ThinkPadEC ]: ThinkPad EC - ThinkPad Console Audio Control
   ThinkPad Console Audio Control at EC reg 0x30, fw 
unknown

cat /sys/class/sound/card*/id
HDMI
PCH
ThinkPadEC
> 
> Without such kind of information, I'm just unable to do anything about
> the issue.
> 
> Samuel
> 

Re: Sound Parameters on Net Installer? Need speech for accessibility

[am_dxer]

On Tue, Oct 10, 2017, at 10:32 AM, am_d...@fastmail.fm wrote:
> 
> 
> On Wed, Oct 4, 2017, at 10:08 AM, Samuel Thibault wrote:
> > Hello,
> > 
> > Dave Hunt, on mer. 04 oct. 2017 09:56:56 -0400, wrote:
> > > I am trying to get software speech to work on the Stretch net installer, 
> > > on
> > > a machine having multiple sound output possibilities.  When typing 's', 
> > > and
> > > pressing enter, at the boot prompt/beep, I am expecting spoken prompts for
> > > the installer, but get silence, except for the beeping boot prompt.
> > 
> > Normally the debian installer loops over all sound boards it finds, to
> > prompt the user for which one he wants to use. If that doesn't work it
> > means there is a problem with the driver of your board. It's no use
> > trying to force using a given device: it already does so for each board
> > which was discovered.
> > 
> > So unfortunately it's most probably a bug in sound drivers, and more
> > information is needed to determine how to fix it, see
> > https://wiki.debian.org/accessibility#Debian_installer_accessibility
> > for the amixer commands to get output of, and the content of
> > /proc/asound/cards. Perhaps you can do so from some other image with
> > which sound does work, be it knoppix adriane or such.
> > 
> > Samuel
> > 
> I have found that for some reason the Debian sound board selector prompt
> does not work on some Broadwell machines. Dave has a Broadwell machine
> so I think this might be the problem. It seems to default to the HDMI
> output and not loop to the Intel HD Audio card connected to the internal
> speakers. I am not sure what is different, however, the sound board
> selector on the Arch Linux live cd works with these Broadwell machines.
> I copied the asound.conf generated by the Arch Linux sound board
> selector to a flash drive and used that to do my Debian install. I
> copied it to /etc and then restarted the espeakup process from one of
> the extra terminals available when the Debian installer was booted. I
> used a braille display for this task. It would be interesting to know
> what Arch is doing differently. I don't know a lot about Alsa but maybe
> someone with more knowledge in this area might have some ideas.
> 
The script Arch Linux is using for picking cards can be found here.
Maybe someone who understands Alsa might be able to help with knowing
what this script and the one in Debian are doing differently.
https://notabug.org/TalkingArch/TalkingArch/src/master/configs/talking-inst/airootfs/usr/bin/pick-a-card

Re: Sound Parameters on Net Installer? Need speech for accessibility

[am_dxer]

On Wed, Oct 4, 2017, at 10:08 AM, Samuel Thibault wrote:
> Hello,
> 
> Dave Hunt, on mer. 04 oct. 2017 09:56:56 -0400, wrote:
> > I am trying to get software speech to work on the Stretch net installer, on
> > a machine having multiple sound output possibilities.  When typing 's', and
> > pressing enter, at the boot prompt/beep, I am expecting spoken prompts for
> > the installer, but get silence, except for the beeping boot prompt.
> 
> Normally the debian installer loops over all sound boards it finds, to
> prompt the user for which one he wants to use. If that doesn't work it
> means there is a problem with the driver of your board. It's no use
> trying to force using a given device: it already does so for each board
> which was discovered.
> 
> So unfortunately it's most probably a bug in sound drivers, and more
> information is needed to determine how to fix it, see
> https://wiki.debian.org/accessibility#Debian_installer_accessibility
> for the amixer commands to get output of, and the content of
> /proc/asound/cards. Perhaps you can do so from some other image with
> which sound does work, be it knoppix adriane or such.
> 
> Samuel
> 
I have found that for some reason the Debian sound board selector prompt
does not work on some Broadwell machines. Dave has a Broadwell machine
so I think this might be the problem. It seems to default to the HDMI
output and not loop to the Intel HD Audio card connected to the internal
speakers. I am not sure what is different, however, the sound board
selector on the Arch Linux live cd works with these Broadwell machines.
I copied the asound.conf generated by the Arch Linux sound board
selector to a flash drive and used that to do my Debian install. I
copied it to /etc and then restarted the espeakup process from one of
the extra terminals available when the Debian installer was booted. I
used a braille display for this task. It would be interesting to know
what Arch is doing differently. I don't know a lot about Alsa but maybe
someone with more knowledge in this area might have some ideas.

Re: Overlapping speech with brltty and espeak-ng again

[am_dxer]

I was able to reproduce this as well when using RC4 of the Debian
Installer for Stretch when using the s option from the boot menu. I
found that I was not always able to interrupt speech with a keyboard
command. When the speech finally stopped, it seemed to repeat different
parts of the phrase. Its quite hard to describe. When i go back to the
rc3 version of the stretch installer, speech does not overlap.

On Wed, May 24, 2017, at 11:46 AM, Eric Scheibler wrote:
> Hello Samuel,
> 
> Samuel Thibault  schrieb am 24.05.2017, 17:16
> +0200:
> >Eric Scheibler, on mer. 24 mai 2017 10:53:30 +0200, wrote:
> >> But yesterday I've updated my system and installed espeak version
> >> 1.49.0+dfsg-10 and now it's as bad as described in bug #848016 again.
> >
> >Just to make sure, could you try to downgrade to 1.49.0+dfsg-9 to check
> >whether the changes in -10 bring a difference here?
> 
> I already did that and yes, I think, -10 made it a bit worse. At least
> I've adapted to the
> overlapping of -7 over time and recognized a difference after the system
> upgrade from yesterday. But
> -9 is still bad, compared to the situation with the killed speech
> dispatcher (see following email).
> 
> Cheers
> Eric
> 

Re: wireless configuration

[am_dxer]

On Tue, May 16, 2017, at 05:11 AM, Alex ARNAUD wrote:
> Hello Mark,
> 
> I use the Mate wireless icon from the top panel.
> To access it you can do those steps :
> 1) control+alt+tab until you hear top panel (or something like that, I'm 
> in French locale)
> 2) Do shift+tab until you hear network : it's between battery and sound
> 3) Press enter on it and after use the list with down arrow
Hi,
One thing to be aware of with this when using testing is that if you
install over an ipv6 network, network-manager does not get installed.
This is because rdnssd is installed when the installer senses it is on
an ipv6 network and the rdnssd package conflicts with network-manager.
To resolve this, install packages network-manager and
network-manager-gnome after install. Apt will tell you that it is going
to remove rdnssd.

Re: Speech Dispatcher cutting off the end of phrases while using Flite

[am_dxer]

On Tue, Feb 21, 2017, at 05:06 PM, Luke Yelavich wrote:

> Ok, what audio output are you using in Speech Dispatcher? Pulseaudio is
> the 
> default, so if you haven't changed the configuration for the audio
> output, 
> that is what you would be using.
I am using Pulseaudio.
> 
> Have you tried using any other software that makes use of flite? If so,
> do 
> you experience the same problem?
> 
I have not tried any other software that uses Flite, however, I would be
willing to test something if it would help with troubleshooting.
> Luke
> 

Firefox-ESR Crash in Stretch when exiting Browser with Orca running

[am_dxer]

Hello,
I have all the latest packages installed for the testing release. I
notice that almost every time I close firefox-esr, I get a message that
it has crashed. I guess I am not sure if this is an accessibility
related issue. The reason I think it might be is because if these
crashes were happening without Orca running, many other users would have
noticed it. The test case that i have is to just open Firefox and close
it. This seems to cause a crash in most cases for me with a resulting
dialog asking if I want to send crash results to Mozilla. If I use the
Firefox package from experimental, the crashes are gone. I thought it
might be interesting to see if any Orca users can reproduce this and if
any sighted users can confirm whether the crash occurs when Orca is off.
I can reproduce on both an AMD and Intel machine. Thanks

Re: Speech Dispatcher cutting off the end of phrases while using Flite

[am_dxer]

On Mon, Feb 20, 2017, at 04:34 PM, Luke Yelavich wrote:

> Mind telling us what Orca version and what Speech Dispatcher version?
> Maybe 
> the version of flite is relevant too. Do you experience this with espeak
> or 
> espeak-ng?
Hello,
I am using stretch so speech dispatcher 0.8.6-3 and flite
(2.0.0-release-3). The orca version is (3.22.2-2. I don't have problems
with speech being cut off when using espeak-ng. Also, I observe this
behavior on an AMD and Intel machine. On both machines, espeak-ng works
fine but flite speech is cut off. Thanks.

Speech Dispatcher cutting off the end of phrases while using Flite

[am_dxer]

Hello,
I notice that while using Orca with Speech Dispatcher and Flite, the end
of most phrases are cut off. It usually cuts off the second half of the
last word spoken. I was just wondering if anyone has noticed this before
and knows of a fix if one exists. Thanks.

Re: No sound From Orca after a Strech Install

[am_dxer]

On Sun, Jan 22, 2017, at 11:47 AM, Samuel Thibault wrote:
> Hello,
> 
> am_d...@fastmail.fm, on Sun 22 Jan 2017 11:22:54 -0500, wrote:
> > In the Stretch install, the HDMI sound device was selected as the
> > default device in the Mate Control Panel on both laptops.
> 
> Mmm, I'm afraid it might be the same kind of issue as I had.
> 
> I've put in /etc/modprobe.d/perso.conf this:
> 
> options snd-hda-intel index=1,0
> 
> which exchanges the two cards, so HDMI comes second. Otherwise I don't
> get any output through pulseaudio.
> 
> Samuel
Hello,
Thanks for your suggestions. I tried that and it didn't turn out to be
the problem, however, it did prevent me from having to change hdmi to
internal speakers and listed the speakers as the first device in sound
prefs so it is a great help. I did find a solution to my problem. In the
Orca preferences by changing the option from default speech synthesizer
to espeak-ng on the Voice tab things work properly. I think that for
some reason, on my hardware, no speech synthesizer is selected by
default. Can you reproduce this with a fresh install on your hardware?
Thanks.

No sound From Orca after a Strech Install

[am_dxer]

Hello,
I recently installed Stretch on two test laptops (both amd) and had no
speech from Orca after install, however, braille does work fine with
Orca and in the console and Speakup talks fine as well. I used the
non-free rc1 image because the wireless cards in both machines require
firmware. One thing worth noting is that speakup stopped talking at
different points of both installations and I had to finish the installs
using only braille. During the first install, speakup crashed at the
detecting networking hardware step and in the second install, it crashed
when starting the partitioner. On both machines. With Debian stable,
speech from Orca works correctly so I guess this is a regression from
the previous release of Debian. Speakup also does not crash when
installing Debian stable on these machines. In the Stretch install, the
HDMI sound device was selected as the default device in the Mate Control
Panel on both laptops. After changing this to my internal sound card
using braille, I was able to record and play sound as well as use other
applications like espeak from the Mate Terminal and I heard sound
through my speakers, however, I could not get orca to talk.
I tried some troubleshooting steps without success to fix this issue.
1. I first tried using spd-say to play speech using speech dispatcher
directly and that did not work.
2. I tried restarting the Pulseaudio process as well as the computer.
Another thing that I tried was deleting the ~/.config/pulse folder.
3. I tried running spd-conf and I got an error when running this so as a
workaround, I copied /etc/speech-dispatcher to
~/.config/speech-dispatcher. After this, I changed the default audio
device from pulse to libao in speechd.conf and restarted the speech
dispatcher process and the computer and still could not get sound to
work.

I am at a loss now of other things to try and was wondering if anyone
else has had these issues. I have a laptop that is Intel that is
available for testing so will try that later today. The two laptops that
I tried were both HP pavilions. One had an AMD processor from the 15h
series, the other had a 16h series processor. The laptop I will use for
testing this afternoon has a core 2 duo processor. Any advice or
suggestions are appreciated.
Thanks.

solution to the problem of orca and gecko not working in non-gnome environment

[am_dxer]

In my XFCE environment, It appears that the problem is occurring from a
Gtk module import path issue. I coppied the
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules directory to /usr/lib/gtk-2.0
and things work for me in the Mozilla apps.


-- 
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1394384383.31203.92360033.63a56...@webmail.messagingengine.com

Re: solution to the problem of orca and gecko not working in non-gnome environment

[am_dxer]

On Sun, Mar 9, 2014, at 07:21 PM, Cyril Brulebois wrote:
 Jason White ja...@jasonjgw.net (2014-03-10):
  I think I've found it with a quick search of the Mozilla repository.
  mozilla/accessible/src/atk/Platform.cpp, line 81:
  
  81 #if defined(LINUX)  defined(__x86_64__)
  82 libPath.Append(:/usr/lib64:/usr/lib);
  
  If you change line 82 to
  libPath.Append(:/usr/lib64:/usr/lib:/usr/lib/x86_64-linux-gnu);
  and rebuild Mozilla, it might work.
 
 I think that's a very good catch indeed. There are a few other places
 where one can find /usr/lib in *.ccp files in iceweasel, but most of
 them are debug directories, or paths below /usr/lib/mozilla/.
 
 I suspect it would be nice to have a placeholder/#define somewhere so
 that the proper multiarch directory can be injected from debian/rules;
 depending on how easily I can reproduce the issue, I'll try and get a
 working patch and submit the bug report against iceweasel.
 
I appreciate all the helpful replies so far. The thing that seems so
puzzling to me is why this problem does not occur when running in gnome
shell.


-- 
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1394408040.12662.92454065.4a116...@webmail.messagingengine.com

My experience and some issues with the accessibility of the Jessie/testing desktop

[am_dxer]

I did an install of Jessie today from one of the netboot images. I did
an install of the xfce desktop and lightdm display manager which I
believe is the default at this point. I know that from prior experience,
by default, xfce doesn't load the accessibility modules for gtk but they
can either be sourced in a profile or there is a checkbox in the
accessibility settings for xfce that loads the modules. I chose to check
the accessibility box as I know from prior experience that this works
reliably. If XFCE does get chosen as the default desktop, I wonder if
checking this box could be part of the accessibility profile in the
installer for Debian if the desktop task is chosen. I know that this can
be done on the command line using xfconf. After I restarted the machine,
I got the expected level of accessibility from XFCE. For those who don't
know, the current state of accessibility in XFCE allows one to read the
menus and some of the programs that are included with the desktop.
Currently the panel is completely inaccessible with Orca. Thunar (XFCE's
file manager) has some accessibility issues that prevent access to the
desktop but if you replace this with pcmanfm from the lxde desktop, you
will find these are resolved as of the new version that was released a
few weeks ago. All the things I have described so far are upstream and
are not related specifically to Debian. One problem I have found that I
have only seen in debian is inaccessibility of the mozilla apps in a
non-gnome environment. I tried Iceweasel from the Debian repositories.
When this would not work, I tried downloading a precompiled version from
the Mozilla site and orca still wouldn't talk. It appears orca is not
even seeing the application because when using orca -l which gives a
list of application orca sees, the Mozilla apps are not listed at all.
It appears that others are having a similar issue see
https://bugzilla.mozilla.org/show_bug.cgi?id=956684. One of the things
mentioned in this bug report is that Mozilla apps check for an
accessibility value using dbus to enable their accessibility. I checked
this value in my environment and the value was set to true. I wonder if
the issue could be related since ubuntu is downstream from debian. I
have not had this issue in Gentoo or Arch with XFCE so I guess at this
point, a next step would be to figure out what is different in the
Debian environment. I will do some poking around in my Gentoo, Arch, and
Debian environments and see if I can spot some differences but I thought
at least posting this hear could maybe help determine if others are
having this issue, and make others aware. I will also install a full
Gnome environment on Debian to see if I can get Mozilla apps talking
there. Any advice related to this issue would be greatly appreciated.


-- 
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1394305195.29552.92144285.22d9e...@webmail.messagingengine.com

Re: My experience and some issues with the accessibility of the Jessie/testing desktop

[am_dxer]

On Sat, Mar 8, 2014, at 02:23 PM, Samuel Thibault wrote:
 Hello,
 
 am_d...@fastmail.fm, le Sat 08 Mar 2014 13:59:55 -0500, a écrit :
  If XFCE does get chosen as the default desktop, I wonder if
  checking this box could be part of the accessibility profile in the
  installer for Debian if the desktop task is chosen.
 
 Most probably.
 
  I know that this can be done on the command line using xfconf.
 
 Could you determine the precise command line and tell us, so we can
 include it in the installer scripts?
The exact command is xfconf-query -c xfce4-session -p
/general/StartAssistiveTechnologies -n -t bool -s true. XFCE stores it
settings in categories called channels and each setting is called a
property. In this command, c specifies the channel, p specifies the
property, -s sets the property, -t specifies the type of the property
and n specifies to create a new property. The property actually is not
created in xfce's configs until the box is checked in the gui (if it
does not exist xfce assumes it is false)  which is why we have to create
it in the command as opposed to just changing its value. One problem I
found with this method, however, is that if trying to run without x
going, the following error is displayed. Failed to init libxfconf:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11. One way
to possibly get around this would be to set the property manually in xml
files since this is how xfce stores the settings. they are stored at
~/.config/xfce4/xfconf/xfce-perchannel-xml. The file is called
xfce4-settings and the property is set like this in the general category
in the file.
property name=StartAssistiveTechnologies type=bool value=true/


 
 Samuel


--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1394310295.12164.92162009.07db2...@webmail.messagingengine.com

Re: My experience and some issues with the accessibility of the Jessie/testing desktop

[am_dxer]

On Sat, Mar 8, 2014, at 02:23 PM, Samuel Thibault wrote:
 Hello,
 
 am_d...@fastmail.fm, le Sat 08 Mar 2014 13:59:55 -0500, a écrit :
  If XFCE does get chosen as the default desktop, I wonder if
  checking this box could be part of the accessibility profile in the
  installer for Debian if the desktop task is chosen.
 
 Most probably.
 
  I know that this can be done on the command line using xfconf.
 
 Could you determine the precise command line and tell us, so we can
 include it in the installer scripts?
I have one correction. The file where the xml is stored is actually
called xfce4-session not xfce4-settings. Sorry for this error.

 
 Samuel


--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1394310816.13726.92167641.5e34d...@webmail.messagingengine.com

Re: My experience and some issues with the accessibility of the Jessie/testing desktop

[am_dxer]

On Sat, Mar 8, 2014, at 03:44 PM, Cyril Brulebois wrote:
 am_d...@fastmail.fm am_d...@fastmail.fm (2014-03-08):
  On Sat, Mar 8, 2014, at 02:23 PM, Samuel Thibault wrote:
   Hello,
   
   am_d...@fastmail.fm, le Sat 08 Mar 2014 13:59:55 -0500, a écrit :
If XFCE does get chosen as the default desktop, I wonder if
checking this box could be part of the accessibility profile in the
installer for Debian if the desktop task is chosen.
   
   Most probably.
   
I know that this can be done on the command line using xfconf.
   
   Could you determine the precise command line and tell us, so we can
   include it in the installer scripts?
  I have one correction. The file where the xml is stored is actually
  called xfce4-session not xfce4-settings. Sorry for this error.
 
 Thanks for the details.
 
 I seem to remember we have a D-Bus session running when installing with
 accessibility enabled, so it should be possible to run D-Bus-demanding
 things.
 
 I was very happy to receive this sort of very detailed mail; I was
 precisely wondering what the accessibility status was, since we're
 aiming at publishing images very soon.
 
I had a chance to pull in the entire Gnome session a little while ago on
my Debian testing system. In this configuration Orca reads Mozilla
applications. I guess now that we know that Orca will read these
applications in a full Gnome environment the puzzle to solve is why they
are not reading in XFCE in Debian but are reading in XFCE in other
distros. It also seems possible to me that the issue is not related to
xfce directly since the ubuntu bug report mentions this not working in
LXDE either. If anyone has any insight on this it would be greatly
appreciated.


--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/1394336225.24093.92238385.27635...@webmail.messagingengine.com

Re: problem with speech in latest debian installer dailies

[am_dxer]

On Sun, Feb 23, 2014, at 11:27 PM, am_d...@fastmail.fm wrote:
 I tried to install debian testing today using the installer images. I
 grabbed the latest amd64 image and got no speech after I started the
 installation with s and then enter from the boot menu.. I asked someone
 sighted what was going on and they said that there was a bar going back
 and forth at the bottom of the screen like something was loading. I left
 this go for a minute or so and nothing happened. According to them, the
 gui installer worked just fine when I selected that from the menu. I
 also tried a weekly image and got no speech. Can anyone else reproduce
 this?

I have done some more testing this morning. I booted the installer with
a braille display connected. The message showed on the braille display
that brltty was starting and then the display went blank. As a
troubleshooting step, I went to another terminal and killed the espeakup
process. As soon as I returned to the installer on tty 1, braille was
working and a message showed on the display that localization had failed
and that I could press enter to continue which took me to the main menu.
I didn't do an install past this point but when I selected a few menu
items they seemed to load normally. Please let me know if there is any
other information that I can provide that would assist with tracking
this down.


-- 
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1393245497.15248.87061329.471e0...@webmail.messagingengine.com

Re: problem with speech in latest debian installer dailies

[am_dxer]

Thank you very much for your quick and helpful reply. I tried the
following image and speech as well as braille worked.
http://ftp.fr.debian.org/debian/dists/sid/main/installer-amd64/20140208/images/netboot/mini.iso
The image that I tried this morning where speech was not working is
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso
The date from this iso was 2014-02-24 05:04 as I tried a newer build
from today when I did the testing in my second message. IF there is any
more info that I could provide that would be helpful let me know.


-- 
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1393253303.15718.87103009.60a60...@webmail.messagingengine.com

Re: problem with speech in latest debian installer dailies

[am_dxer]

I apologize for this mix up. The working iso was actually
http://ftp.fr.debian.org/debian/dists/sid/main/installer-amd64/20140208/images/netboot/gtk/mini.iso.
I read somewhere that speech was only on the gtk cd's which is why I
used that image although I could be wrong about this as I read it a
while ago and things might have changed.


-- 
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1393253950.19277.87114621.7310e...@webmail.messagingengine.com

Re: problem with speech in latest debian installer dailies

[am_dxer]

I did some testing of the daily builds from d-i.debian.org. It appears
that the first one that is broken as far as speech is concerned is
http://d-i.debian.org/daily-images/amd64/20140209-00:16/netboot/gtk/mini.iso
I hope this might help narrow down where the bug was introduced. One
thing that I also noticed is that a few of the gtk images before this
one failed to build, however, the last successful build before the
failed builds did have working speech. 


-- 
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1393261104.20666.87168753.2dd92...@webmail.messagingengine.com

Re: problem with speech in latest debian installer dailies

[am_dxer]

On Mon, Feb 24, 2014, at 01:21 PM, Cyril Brulebois wrote:
 Cyril Brulebois k...@debian.org (2014-02-24):
  So if 20140207-00:17 works and 20140209-00:16 doesn't, here's the diff of 
  udeb.list:
  
  “pure” d-i side:
  -di-utils 1.102 amd64
  -di-utils-reboot 1.102 all
  -di-utils-shell 1.102 all
  -di-utils-terminfo 1.102 amd64
  +di-utils 1.103 amd64
  +di-utils-reboot 1.103 all
  +di-utils-shell 1.103 all
  +di-utils-terminfo 1.103 amd64
  
  This change is included in that debian-installer-utils update:

  http://anonscm.debian.org/gitweb/?p=d-i/debian-installer-utils.git;a=commit;h=9c6685364a56697ea9c590e1bc93a73ade88b679
  
  and I suspect it might have to do with the hang. I'll try to debug
  that in the upcoming hour(s).
 
 Confirmed, and now tracked here:
   http://bugs.debian.org/739989
 
 Thanks for reporting! (And for bisecting, it saved me a lot of testing

Thanks to you and everyone on this list who work on accessibility. These
tools are used by a small minority of people but I think I can speak for
everyone that uses them that the time that is spent ensuring that they
function is greatly appreciated!


--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1393286148.15582.87340753.10d66...@webmail.messagingengine.com

problem with speech in latest debian installer dailies

[am_dxer]

I tried to install debian testing today using the installer images. I
grabbed the latest amd64 image and got no speech after I started the
installation with s and then enter from the boot menu.. I asked someone
sighted what was going on and they said that there was a bar going back
and forth at the bottom of the screen like something was loading. I left
this go for a minute or so and nothing happened. According to them, the
gui installer worked just fine when I selected that from the menu. I
also tried a weekly image and got no speech. Can anyone else reproduce
this?


-- 
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1393216021.6661.86935985.762fb...@webmail.messagingengine.com

orca dependency problems wheezy

[am_dxer]

I installed debian wheezy with the talking installer and everything went
fine. However, when I installed orca with apt, I noticed that apt wanted
to auto-remove libgail-common and without this package, some things in
orca are broken. The old at-spi package depended on libgail-common but
seems to have been replaced by libatk-adaptor which provides a virtual
package for at-spi. Should libatk-adaptor or maybe a similar package
have a dependency for libgail-common? I am not an expert of linux by any
means which is why I didn't want to file any sort of bug report. The
solution I gave is simply my best guess based on what I know. I figured
I'd ask the opinion of the list to determine what the solution to this
problem might be or if I am simply doing something wrong.


-- 
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/1340971001.12209.140661095652525.6a44c...@webmail.messagingengine.com