Hello,
Aura Kelloniemi, le jeu. 26 nov. 2020 11:42:54 +0200, a ecrit:
> But what if I had open BrlAPI connections? They are still open, but
> they are being served by the BRLTTY talking to the (now non-existent)
> Bluetooth receiver.
If the bluetooth-serving BRLTTY daemon is still running, yes.
Dave Mielke (2020/11/26 10:54 -0500):
> >There is no way to automatically determine what the "right" BRLTTY
> >instance would be. It depends on what the user wants.
>
> This is something I've been thinking about from time to time. What we really
> need is for a given USB device to be associated
[quoted lines by Mario Lang on 2020/11/26 at 08:50 +0100]
>There is no way to automatically determine what the "right" BRLTTY
>instance would be. It depends on what the user wants.
This is something I've been thinking about from time to time. What we really
need is for a given USB device to be
[quoted lines by Samuel Thibault on 2020/11/26 at 09:31 +0100]
>I don't think there is anything in the brltty source to make them
>consecutive? I would have rather thought that they all try to bind on
>the default TCP port, and the BRLTTY started last will wait for the
>previous BRLTTY to
Mario Lang writes:
> Aura Kelloniemi writes:
> > If I have many BRLTTYinstances running, will BrlAPI clients connect to
> > the right BRLTTY (i.e. will the latest BRLTTY be able to override the
> > BrlAPI server for the previously started instances)?
> There is no way to automatically
Sébastien Hinderer, le jeu. 26 nov. 2020 09:39:38 +0100, a ecrit:
> I was sure at some point we had some code to look for the first free TCP
> port starting with our base IANA port and choosing that one.
That reminds me something indeed, but that leads to non-deterministic
behavior, which is not
Samuel Thibault (2020/11/26 09:31 +0100):
> Sébastien Hinderer, le jeu. 26 nov. 2020 08:39:11 +0100, a ecrit:
> > When several instances of BRLTTY are started, each instance that is
> > asked to run a BrlAPI server will do so and, by default, the servers
> > will be listening on ocnsecutive TCP
Sébastien Hinderer, le jeu. 26 nov. 2020 08:39:11 +0100, a ecrit:
> When several instances of BRLTTY are started, each instance that is
> asked to run a BrlAPI server will do so and, by default, the servers
> will be listening on ocnsecutive TCP ports.
consecutive?
I don't think there is
Aura Kelloniemi writes:
> If I have many BRLTTYinstances running, will BrlAPI clients connect to
> the right BRLTTY (i.e. will the latest BRLTTY be able to override the
> BrlAPI server for the previously started instances)?
There is no way to automatically determine what the "right" BRLTTY
Hello,
When several instances of BRLTTY are started, each instance that is
asked to run a BrlAPI server will do so and, by default, the servers
will be listening on ocnsecutive TCP ports.
Thus, yes, a client will, by default, connect to the first BrlAPI server
it finds. However, the BRLAPI_HOST
Hello,
Sébastien Hinderer writes:
> Okay, thanks for the explanations!
> So everything will work nicely with 6.2, I guess.
Dave, even BrlAPI? If I have many BRLTTYinstances running, will BrlAPI clients
connect to the right BRLTTY (i.e. will the latest BRLTTY be able to override
the BrlAPI
[quoted lines by Sébastien Hinderer on 2020/11/25 at 18:59 +0100]
>So everything will work nicely with 6.2, I guess.
Yes, I expect so.
--
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/
EMail:
Okay, thanks for the explanations!
So everything will work nicely with 6.2, I guess.
Sébastien.
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to:
[quoted lines by Sébastien Hinderer on 2020/11/25 at 17:47 +0100]
>So are you saying that a Linux distribution like Debian should actually
>not start brltty as part of its boot process by default?
It could, but then it should have a brltty.conf that specifies braille-device
bluetooth: so that it
Dave Mielke (2020/11/25 11:41 -0500):
> [quoted lines by Sébastien Hinderer on 2020/11/25 at 17:25 +0100]
>
> >If an instance is run as part of system boot, I would have guessed that
> >this instance run at boot would try to use the USB device, but I am
> >guessingI am wrong here?
>
> Yes, and
[quoted lines by Sébastien Hinderer on 2020/11/25 at 17:25 +0100]
>If an instance is run as part of system boot, I would have guessed that
>this instance run at boot would try to use the USB device, but I am
>guessingI am wrong here?
Yes, and that shouldn't be done by default on a
Hello,
Out of curiosity...
Dave Mielke (2020/11/25 10:55 -0500):
> That isn't a problem. Well, it was a bit of a problem before the latest fix to
> the udev rules. Now it works exactly as it should. Connecting a braille device
> via USB starts up an instance of brltty for that device, and
[quoted lines by Aura Kelloniemi on 2020/11/25 at 15:03 +0200]
>Sorry of being imprecise. I meant that using BrlAPI will fail, if an automatic
>instance is started while there is already anther instance of BRLTTY running.
That isn't a problem. Well, it was a bit of a problem before the latest
Hi
Dave Mielke writes:
> [quoted lines by Aura Kelloniemi on 2020/11/24 at 18:46 +0200]
> >This probably is not enough, if there is a "system-wide" instance of BRLTTY
> >running, for example if if the main method of connecting one's display is
> >via
> >Bluetooth.
> Only USB connections
Hi list,
Dave Mielke writes:
> [quoted lines by Alexander Epaneshnikov on 2020/11/22 at 01:32 +0300]
> >if i unplug display and plug it back. new brltty instance can't
> >connect to brlapi. i get this:
> >ноя 22 01:27:14 alex-pc brltty[2549]: another BrlAPI server is already
> >listening
23.11.2020 20:05, Dave Mielke пишет:
> [quoted lines by Alexander Epaneshnikov on 2020/11/23 at 19:46 +0300]
>
>> 23.11.2020 18:38, Dave Mielke пишет: > [quoted lines by Alexander
>> Epaneshnikov
>> on 2020/11/23 at 10:55 +0300] > > > ноя 23 10:33:14 brltty[492]:
>>
[quoted lines by Alexander Epaneshnikov on 2020/11/23 at 19:46 +0300]
>23.11.2020 18:38, Dave Mielke пишет: > [quoted lines by Alexander Epaneshnikov
>on 2020/11/23 at 10:55 +0300] > > > ноя 23 10:33:14 brltty[492]:
>polkit_authority_check_authorization_sync error:
[quoted lines by Alexander Epaneshnikov on 2020/11/23 at 10:55 +0300]
>ноя 23 10:33:14 brltty[492]: polkit_authority_check_authorization_sync error:
>GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Unix process subject does
>not have uid set
Another user has reported a similar problem.
[quoted lines by Alexander Epaneshnikov on 2020/11/23 at 11:45 +0300]
>followup to reconnection problem. if i disconnect display and connect it
>again
>systemd will flag unit as failed. i think this happens because
>Process /usr/lib/brltty/systemd-wrapper -C exits with code 3.
There's
followup to reconnection problem. if i disconnect display and connect it
again
systemd will flag unit as failed. i think this happens because
Process /usr/lib/brltty/systemd-wrapper -C exits with code 3.
relevant logs:
ноя 23 11:13:42 alex-pc brltty[3620]: USB URB status error 71: Ошибка
23.11.2020 00:39, Dave Mielke пишет:
> [quoted lines by Alexander Epaneshnikov on 2020/11/22 at 23:20 +0300]
>
>> now only log problem is remains.
> Fixed. It's a change to brltty@.service.
>
thanks. fix is confirmed. don't know, is it relevant, but in logs i get this:
ноя 23 10:33:14
[quoted lines by Alexander Epaneshnikov on 2020/11/22 at 23:20 +0300]
>now only log problem is remains.
Fixed. It's a change to brltty@.service.
--
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/
22.11.2020 09:48, Dave Mielke пишет:
> [quoted lines by Alexander Epaneshnikov on 2020/11/22 at 01:32 +0300]
>
>> if i unplug display and plug it back. new brltty instance can't
>> connect to brlapi. i get this:
>> ноя 22 01:27:14 alex-pc brltty[2549]: another BrlAPI server is already
>> listening
[quoted lines by Alexander Epaneshnikov on 2020/11/22 at 01:32 +0300]
>if i unplug display and plug it back. new brltty instance can't
>connect to brlapi. i get this:
>ноя 22 01:27:14 alex-pc brltty[2549]: another BrlAPI server is already
>listening on 0 (file /var/lib/BrlAPI/.0 exists)
>
>i
hello. responding to call for testing. my setup is:
brltty 6.1.r606.g1d757b705-1 compiled with systemd and udev support.
when i view the logs by journactl i get duplicated output like this:
ноя 22 01:09:45 alex-pc brltty[490]: BRLTTY 6.1 rev
BRLTTY-6.1-606-g1d757b70 [http://brltty.app/]
ноя 22
30 matches
Mail list logo
