[drawterm] two bugs

[Maurice Quennet <maurice@quennet.eu>]

Hi,

I've just hit two bugs in drawterm.

The first one I could pin down to commit 175:5afb44d9672b. When
pressing (and releasing) the Ctrl key once, drawterm gets stuck
and thinks the Ctrl key is then pressed forever (I found no
method to stop this). This results in being unable to type
lowercase characters ('d' becomes '^D'). (Yes, I checked; I did
indeed take my finger off the Ctrl key.) The bug can be
circumvented using "-B".

The second bug is rather obscure, but nonetheless I was able to
hit it while recompiling my system. To reproduce: log into an
account, which doesn't start rio on login (in my case it was
"glenda" on a CPU server), so you get the drawterm console.
Then, while lots of text is scrolling on the screen (e.g.
recompiling the system; `seq 100000` does the trick, too),
flip fast and long enough between virtual desktops and soon
enough drawterm will crash and dump

[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has 
not been called
[xcb] Aborting, sorry about that.
drawterm: xcb_io.c:274: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.

into ~/.xsession-errors. It seems, that the more text has scrolled
past the screen the sooner drawterm will crash.

I have no clue about X11 programming, so no patches. Sorry.

- Maurice

PS: I doubt it is relevant in this case, but just for the sake of
completeness: Drawterm runs on Slackware 14.1 with XFCE 4.10 on a
Thinkpad x230 and 9front runs 9pccpuf (commit: 5174:b56a9e7f8cd0)
on an Intel NUC DN2820FYKH.