It looks like some posts to this list had problems yesterday. For example,
posts may have been rejected due to no space on the server. The problems
occurred between about 14:00 UTC yesterday till about 03:00 UTC today. Please
repost any of your messages that you either know or feel didn't get th
Le mercredi 29 juin à 14:00, Didier Spaier a écrit :
> On 29/06/2016 13:22, Dave Mielke wrote:
> > [quoted lines by Didier Spaier on 2016/06/29 at 10:50 +0200]
> >
> > Did you used to use a udev rules file that worked? If so, could you please
> > post
> > it?
>
> I just appended a double quote
{repost}
Thank you for the reply, here is the new output log file. I changed
brltty.conf according to your instructions.
2016-06-29@17:02:57.265 [brltty] BRLTTY 5.4 rev unknown [http://brltty.com/]
2016-06-29@17:02:57.268 [brltty] lock descriptor allocated:
queue-discarded-elements
2016-06-2
[quoted lines by Arthur BREUNEVAL on 2016/06/30 at 12:49 +0200]
>here is the new output log file. I changed brltty.conf according to your
>instructions.
Thanks. Brltty simply isn't seeing the device. Could you please do lsusb to see
if Linux is or isn't seeing it? Also, I'd appreciate a copy of
(message initially sent on 29/06/2016 13:49 UTC with in CC
Philippe DELAVALADE and Patrick J. VOLKERDING)
On 29/06/2016 14:00 (12:00 UTC), Didier Spaier wrote:
> Meanwhile I just realized that I sent to Philippe a package built on
> Slint64-14.2 but he has 14.1 as that (triggered a version misma
On 29/06/2016 16:27, Dave Mielke wrote:
> [quoted lines by Didier Spaier on 2016/06/29 at 10:50 +0200]
>
>> On 29/06/2016 09:27, Didier Spaier wrote:
>>> On 29/06/2016 08:59, Dave Mielke wrote:
[quoted lines by Didier Spaier on 2016/06/29 at 08:45 +0200]
> In dmesg's output and /var/
[quoted lines by Didier Spaier on 2016/06/30 at 14:38 +0200]
>(and sorry to have bothered you with this issue in two voicemail messages).
Why would you be sorry? I didn't realize the server was having problems until
you made me aware of it. Thank you.
>To clarify, in the source tarball I sent t
Let's do it.
$ lsusb
Bus 001 Device 008: ID c251:1130 Keil Software, Inc.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
On 6/28/2016 11:29 PM, Dave Mielke wrote:
[quoted lines by Chevelle on 2016/06/28 at 23:05 -0400]
I downloaded brltty-win-5.4-1-libusb-1.0.exe. Microsoft Security
Essentials flags Win32/Maltule.c!cl; as a threat. Not sure if it is,
but I let it remove it.
Googling it says that it's a Trojan t
[quoted lines by Arthur BREUNEVAL on 2016/06/30 at 18:27 +0200]
Hi:
This is interesting. The two files identify the Esytime differently.
>$ lsusb
>Bus 001 Device 008: ID c251:1130 Keil Software, Inc.
>$ cat /sys/kernel/debug/usb/devices
>P: Vendor=c251 ProdID=1130 Rev= 1.00
>S: Manufacturer=E
Hi,
a c (2016/06/29 11:12 +):
> Hi,
>
> I'm writing some C++ code on ubuntu, trying to connect to a Papenmeier
> Braillex EL 40s and just write some characters on it, for a start.
> However, when taking control of the tty using the default tty number
> (brlapi_enterTtyMode(BRLAPI_TTY_DEFAULT,
[quoted lines by Arthur BREUNEVAL on 2016/06/30 at 22:08 +0200]
>Actually, I built using the brltty with the '--without-usb-package'
>option invoking configure, because I thought that libusb was only
>when you would build on Windows with Cygwin...
>So should I specify an USB package even on Linux?
Oh lol! So now there is an important progression. The output log file is
below...
Don't worry is the date does not correspond, but it is a fresh log file.
2016-06-29@22:40:16.538 [brltty] BRLTTY 5.4 rev unknown [http://brltty.com/]
2016-06-29@22:40:16.540 [brltty] lock descriptor allocated:
qu
[quoted lines by Arthur BREUNEVAL on 2016/07/01 at 00:19 +0200]
>Oh lol! So now there is an important progression.
Yes, it makes a bit of a difference. :-) We try to listen to our users, even
when they're configuring a build. :-)
>The output log file is below...
I'd like to know if this is a
Yes, when I plug it up, I see the firmware version: 'Esytime 1.03
31-03-2014' is printed.
I try to make BRLTTY work with it since about 5.2. But I was under
Windows - Cygwin so not really in the best conditions. And it was not
absolutely necessary, so I tried some things sometimes. I tried to
[quoted lines by Arthur BREUNEVAL on 2016/07/01 at 01:05 +0200]
>Yes, when I plug it up, I see the firmware version: 'Esytime 1.03
>31-03-2014' is printed.
I'll check to be sure, but that does indeed look like a year or two ago so it's
probably the expected problem. In fact, when I compare our c
hi all
I've been struggling to enable brltty as a console screen reader for the
sonar gnu linux distribution. I'm getting nowhere with the espeak driver
so I'd like to reconfigure brltty to speak through speech-dispatcher.
But for whatever reason, the package for archlinux, which manjaro and
sonar
17 matches
Mail list logo
