Samuel Thibault wrote:
> I can indeed reproduce it with the XWindow driver. Could you try the
> attached patch?
>
> The fix is making api_unlink restore the brlapi server state to what it
> is on first entering api_link: while the api is unlinked, the driver
> should be not constructed from the
AlexTrial91, le Mon 18 Jun 2012 00:39:40 +0200, a écrit :
> > What could I do ?
>
> please run run-debug.bat and send us the debug.log
> and brltty.conf files.
>
> I can't run it.
Why?
> I can just reinstall or restart my computer for changing BRLTTY
> configuration.
Just to make i
Hi Samuel!
2012/6/18 Samuel Thibault
> AlexTrial91, le Mon 18 Jun 2012 00:31:19 +0200, a écrit :
> > It's the same with BRLTTY debug mode.
>
> > What's problem ?
>
> Hard to say without error messages etc.
>
I know.
>
> > What could I do ?
>
> please run run-debug.bat and send us the debug.log
AlexTrial91, le Mon 18 Jun 2012 00:31:19 +0200, a écrit :
> It's the same with BRLTTY debug mode.
> What's problem ?
Hard to say without error messages etc.
> What could I do ?
please run run-debug.bat and send us the debug.log
and brltty.conf files.
Samuel
Hi everybody, I'm new here. I'm A French user of BRLTTY with NVDA on
Windows. My braille display is an Eurobraille Iris 40.
I come to you because I've an important issue on both Windows 7 (32
and 64 bits). When I start my computer and I launch NVDA without connecting
my braille display, then I conn
Hello,
Jason White, le Sun 17 Jun 2012 17:40:13 +1000, a écrit :
> Interestingly, this bug was hard to trigger under BRLTTY 4.3, but under 4.4 I
> am finding that I can reliably reproduce it - I just power down the braille
> display, ask another user to log into the machine and start an X session
Jason White (2012/06/17 18:34 +1000):
> The driver code in updateBaumKeys() in the driver which handles this case is:
>
> case BAUM_RSP_PowerdownSignal:
> if (!logBaumPowerdownReason(packet.data.values.powerdownReason)) continue;
> errno = ENODEV;
> return;
I don't know whether this way of
Shérab wrote:
> Hello,
>
> when the device is powered donw, does the driver return
> BRL_CMD_OFFLINE ?
The driver code in updateBaumKeys() in the driver which handles this case is:
case BAUM_RSP_PowerdownSignal:
if (!logBaumPowerdownReason(packet.data.values.powerdownReason)) continue;
errn
Hello,
when the device is powered donw, does the driver return
BRL_CMD_OFFLINE ?
Sherab.
___
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/mailm
Samuel Thibault wrote:
> Could you try this one?
With this patch applied, we still segfault at the same line, with disp ==
NULL.
Interestingly, this bug was hard to trigger under BRLTTY 4.3, but under 4.4 I
am finding that I can reliably reproduce it - I just power down the braille
display, as
10 matches
Mail list logo
