Vincent LE GOFF writes:
> I was referring to the other keyboard, as a matter of fact. The
> computer's. On NVDA and Orca (and I think on BRLTTY), one can use the
> numpad7 and numpad9 to go up and down in the window.
Yes, and Dave's suggestion to use -kkeypad will allow you to do just
that.
If
Cheryl Homiak wrote:
> 1. Debian's brltty package uses /sbin/brltty for the daemon. My development
> version is in /usr/local but I am not using /sbin as far as I know. While it
> appears to run fine when I switch to it, I'm wondering whether I have to
> have some way of starting the daemon from
Jason White wrote:
> I'm not sure how you would change this, but I think you have to copy it into
> /etc/systemd/system and then modify the above line, e.g., to refer to
> /usr/local/bin/brltty or whatever you need.
I looked it up: after placing the modified file in
/etc/systemd/system/brltty.
Hi Dave!
I can also confirm that this issue no has gone. Took a while until I
noticed I had the problem.
Thanks and regards, Lars
On Thu, Dec 17, 2015 at 02:10:57PM -0500, Dave Mielke wrote:
> [quoted lines by Nicolas Pitre on 2015/12/17 at 13:29 -0500]
>
> >That calls for another official rele
Okay that worked. I disabled brltty and enabled brltty-github and rebooted and
the development version came up. If I didn't want to use the Debian version at
all, I suppose I could uninstall the debian package and then rename and
reenable the brltty-github version as brltty but for now I will le
Cheryl Homiak wrote:
> Okay that worked. I disabled brltty and enabled brltty-github and rebooted
> and the development version came up. If I didn't want to use the Debian
> version at all, I suppose I could uninstall the debian package and then
> rename and reenable the brltty-github version as b
Yes, I agree. That's why I am leaving it there for now.
--
Cheryl
May the words of my mouth
and the meditation of my heart
be acceptable to You, Lord,
my rock and my Redeemer.
(Psalm 19:14 HCSB)
> On Dec 19, 2015, at 12:53 PM, Jason White wrote:
>
> Cheryl Homiak wrote:
>> Okay that work
Since we do need to release 5.3.1 more or less now in order to resolve the
"can't get console state" issue, I hope you don't mind that I'd like to deal
with any HIMS qwerty keyboard issues as quickly as possible. To this end:
I'd like to see a log of autodetection with: -ldebug,inpkts,outpkts,br
Hi,
I hope I'm not too much in late. I had a major debugging to do on a
different product all morning and part of the afternoon. And it's not
even over, but I got a break. I've tried seeing both logs, but I got
something really odd. The first one (brltty.log) is an extended
description wh
[quoted lines by Vincent LE GOFF on 2015/12/19 at 16:43 -0800]
>I hope I'm not too much in late.
Not at all. Thanks for capturing those two logs.
>I had a major debugging to do on a different product all morning and part of
>the afternoon. And it's not even over, but I got a break.
That's f
Hi,
The fact that the BRLTTY driver failed for five successive attempts is
probably due to the fact I cannot plug the device in at once. Linux runs
in a virtual machine, but when I open it, it attempts to transfer toe
USB port to the virtual machine, so the guest machine can use it instead
of
11 matches
Mail list logo
