> Am 25.06.2023 um 22:10 schrieb Dave Mielke :
>
> [quoted lines by Christian Schoepplein on 2023/06/25 at 20:59 +0200]
>
>> For me it is OK to set
>>
>> dev.tty.legacy_tiocsti=1
>>
>> in /etc/sysctlconf as a workaround like Rob suggested, thanks Rob for this
>> hint!
>
> I'm wondering if
Hello,
On 2023-06-27 at 07:09 +0200, Mario Lang wrote:
> Nicolas Pitre writes:
> > On Sun, 25 Jun 2023, Dave Mielke wrote:
> >> I'm wondering if brltty shouldn't just set it automatically?
> > The brltty package could install a file in /etc/sysctl.d/ to provide
> > that config. This way
Nicolas Pitre writes:
> On Sun, 25 Jun 2023, Dave Mielke wrote:
>
>> [quoted lines by Christian Schoepplein on 2023/06/25 at 20:59 +0200]
>>
>> >For me it is OK to set
>> >
>> >dev.tty.legacy_tiocsti=1
>> >
>> >in /etc/sysctlconf as a workaround like Rob suggested, thanks Rob for this
>>
Dave Mielke, le lun. 26 juin 2023 12:49:05 -0400, a ecrit:
> TIOCSTI injects input. Of course one could argue that that poses a security
> risk, but how is that different from creating a uinput device and injecting
> key events? What am I missing?
Basically, TIOCSTI is not privileged and
TIOCSTI injects input. Of course one could argue that that poses a security
risk, but how is that different from creating a uinput device and injecting key
events? What am I missing?
--
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke| 2213 Fox
Hi,
On 2023-06-25 at 16:10 -0400, Dave Mielke wrote:
> [quoted lines by Christian Schoepplein on 2023/06/25 at 20:59 +0200]
> >For me it is OK to set
> >
> >dev.tty.legacy_tiocsti=1
> >
> >in /etc/sysctlconf as a workaround like Rob suggested, thanks Rob for this
> >hint!
> I'm
On Sun, 25 Jun 2023, Dave Mielke wrote:
> [quoted lines by Christian Schoepplein on 2023/06/25 at 20:59 +0200]
>
> >For me it is OK to set
> >
> >dev.tty.legacy_tiocsti=1
> >
> >in /etc/sysctlconf as a workaround like Rob suggested, thanks Rob for this
> >hint!
>
> I'm wondering if brltty
[quoted lines by Christian Schoepplein on 2023/06/25 at 20:59 +0200]
>For me it is OK to set
>
>dev.tty.legacy_tiocsti=1
>
>in /etc/sysctlconf as a workaround like Rob suggested, thanks Rob for this
>hint!
I'm wondering if brltty shouldn't just set it automatically?
--
I believe the Bible to
Hi Samuel and all who replied to my request,
> Am 25.06.2023 um 18:12 schrieb Samuel Thibault :
> Christian Schoepplein, le ven. 23 juin 2023 16:37:45 +0200, a ecrit:
>> Is this a known issue with kernel 6.3?
>
> Unfortunately, yes: TIOCSTI poses security problems so it got
> disabled by
Hello,
Christian Schoepplein, le ven. 23 juin 2023 16:37:45 +0200, a ecrit:
> Is this a known issue with kernel 6.3?
Unfortunately, yes: TIOCSTI poses security problems so it got
disabled by default. I had warned at that time that it was needed for
accessibility and proposed solutions, but
You need to set
dev.tty.legacy_tiocsti=1
in
/etc/sysctl.conf
- Original Message -
From: Elias Oltmanns
To: Christian Schoepplein
Cc: debian-accessibil...@lists.debian.org, BRLTTY@brltty.app
Date: Sat, 24 Jun 2023 16:57:32 +0200
Subject: Re: [BRLTTY] Cursor routing not longer working
I am using 6.1.33 but I use gentoo and Brltty is working properly,
just tested with routing keys.
On Sat, 24 Jun 2023 10:57:32 -0400,
Elias Oltmanns wrote:
>
> Hi Schoepp,
>
> apparently, all keypresses emulated by BRLTTY show no reaction. This is
> on Manjaro (Arch Linux derivative), Kernel
Hi Schoepp,
apparently, all keypresses emulated by BRLTTY show no reaction. This is
on Manjaro (Arch Linux derivative), Kernel version 6.3.5 and BRLTTY 6.5.
Since I am on Kernel version 6.1 regularly, I booted into 6.3 only now
to double check. Indeed, everything works as usual under 6.1 but
Hi,
I am using Debian testing and today the kernel was updated to
linux-image 6.3. Since this update the cursorrouting is not working
anymore in the pure text console. In the graphical environment (Mate)
and also in the settings menu of brltty the cursorrouting keys are
working and
14 matches
Mail list logo
