Please try with attached kterm binary.
I recompiled vte library with debug enabled.
To show debug output you need to ssh to you kindle export VTE_DEBUG environment variable and start attached binary.
Code:
export VTE_DEBUG="signals,io,lifecycle,pty,keyboard,work,timeout,draw,ally,pangocairo,events,updates,adj,misc,parse,selection,substitution,ring,cursor,matcher,cel
ls,widget-size,style,resize"
The variable contains list of individual debug options. We don't need all of them enabled. You can probably skip some if you realize they are useless for our investigation. Or just post output of all enabled.
Most interesting options output while pressing End
Option "keyboard":
Code:
[root@kindle bin]# export VTE_DEBUG="keyboard"
[root@kindle bin]# ./kterm-debug
Mapping GDK_End via ncurses to '<0x1b>OF', returning.
Sending <1b> to child.
Sending 'O' to child.
Sending 'F' to child.
Maybe there are differences in ncurses on newer platforms?
Option "io":
Code:
[root@kindle bin]# export VTE_DEBUG="io"
[root@kindle bin]# ./kterm-debug
Set terminal encoding to `UTF-8'.
polling vte_terminal_io_read
Feed 29 bytes, in 1 chunks.
read 29/4096 bytes, again? yes, active? yes
read 29/4096 bytes, again? yes, active? no
Handler processing 29 bytes over 1 chunks + 0 bytes pending.
0 chars and 0 bytes in 1 chunks left to process.
Wrote ^[
Wrote O
Wrote F
Option "events":
Code:
[root@kindle bin]# export VTE_DEBUG="events"
[root@kindle bin]# ./kterm-debug
Keypress, modifiers=0x0, keyval=0xffe7, raw string=`(null)'.
Keypress, modifiers=0x0, keyval=0xff57, raw string=`(null)'.