Re: Amazon and console browsers

[Chevelle]

    I just used 'w3m' to do a search on Amazon by typing 'w3m 
https://amazon.com'.  I didn't go through the buying process.  I'm not 
sure when you hit the CAPTCHA.  Jason makes some good points.




On 11/23/23 12:48, Jason J.G. White wrote:


On 23/11/23 12:16, David J. J. Ring, Jr. wrote:
CAPTCHA of Amazon can be heard?
If not, is there a way of configuring mplayer or other program to 
play the CAPTCHA?


I'm not aware of any, and I would expect Amazon to be so 
Javascript-dependent these days that you wouldn't be able to use the 
site effectively without a browser that supports Javascript, DOM, and 
all of the associated APIs. Your only option might be to find a 
"mobile" version that perhaps isn't Javascript-dependent.


I gave up on console-based browsers a long time ago, as Javascript was 
increasingly becoming a necessity, and ARIA was solving its 
accessibility problems.

Re: Noobie questions about installing Debian for blind user

[Chevelle]

    You can use Rufus to create a bootable USB drive from Windows. I 
last installed the Debian Bookworm by downloading it from www.debian.org.


I would use the latest Bookworm installer.  If the PC has a speaker, you 
should hear a beep.  Then you can type 's' to start Speakup.

There is an FAQ at:
https://wiki.debian.org/accessibility
For a serial Braille display you have to mannually add a line to the 
/etc/brltty.conf like this:

braille-device ttyUSB0
You probably can't do that until after the system is installed.




On 10/18/23 21:19, Susan Fowle wrote:
My blind husband, Tom, has used very old Debian version Jessie on a 
very old machine for many years. Something finally broke or got corrupted.


So we are planning to buy a new small computer (Kingdel Desktop 
Computer, Intel i5 CPU, 8GB RAM 256GB SSD, Intel HD Graphics 4400, 
6xCOM RS232).


We plan to install Debian 12 stable (or possibly 11 if that turns out 
to be better for our needs). I mainly use Windows, but have done a bit 
of reading about Debian, and sometimes use the Raspberry Pi OS on a Pi 
3 and a netbook.


Tom wants Debian to boot into the console/terminal, and plans to use 
GUI only for occasional web browsing. He uses a DoubleTalk speech 
synthesizer and Speakup, plus an Alva braille terminal -- the hardware 
requires COM ports, hence our choice of computer. He uses Mutt for 
email and text browsers Lynx, Links, etc.


What is the best way to start? debian-live-12.2.0-amd64-gnome.iso?  
Something else -- jigdo?


Tom will want to hear what's happening during installation. Will the 
live version provide that option?


We have a copy on a flash drive of the data from the older machine 
(everything under /home). What is the best way of re-installing all 
this personal data after the system has been installed?


Are these types of questions answered on a web page somewhere, so I 
don't need to bother you good folks unless we run into problems?


Thanks very much,

Sue and Tom Fowle

Re: [orca] Re: Braille navigation issues with Orca 44.1

[Chevelle]

    Thanks Samuel.  The ORCA Debian package only has xbrlapi as 
Reccomends.  There doesn't seem to be any warning by ORCA so if xbrlapi 
isn't installed the unsuspecting user has a Braille display that doesn't 
work properly.  Should xbrlapi be a depends instead?



On 9/4/23 18:08, Samuel Thibault wrote:

Samuel Thibault, le lun. 04 sept. 2023 22:59:05 +0200, a ecrit:

I'm on it.

So, as usual it's the combination of two issues that were producing the
odd behavior.

What was happening is that with xbrlapi installed but brltty-x11 not
installed, the xbrlapi startup script would try to run brltty with the
BrlAPI braille driver and the AtSpi2 screen driver, but the latter
wouldn't load, so brltty would fallback to the "no" screen driver. But
that driver was not telling the BrlAPI braille driver that it cannot do
much, on the contrary it would tell that it works really well, better
than Orca, and thus the BrlAPI braille driver would consume most BrlAPI
keypresses. With the AtSpi2 driver installed, it knows to tell exactly
when it has good support (e.g. in terminals).

It happens that upgrading xbrlapi fixed this because in the newer
version the xbrlapi startup script checks that both the BrlAPI and the
AtSpi2 drivers are available, and not start that brltty in that case.

So, long story short:

https://github.com/brltty/brltty/pull/428

and I'll backport some fixes to bookworm.

Samuel
___
orca mailing list
o...@freelists.org
https://www.freelists.org/list/orca
Orca wiki: https://wiki.gnome.org/Projects/Orca
Orca documentation: https://help.gnome.org/users/orca/stable/
GNOME Universal Access guide: 
https://help.gnome.org/users/gnome-help/stable/a11y.html

Re: espeakup stops speaking bookworm arm64

[Chevelle]

    I'm using AMD64, but sometimes I can find the PID for 
pipewire-pulse with 'ps ax'.  Then enter

kill -SIGHUP 
Suddenly it will start working again.
It might be worth a try.


On 8/28/23 05:46, Geoff Shang wrote:

On Mon, 24 Apr 2023, James Addison wrote:


Working towards a better backtrace is a good recommendation.  I'd also
like to mention that there are existing Debian bookworm debug symbol
packages available for both espeak and espeakup that can avoid the
need to recompile from source.

The packages are named 'espeak-dbgsym' and 'espeakup-dbgsym' and can
be installed after enabling the bookworm-debug APT repository.


I don't see espeakup-dbgsym in bookworm-debug.  I do see 
espeak-dbgsym, however espeakup does not depend on espeak, it depends 
on libespeak, actually libespeak-ng1.  There is also 
libespeak-ng1-dbgsym, but I'm not sure if espeakup would use it if I 
installed it.


Cheers,
Geoff.

Re: espeakup stops speaking bookworm arm64

[Chevelle]

    I have the AMD64 build of bookworm, but I have had it stop 
speaking.  Sometimes if I have a graphical session running, then switch 
to a speakup console, it is very slow to respond.  I wrote a simple bash 
script like this:


#!/usr/bin/bash

sleep 5

ls


I start that in the terminal with ORCA running then switch consoles to 
another session.  With that I can get some errors in the 'espeakup' 
debug log like this:


error: Device or resource busy
ALSA lib pcm_dmix.c:999:(snd_pcm_dmix_open) unable to open slave
error: Device or resource busy
ALSA lib pcm_dmix.c:999:(snd_pcm_dmix_open) unable to open slave
error: Device or resource busy
ALSA lib pcm_dmix.c:999:(snd_pcm_dmix_open) unable to open slave
error: Device or resource busy

Also if it is talking and you type something in the console you are in, 
it can't stop the speech.  Maybe I'm expecting to much, I'm not sure how 
it is designed to work.


Not sure if that helps.


On 8/18/23 12:39, Frank Carmickle wrote:

Greetings,

I've been living with this for the last sixish months, and it's annoying. I 
have a console where I can just up arrow and hit enter for

`killall -1 espeakup`

I would love to see this get fixed but I've gotten nowhere with debugging it.

I haven't tried Sam's recommendation of having a middle layer of pulseaudio or 
pipewire to keep the audio buffer always full with silence when it's not 
speaking. I spent so much time trying to get a working machine before, that 
I've not wanted to go back to work on it again for a bit. I'll probably get to 
it when the kids go back to school in a few weeks time.

I'll let you know if I find it to be of help.

--FC


On Aug 17, 2023, at 13:48, Geoff Shang  wrote:

Hello,

I just updated to Bookworm on my work VM running under VMWare 17 under Windows 
11 and am experiencing the same problem.

This was not happening under Bullseye.

The only other thing that I can add to what has already been described in this 
thread is that using conventional Debian methods to stop the espeakup process 
takes a long time.  Running espeakup in debug mode doesn't print anything to 
the console, and when I lose speech, I have to press control-backslash to kill 
it (control-c doesn't work).

I've only just seen the suggestion to test with the debug versions, which I 
will try at some point soon.

I'm running just in the console, no desktop environments.

BTW: I was just proofing this message and it died.  I was cursoring down 
through this email, so I wasn't reviewing by character this time.

Cheers,
Geoff.

Re: newer version of libatspi for Bookworm?

[Chevelle]

    Not trying to rush you Samuel, just curious.

Thanks for all your effort.


On 7/21/23 12:56, Samuel Thibault wrote:

Chevelle, le ven. 21 juil. 2023 10:51:53 -0400, a ecrit:

Is it possible libatspi2.48.3 or newer will make it to Bookworm or Bookworm
backports any time soon?

bookworm-backports has opened only today, and not even announced
officially, allow me the time to react :)

Samuel

newer version of libatspi for Bookworm?

[Chevelle]

    Hello,

Is it possible libatspi2.48.3 or newer will make it to Bookworm or 
Bookworm backports any time soon?


See below:

Thanks.




 Forwarded Message 
Subject:[orca] Re: Orca stopped speaking after distribution upgrade
Date:   Fri, 07 Jul 2023 19:19:27 +0200
From:   Joanmarie Diggs 
Reply-To:   o...@freelists.org
To: o...@freelists.org



Hi David.

I just use my package manager. I have 2.48.3.

In 2.48.1, at-spi2-core had these two relevant fixes:

* Fix crash when a bad index is passed to
atspi_accessible_get_child_at_index.
* Fix possible infinite recursion in atspi_accessible_clear_cache.

In 2.48.3, at-spi2-core had this relevant fix:

* Fix a couple of use after frees when finalizing devices.

Mike fixed those issues to solve some Orca hangs I reported.

Here's the tracker issue I'm using:
https://gitlab.gnome.org/GNOME/orca/-/issues/307

If your distro is not shipping at-spi2-core 2.48.3, perhaps point them
to that tracker issue and encourage them to update their package.

HTH.
--joanie

On Fri, 2023-07-07 at 09:48 -0700, David E. Price` wrote:

Hi, Joanie,

Is there a way to directly query the version? I couldn't find anything 
with a quick Google search.


Dpkg tells me that at-spi2-core and at-spi2-common are both 2.48.0-1.

Thanks,

dave

On 7/7/2023 1:30 AM, Joanmarie Diggs wrote:
> Hi David.
> > What version of AT-SPI2 do you have installed? There were some hangs
> (which would cause the symptoms you describe) that were recently fixed
> in AT-SPI2.
> > --joanie
> > On Thu, 2023-07-06 at 17:58 -0700, David E. Price` wrote:
> > Hi,
> > > > I installed the mate desktop with no change in behavior. I got 
exactly

> > the same debug output.
> > > > I guess I'm going to have to dig into the Orca source code to 
see if I

> > can figure this out. I see Orca on GitHub. Is that the best repository
> > to clone?
> > > > If I'm using gnome 44.2, are there any other projects I'd need 
to build

> > from source if I try to build master?
> > > > Thanks,
> > > > dave
> > > >  On 7/6/2023 6:42 AM, Chevelle wrote:
> > > Did you install Mate desktop?  You could login under a different
> > > session and test if ORCA will work.
> > > > > > > > > On 7/5/2023 8:03 PM, David E. Price` wrote:
> > > > Hi,
> > > > > > > > I finally got around to upgrading from Ubuntu 22.10 to 
Ubuntu 23.04,
> > > > and the result is that Orca will not speak after log in. It 
will speak

> > > > on the log in screen.
> > > > > > > > Versions:
> > > > orca: 44.0
> > > > gnome-shell: 44.2
> > > > > > > > I have a debug output with 32 lines, no errors, and 
the final line

> > > > says:
> > > > > > > > 15:00:20.948304 - ORCA: Launching version 44.0
> > > > > > > > When I type "orca -l" on the command line, I get a 
list of processes,

> > > > but orca does not appear in the list.
> > > > > > > > Espeak is working just fine--I have emacspeak running 
on the same

> > > > machine.
> > > > > > > > I tested speech dispatcher using spd-say, and I 
receive speech

> > > > feedback using espeak.
> > > > > > > > I logged the distribution upgrade, and the only 
warnings came from
> > > > cryptsetup because a swap device had changed its UUID. 
Installation of

> > > > the orca and speech dispatcher packages went off without a hitch.
> > > > > > > > I uninstalled and reinstalled the orca package with no 
change in

> > > > behavior.
> > > > > > > > I grepped in some of the system logs and could see 
nothing related to
> > > > orca. If there is a specific log I should check, please let me 
know.

> > > > > > > > Does anyone have ideas on what I should try next?
> > > > > > > > Thanks,
> > > > > > > > dave
> > > > > > > > ___
> > > > orca mailing list
> > > > o...@freelists.org
> > > > https://www.freelists.org/list/orca
> > > > Orca wiki: https://wiki.gnome.org/Projects/Orca
> > > > Orca documentation: https://help.gnome.org/users/orca/stable/
> > > > GNOME Universal Access guide:
> > > > https://help.gnome.org/users/gnome-help/stable/a11y.html
> > > > ___
> > orca mailing list
> > o...@freelists.org
> > https://www.freelists.org/list/orca
> &g

Re: Debian 12, Easiest Way to switch Between Already Installed Desktop Environments?

[Chevelle]

    When you are at the Login screen, try pressing the F10 key to get 
to the menu.  Then use your arrow keys to explore the menu.  I don't 
have two environments installed, but mine shows Mate currently.




On 7/5/2023 3:19 PM, Al Puzzuoli wrote:


Thanks,

That seems to be the issue though. I can’t find anything relevant in 
the login dialogue box that looks like it’s clickable. If the control 
does exist, It definitely doesn’t seem to be in the tab order. Can 
anyone confirm or suggest an alternate way to switch? I imagine 
modifying some config file or other would do the trick?


--Al

*From:* K0LNY 
*Sent:* Wednesday, July 5, 2023 2:26 PM
*To:* Al Puzzuoli 
*Subject:* Re: Debian 12, Easiest Way to switch Between Already 
Installed Desktop Environments?


I think it is a list selection, so if you land on a system or 
something, and it is closed,  open the list and arrow to the selection.


Glenn

- Original Message -

*From:*Al Puzzuoli 

*To:*debian-accessibility@lists.debian.org

*Sent:*Wednesday, July 5, 2023 1:12 PM

*Subject:*Debian 12, Easiest Way to switch Between Already
Installed Desktop Environments?

Hi all,

Curious what the best way is to switch between desktop
environments? My reading suggests that there’s some sort of icon
that you can click in the login window that will allow you to
select which desktop you want to use; However if I tab through the
dialog, I’m not seeing that icon. I tried reviewing the screen
with Orca and clicking a few possible objects that I thought could
be the icon but to no avail.

Thanks,

--Al

Re: Bookworm: BRLTTY constantly logs errors

[Chevelle]

    Yes, I use an old Alva.  I upgraded from Bullseye with the package 
manager.


Installing 'brltty-x11' did stop the errors.  Possibly the package was 
missing after I installed Bullseye, I don't know for sure.


Thanks!



On 6/16/23 11:13, Samuel Thibault wrote:

Hello,

Chevelle, le ven. 16 juin 2023 10:52:57 -0400, a ecrit:

I view the system log with 'journalctl -e' there are repeating errors.
Possibly it can't find yxa2.so.

Oops.

Are you actually using a braille device? If so, install the brlttyx11
package (and I wonder how it didn't get installed, how did you
install/upgrade your system?). Otherwise you can remove the xbrlapi
package, that'll avoid triggering brltty.

Samuel

Bookworm: BRLTTY constantly logs errors

[Chevelle]

I view the system log with 'journalctl -e' there are repeating errors.  
Possibly it can't find yxa2.so.


See attached log.

Do others see these errors?

Thanks.

Jun 16 10:43:06 m5 brltty[1496]: cannot load screen driver: 
/lib/brltty/libbrlttyxa2.so
Jun 16 10:43:06 m5 brltty[1496]: screen driver not loadable: a2
Jun 16 10:43:11 m5 brltty[1496]: /lib/brltty/libbrlttyxa2.so: cannot open 
shared object file: No such file or directory
Jun 16 10:43:11 m5 brltty[1496]: cannot load screen driver: 
/lib/brltty/libbrlttyxa2.so
Jun 16 10:43:11 m5 brltty[1496]: screen driver not loadable: a2
Jun 16 10:43:16 m5 brltty[1496]: /lib/brltty/libbrlttyxa2.so: cannot open 
shared object file: No such file or directory
Jun 16 10:43:16 m5 brltty[1496]: cannot load screen driver: 
/lib/brltty/libbrlttyxa2.so
Jun 16 10:43:16 m5 brltty[1496]: screen driver not loadable: a2
Jun 16 10:43:21 m5 brltty[1496]: /lib/brltty/libbrlttyxa2.so: cannot open 
shared object file: No such file or directory
Jun 16 10:43:21 m5 brltty[1496]: cannot load screen driver: 
/lib/brltty/libbrlttyxa2.so
Jun 16 10:43:21 m5 brltty[1496]: screen driver not loadable: a2
Jun 16 10:43:26 m5 brltty[1496]: /lib/brltty/libbrlttyxa2.so: cannot open 
shared object file: No such file or directory
Jun 16 10:43:26 m5 brltty[1496]: cannot load screen driver: 
/lib/brltty/libbrlttyxa2.so
Jun 16 10:43:26 m5 brltty[1496]: screen driver not loadable: a2
Jun 16 10:43:31 m5 brltty[1496]: /lib/brltty/libbrlttyxa2.so: cannot open 
shared object file: No such file or directory
Jun 16 10:43:31 m5 brltty[1496]: cannot load screen driver: 
/lib/brltty/libbrlttyxa2.so
Jun 16 10:43:31 m5 brltty[1496]: screen driver not loadable: a2

Re: BRLTTY on Debian Installer Bookworm Alpha 2 release

[Chevelle]

Sorry, the command was:

quickemu --vm debian.conf --braille --display sdl



On 2/23/2023 8:34 PM, Chevelle wrote:

I was using 'quickemu'.  I think I tried

quickemu --vm --braille --display sdl

I'm not sure from the instructions how it is supposed to work. Should 
'brltty' be running before we start the virtual machine, or not.  I 
searched around, but couldn't find clear instructions.


Thanks.


On 2/23/2023 7:35 PM, Samuel Thibault wrote:

Hello,

Chevelle, le lun. 20 févr. 2023 21:46:46 -0500, a ecrit:
update-rc.d: Warning: start and stop actions are no longer 
supported: falling

back to defaults

Not sure if this is a problem or not,

That is not a problem.


because I haven't gotten the Braille device working under the VM.

How did you expose the braille device to the VM guest?

Samuel

Re: BRLTTY on Debian Installer Bookworm Alpha 2 release

[Chevelle]

    I was using 'quickemu'.  I think I tried

quickemu --vm --braille --display sdl

I'm not sure from the instructions how it is supposed to work. Should 
'brltty' be running before we start the virtual machine, or not.  I 
searched around, but couldn't find clear instructions.


Thanks.


On 2/23/2023 7:35 PM, Samuel Thibault wrote:

Hello,

Chevelle, le lun. 20 févr. 2023 21:46:46 -0500, a ecrit:

update-rc.d: Warning: start and stop actions are no longer supported: falling
back to defaults

Not sure if this is a problem or not,

That is not a problem.


because I haven't gotten the Braille device working under the VM.

How did you expose the braille device to the VM guest?

Samuel

BRLTTY on Debian Installer Bookworm Alpha 2 release

[Chevelle]

    I was able to install it with speech under QUICK EMU.  I notice if 
I install BRLTTY, I get this:


update-rc.d: Warning: start and stop actions are no longer supported: 
falling back to defaults



Not sure if this is a problem or not, because I haven't gotten the 
Braille device working under the VM.


 Forwarded Message 
Subject:Debian Installer Bookworm Alpha 2 release
Resent-Date:Sun, 19 Feb 2023 12:31:43 + (UTC)
Resent-From:debian-accessibility@lists.debian.org
Date:   Sun, 19 Feb 2023 13:31:15 +0100
From:   Cyril Brulebois 
Reply-To:   debian-b...@lists.debian.org
Organization:   Debian
To: debian-devel-annou...@lists.debian.org
CC: debian-b...@lists.debian.org



The Debian Installer team[1] is pleased to announce the second alpha release
of the installer for Debian 12 "Bookworm".

Following the 2022 General Resolution about non-free firmware[2], many
packages containing firmware files that can be requested by the Linux kernel
at runtime were moved from non-free to non-free-firmware, making them
eligible for inclusion on official media per the updated Social Contract #5.

Starting with this release, official images include firmware packages from
main and non-free-firmware, along with metadata to configure the installed
system accordingly. Our installation guide has been updated accordingly[3].


Improvements in this release


* apt-setup:
- Add an apt-setup/non-free-firmware template, similar to the non-free
and contrib ones, used by 50mirror to enable the non-free-firmware
component: expert install only, disabled by default, but automatically
set when non-free firmware packages are installed.
- Factorize component handling across Debian generators, and add
support for non-free-firmware to all of them.
- Avoid leaving duplicate cdrom: entries in comments at the end of the
installation (#1029922).
* base-installer:
- Ignore multi-arch qualifier (#1020426).
* cdebconf:
- text: During progression, provide user feedback at least every
minute.
- newt: Align more items on top-left in braille mode.
* debian-cd:
- Refresh modalias information for firmware-sof-signed.
- Extend generated firmware metadata with component information.
- Include firmware packages based on the configured components (e.g.
main and non-free-firmware for official builds).
- Bump maximal image size to 1G for netinst CD images: 650 MB is no
longer enough, but current images are still below 700 MB.
- Implement a more robust installer lookup when booting from grub-efi,
using .disk/id/$UUID instead of .disk/info (#1024346, #1024720).
- All amd64 installation images will now boot on amd64 machines using
32-bit UEFI firwmare. Users no longer need the multi-arch installer
for those machines.
- Stop building multi-arch images accordingly.
- Delete support for win32-loader, which is no longer maintained.
* debian-installer:
- Switch to using bookworm artwork for the splash screens (Emerald).
- Fix missing glyphs for Georgian (#1017435).
- Bump Linux kernel ABI to 6.1.0-3.
* debootstrap:
- Add specific handling for the usr-is-merged package.
* espeakup:
- Set speakup_soft direct parameter to 1 in the installed system for
non-English language, to fix the pronunciation of symbols and
numbers.
- Avoid warning about missing mbrola voices.
- Run espeakup in a loop, to compensate for crashes.
* grub-installer:
- Fix missing debconf module integration.
* grub2:
- Add commented-out GRUB_DISABLE_OS_PROBER section to /etc/default/grub
to make it easier for users to turn os-prober back on if they want
it (#1013797, #1009336).
* hw-detect:
- Add support for Contents-firmware indices to speed up firmware
lookup (from requested files to available packages), keeping the
manual lookup as a fallback.
- Add support for component detection, enabling apt-setup/$component
automatically.
- Resolve “usb” module into the underlying module when it requests
firmware files (e.g. rtl8192cu for a RTL8188CUS USB Wi-Fi dongle),
to reload the right module after deploying the relevant firmware
package.
- Delete support for loading udeb firmware packages (*.udeb, *.ude).
- Note: Use cases regarding loading firmware from external storage
remain to be clarified (#1029543). With firmware packages being
included on official images, this is expected to be much less useful
than it was.
- Skip the historical link up/link down dance on some network
interfaces: while it's useful to ensure modules request firmware
files they might require, it's actively harmful if the interface has
been configured (e.g. manually or via preseed): the link is up and/or
it's involved in a bond.
- Implement support for the hw-detect/firmware-lookup=never setting
(#1029848).
* libdebian-installer:
- Ignore multiarch qualifier suffix (#1020783).
* localechooser:
- Enable Vietnamese in non-bogl console.
* ifupdown:
- Fix missing /etc/network/interfaces configuration for wireless
connections when NetworkManager isn't installed, 

Re: how to stop Marco from locking up on Bullseye/Mate?

[Chevelle]

    Ok that is a good tip, thanks.  It doesn't make sense, but since I 
installed firefox-esr version 91.11.0esr-1_deb11u, the problem hasn't 
happened.  Maybe one of the libraries Firefox depends on was upgraded.  
I didn't even start up Firefox previously and would have the problem 
whever I closed VLC or MPV and sometimes Chromium.


If you haven't installed that, you could try it as an experiment.



On 6/29/2022 7:47 PM, Jérémy Prego wrote:


hello,

I confirm this bug under debian with a version of marco higher than 
1.24.0-1.


I had already mentioned this problem earlier without a solution so 
far. I don't know how to reproduce the problem every time.


to unlock marco and orca, just call the orca preferences with the 
shortcut orca + space. once an orca window appears everything 
unlocks...until next time...


    Jerem
Le 29/06/2022 à 20:48, Chevelle a écrit :
If I start VLC to play an audio file and press control-q to quit the 
file Marco gets locked up.  This renders ORCA useless because it 
can't read things properly.  The system is useless at that point.  A 
similar thing happens with MPV.  It was happening with Chromium until 
version 103 came out last week.  If I switch to a console window and 
kill Marco the problem goes away temporarily.


Does anybody have a solution for this or know how to track it down or 
file a bug report on it?


I sent the ORCA developer a debug file demonstrating the problem with 
Chromium, but she never answered me.




On 6/29/2022 9:59 AM, Didier Spaier wrote:

Hello Roberto

Le 29/06/2022 à 15:27, Roberto Burceni a écrit :
Thank you for your response. Which distribution are you using for 
xlqt?
Slint, but running the pre-version 15.0 not yet released (I am its 
maintainer).


Cheers,
Didier

how to stop Marco from locking up on Bullseye/Mate?

[Chevelle]

    If I start VLC to play an audio file and press control-q to quit 
the file Marco gets locked up.  This renders ORCA useless because it 
can't read things properly.  The system is useless at that point.  A 
similar thing happens with MPV.  It was happening with Chromium until 
version 103 came out last week.  If I switch to a console window and 
kill Marco the problem goes away temporarily.


Does anybody have a solution for this or know how to track it down or 
file a bug report on it?


I sent the ORCA developer a debug file demonstrating the problem with 
Chromium, but she never answered me.




On 6/29/2022 9:59 AM, Didier Spaier wrote:

Hello Roberto

Le 29/06/2022 à 15:27, Roberto Burceni a écrit :

Thank you for your response. Which distribution are you using for xlqt?

Slint, but running the pre-version 15.0 not yet released (I am its maintainer).

Cheers,
Didier

Orca errors on most recent stable release

[Chevelle Strobel]

I tried a command like this
gnome-terminal

orca --setup 2test.txt
Traceback (most recent call last):
  File /var/lib/python-support/python2.5/orca/orca.py, line 1021, in 
_showPreferencesConsole
module.showPreferencesUI(_commandLineSettings)
  File /var/lib/python-support/python2.5/orca/orca_console_prefs.py, line 
437, in showPreferencesUI
(not setupSpeech(prefsDict)):
  File /var/lib/python-support/python2.5/orca/orca_console_prefs.py, line 
207, in setupSpeech
choice = int(sayAndPrint(_(Enter choice: ), False, True))
  File /var/lib/python-support/python2.5/orca/orca_console_prefs.py, line 
111, in sayAndPrint
return raw_input(text)
EOFError: EOF when reading a line



My 'brltty' does work.
If I try
orca --setup
I get a message, but it eventually seems to freeze.
'Starting Orca preferences.  This may take some time'
Any ideas?
Thanks.


--
To UNSUBSCRIBE, email to debian-accessibility-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org