Re: brltty input monitor error 19

2024-01-24 Thread Colomban Wendling

Le 24/01/2024 à 14:14, Samuel Thibault a écrit :

I'd say ask the brltty mailing list. […]


Fair enough :)  I wondered if it being an older Debian version someone 
here would have clues before I bug upstream and they tell me "dunno, try 
latest version first :)", but well, they surely are gonna be most 
knowledgeable indeed.


FWIW, I searched for the term everywhere I could, and only gone 1 fairly 
inconclusive result.


Anyway, I followed you advice and posted there (can share the link 
whenever it pops up), let's see what happens!


Regards,
Colomban



brltty input monitor error 19

2024-01-24 Thread Colomban Wendling

Hello everyone,

A client of mine is having trouble with brltty sometimes heavily 
spamming the logs with "braille input monitor error 19: No such device", 
and I'm wondering what this could actually mean is the trouble.


Also, by spamming I mean like a lot, for the last week alone he's got 
more than 17 million lines matching that in syslog (~500k one day, 9.1M 
another, and 7.6M yesterday).  When it happens, it spams insanely fast, 
I can count around 50k messages/second for about 5s at a time.


The client is running Buster (yeah I know), which is brltty 
5.6.10+deb10u1 [1], not the most recent of all.


As a workaround, I currently set "log-level critical" to try and not get 
these errors in the logs, as their rate managed to fill /var/log [2]; 
and because the client didn't seem to actually have issues with brltty.


Does anybody here have clues on:
* why does it happen?  Is something *actually* wrong, just going 
unnoticed by the user?
* was it a bug that has been fixed in newer releases?  I know there is 
6.3 in the backports, but I'm slightly reluctant to update the client 
just yet unless I can reasonably hope it actually fixes something.


Thanks for your attention, and looking forward to reading you :)
Colomban

[1]: to be entirely honest, it's a custom build from before +deb10u1 got 
released, but it has the exact same patch from Samuel, and diffing the 
sources show no difference apart from the changelog entry
[2]: which is another issue that it can actually happen, but unrelated 
to brltty




Re: Tasksel

2023-06-28 Thread Colomban Wendling

Hello David,

Le 13/06/2023 à 19:50, David Hoff Jr a écrit :

I installed Tasksel and ran it. It listed various choices and I chose
#19, Debian Console Games. I got an "Access denied" error. I tried
with and without sudo as well as using su to try it from root. […]


I tried myself a couple of ways and I couldn't get a similar error. 
Without sudo it tells me it doesn't have the rights (not very obvious, 
but not that arcane), and through sudo it works just fine.  I tried 
Debian 11 and 12 as well… Only difference I see is that I run amd64 
only, so maybe there's a bug in the i386 arch??


Anyhow, you could workaround installing games-console manually instead 
of going through tasksel.  And possibly report a bug against tasksel if 
there's really something wrong there.


Regards,
Colomban



Re: bookworm for accessibility

2020-03-17 Thread Colomban Wendling
Le 16/03/2020 à 21:16, john doe a écrit :
> On 3/16/2020 8:52 PM, Paul Gevers wrote:
>> Hi hjenkins,
>>
>> On 16-03-2020 19:53, hjenkins wrote:
>>> Packaging the Bookworm e-reader could significantly improve the
>>> accessibility of Debian. Bookworm is written by blind developers,
>>> according to its website.
>>
>> Thanks for letting us know about this piece of software. Are you aware
>> of ebook-speaker, already packaged in Debian. Also that has been written
>> by a blind developer.
>>
>> That said, for this bug: if anybody is interested to do the initial
>> work, I think the accessibility team welcomes the package under the team
>> umbrella.
>>
> 
> According to (1), it is only for Windows.
> 
> "• Make sure you are running Windows 7 or later, and you've installed
> Python 3.7 or a later version:"
> 
> 1)  https://github.com/mush42/bookworm/


I'm not sure everybody's talking about the same "bookworm"…  I believe
this thread is about https://babluboy.github.io/bookworm, which is
definitely available on GNU/Linux.



Re: No sound From Orca after a Strech Install

2017-01-23 Thread Colomban Wendling
Le 22/01/2017 à 19:02, am_d...@fastmail.fm a écrit :
> […]
> 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?

I had the same issue on my Sid install after upgrading speech-dispatcher
(or espeak?) to the version that brought espeak-ng.  I did the same,
selecting the engine manually, but there definitely seem to be a problem
somewhere -- for me, at least through an upgrade path.

Regards,
Colomban



Bug#848119: accerciser: Accerciser is incompatible with ipython3 in unstable

2016-12-14 Thread Colomban Wendling
Package: accerciser
Version: 3.22.0-2
Severity: normal

Dear Maintainer,

The version of Accerciser is in incompatible with ipython3 in unstable, and
leads to the console plugin failing to initialize with the error:

> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/accerciser/plugin/plugin_manager.py", 
> line 192, in _enablePlugin
> plugin_instance.init()
>   File "/usr/share/accerciser/plugins/console.py", line 42, in init
> self.ipython_view = ipython_view.IPythonView()
>   File "/usr/share/accerciser/plugins/ipython_view.py", line 549, in __init__
> input_func=self.raw_input)
>   File "/usr/share/accerciser/plugins/ipython_view.py", line 128, in __init__
> self.IP.readline_startup_hook(self.IP.pre_readline)
> AttributeError: 'InteractiveShellEmbed' object has no attribute 
> 'readline_startup_hook'

The ipython3 from stable works (2.3.0-2).

Regards,
Colomban

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages accerciser depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  gir1.2-atk-1.0   2.22.0-1
ii  gir1.2-gdkpixbuf-2.0 2.36.0-1
ii  gir1.2-glib-2.0  1.50.0-1
ii  gir1.2-gtk-3.0   3.22.5-1
ii  gir1.2-pango-1.0 1.40.3-3
ii  gir1.2-rsvg-2.0  2.40.16-1
ii  gir1.2-wnck-3.0  3.20.1-2
ii  ipython3 5.1.0-3
ii  python3-cairo1.10.0+dfsg-5+b1
ii  python3-pyatspi  2.20.2+dfsg-2
pn  python3:any  

accerciser recommends no packages.

accerciser suggests no packages.

-- no debconf information