Hi,
Sorry for the delay. Thank you for your prompt reply. I'm running
Vinux on a virtual machine (perhaps the probem comes from here, but I
don't think so). I had to restart it and find a way to transfer the log
file. I'm afraid this first attempt will not help you much. Here's
what my log was filled with. I guess I should have stopped BRLTTY
before running the 'sudo brltty -L/path/to/log/file /linputs.brlkeys'
command, but I don't know how to do that:
2015-12-13@15:35:29.794 [brltty] BRLTTY 5.2dev rev
BRLTTY-5.1-794-g565e9b1b [htt
p://brltty.com]
2015-12-13@15:35:29.818 [brltty] BrlAPI Server: release 0.6.2
2015-12-13@15:35:29.818 [server-main] another BrlAPI server is already
listening
on 0 (file /var/lib/BrlAPI/.0 exists)
2015-12-13@15:35:29.818 [server-main] error while creating socket 0
2015-12-13@15:35:29.826 [brltty] USBFS open error: /dev/bus/usb/001/003:
Permiss
ion denied
2015-12-13@15:35:29.826 [brltty] USB language code string read error
2015-12-13@15:35:29.826 [brltty] USBFS open error: /dev/bus/usb/001/003:
Permiss
ion denied
2015-12-13@15:35:29.826 [brltty] USB language code string read error
2015-12-13@15:35:29.826 [brltty] USBFS open error: /dev/bus/usb/001/003:
Permiss
ion denied
2015-12-13@15:35:29.826 [brltty] USB language code string read error
2015-12-13@15:35:29.826 [brltty] open error:
/sys/dev/char/189:2/power/autosuspe
nd: Permission denied
2015-12-13@15:35:29.826 [brltty] USBFS open error: /dev/bus/usb/001/003:
Permiss
ion denied
2015-12-13@15:35:29.826 [brltty] USBFS open error: /dev/bus/usb/001/003:
Permiss
ion denied
2015-12-13@15:35:29.826 [brltty] USB configuration descriptor not
readable: 0
2015-12-13@15:35:29.826 [brltty] USB configuration descriptor not found: 1
... and so on. Nothing meaningful seemed to be in this file, I guess I
didn't do the right thing. Since it was hard to upload the log file and
took me some time, perhaps the useful information was lost, too, which
is possible. Can you tell me how to restart BRLTTY with the proper
options? I'm quite nez to Linux (at least as far as a direct access is
concerned) and I guess I missed something on the way.
Thank you again,
Vincent
On 12/13/2015 3:22 PM, Dave Mielke wrote:
[quoted lines by Vincent LE GOFF on 2015/12/13 at 14:43 -0800]
almost everything works well... except for the keys. Actually,
most keys on the keyboard trigger the right commands on the computer
(one can type on the BrailleSense QWERTY keyboard almost without
error), but the navigation keys don't work at all.
You've asked about this just in time! We're planning on releasing 5.3 this
week, but let's try to fix this problem first. It's actually a problem I've
been waiting to resolve, where waiting means waiting for a helpful user with a
Braille Sense qwerty. I guess that's you. :-)
What I'd like you to do is to capture a debug log while you're pressing those
keys so that we can see what the device is sending. To capture the debug log,
please add two options to your invocation of brltty. One is -L (uppercase) to
specify the location of the log file that'll be written, and the other is -l
(lowercase) to specify what should be logged. In this case, we'd like to log
input packets sent from the device and braille device key events. So, those two
options would be:
-L/path/to/logfile
-linpkts,brlkeys
If those aren't enough log categories then I'll let you know what other ones to
add. Please press the keys (or key combinations), one at a time, in a known
order. Then, along with the debug log, let us know exactly which order you
pressed them in.
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@mielke.cc
For general information, go to: http://mielke.cc/mailman/listinfo/brltty
