[BRLTTY] could this be a bug?

[kendell clark]

hi
Ok, testing with a fresh copy built from source it was indeed the commit
ID I was seeing. But after that went away all I got was "screen not in
text mode" until I downgraded back to the installed copy and restarted
both brltty and orca, then braille worked. But only after restarting
them both. I then restarted the computer to make sure the bug was back
and it was. So I'm not sure if the bug is fixed and something else went
wrong, or ... I'm stumped.
Thanks
Kendell Clark


kendell clark wrote:
> hi
>
> Oh it didn't fix the bug where orca wasn't detecting the display after
> it was plugged in, it just worked again once I restarted brltty and
> orca, whereas it wouldn't work with the built version. I'll test
> again, it's definitely possible I was reading the revision number, and
> wasn't sure what I was reading lol. That was probably it now that I
> think about it.
>
> Thanks
>
> Kendell Clark
>
>
>
> On 9/7/2016 12:23 AM, Dave Mielke wrote:
>> [quoted lines by kendell clark on 2016/09/06 at 22:17 -0500]
>>
>>> Unfortunately this doesn't seem to have fixed the problem. When I build
>>> brltty and then start it, after the brltty version 5.4 etc message,
>>> what
>>> looks like 445426 appears on the display for about 3 seconds,
>> It should read: BRLTTY-5.4-66-g8d46edbf
>> The braille is: ⡃⡗⡇⡞⡞⡽⠤⠢⠨⠲⠤⠖⠖⠤⠛⠦⠙⠲⠖⠑⠙⠃⠋
>>
>> That doesn't look the same. Perhaps you could check your system log
>> to be
>> sure since that won't disappear.
>>
>>> followed by the "screen not in text mode" message. This is with
>>> plugging in
>>> the display after orca has started to test the patch. In order to
>>> fix it I had
>>> to reinstall the packaged version of brltty, and then restart both
>>> brltty and
>>> orca, and braill works again.
>> Perhaps I've misunderstood something, then, because I thought that
>> that was the
>> problem (connecting the braille display after Orca had started) so I
>> don't
>> understand why going back to the old version would fix it.
>>
>