[BRLTTY] Brltty behaves strange after wake up.
Anders Holmberg
anders at pipkrokodil.se
Thu Sep 22 17:11:20 EDT 2016
Hi!
Here is the first answer.
Type pm-suspend on your machine and press enter.
Press any key to wake it up.
> 22 sep. 2016 kl. 12:08 skrev Dave Mielke <dave at mielke.cc>:
>
> [quoted lines by Anders Holmberg on 2016/09/21 at 14:56 +0200]
>
>> Using the latest brltty i’ve got som irritating problems when i wake my pc up
>> from Sleep.
>
> Which earlier release of brltty worked properly, or has this always been a
> problem?
> Brltty 5.31 worked like a charm
>> Using Vinux 5 brltty does not wake up automatically but if i disconnect and
>> connect my Papenmeier Els 40 it starts with the side effect that i can not
>> move through the screen.
>
> Do you still see changing output as the screen is updated, though? For example,
> do you see new characters on the braille display as you type them on the
> computer's keyboard?
> Yes i do.
I can not move line by line to see what results i get if i type a command for example.
>> The navigation bar is not responding.
>
> So something about USB input didn't recover.
>
>> Only a beep sound is heard like when you’re at the top or the bottom of the
>> screen.
>
> Always, or only after you press up/down enough times? Maybe it's screen updates
> that you aren't seeing.
>
>> Also if i set brltty to skip blank lines i can not use the display to navigate
>> in Orca.
>
> Yes, that's probably expected. With that setting, brltty sends a different pair
> of commands that Orca probably isn't supporting.
> And what is orca not supporting thats need to be supported.
>> So what should i provide to make it possible for You to track down my problem?
>
> Tw things:
>
> First: Please describe for me how to put my system to sleep and then to wake it
> back up again. Hopefully, I can reproduce your problem here.
>
> Second: Please capture a debug log with:
>
> -L/path/to/logfile
> -ldebug,usb,inpkts,outpkts,brlkeys
>
> Start the log before you put your system to sleep, and leave it running until
> after you reproduce the problem after waking your system back up. Please leave
> noticeable time gaps before the sleep and before the wakeup so that those
> events can be more easily located within the log. Try to let me know exactly
> when the sleep and wakeup took place based on your system's clock (which is
> what's in the log file).
>
> I try to do that.
Its comming soon.
/A
> --
> Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
> Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/
> EMail: Dave at Mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY at mielke.cc
> For general information, go to: http://mielke.cc/mailman/listinfo/brltty
More information about the BRLTTY
mailing list