keyboard behaves poorly after ctrl-c

After I press control-C, keyboard input is... well messed up. Like some keys generate ascii junk, non-deterministically. Especially the "r" key and the arrow keys.

octave:1> ver
----------------------------------------------------------------------
GNU Octave Version: 5.1.0 (hg id: d05d6eebde10)
GNU Octave License: GNU General Public License
Operating System: Linux 4.20.16-200.fc29.x86_64 #1 SMP Thu Mar 14 15:10:22 UTC 2019 x86_64
----------------------------------------------------------------------
Package Name  | Version | Installation directory
--------------+---------+-----------------------
     control  |   3.1.0 | /home/cbm/.local/share/octpkgs/5.1.0/control-3.1.0
          io  |  2.4.12 | /home/cbm/.local/share/octpkgs/5.1.0/io-2.4.12
 packajoozle  |   0.1.0 | /home/cbm/.local/share/octpkgs/5.1.0/packajoozle-0.1.0
  statistics  |   1.4.0 | /home/cbm/.local/share/octpkgs/5.1.0/statistics-1.4.0
octave:2> a = 42
a = 42
octave:3> % going to press Ctrl-C
octave:3> 
[~] 
octave:3> �%�
 parse error:

  invalid character '�' (ASCII 254)

>>> ��
    ^

octave:3> % pressed and ok if I t�
yparse error:

  invalid character '�' (ASCII 254)

>>> �
    ^

octave:3>�
%parse error:

  invalid character '�' (ASCII 254)

>>> �
    ^

octave:3�
-bash: fg: %: no such job
[~] ps�
�  PID TTY          TIME CMD
 9009 pts/32   00:00:00 bash
 9173 pts/32   00:00:00 bwrap
 9182 pts/32   00:00:01 octave-gui
 9228 pts/32   00:00:00 ps
[~] a = 42
bash: a: command not found...
[~] 

Also, when I press Ctrl-C, I see my BASH prompt, but Octave is still running. Not really clear when my commands were going to bash and when to Octave.

Is bwrap doing some filtering on my keycodes? Feels like I've Ctrl-C'd something other than Octave...