On Thu, Jan 08, 2009 at 08:41:35AM -0800, Larry Doolittle wrote: > Thomas - > > On Thu, Jan 08, 2009 at 10:27:02AM -0500, Thomas Dickey wrote: > > On Wed, Jan 07, 2009 at 07:30:08PM +0100, Larry Doolittle wrote: > > > Package: xterm > > > Version: 238-2 > > > Severity: normal > > > > > > Upgrading amd64 from xterm_237-1 to xterm_238-2, the > > > keypad PgUp and PgDn keys stopped responding. This > > > is an ordinary PC keyboard. The dedicated PageUp and > > > PageDown keys are still OK. > > > > That sounds as if "cat -v" will not show any response at all. > > Correct. > > > If it's that type of breakage, it might be possible to see > > the details in xterm's debug-trace (by configuring xterm with > > "--enable-trace"). > > OK. I added "--enable-trace" to the debian/rules configure command, > and re-ran "dpkg-buildpackage -rfakeroot". Finally, I instal the > resulting .deb. > > Now every time I run xterm, I get a Trace-child.out and Trace-parent.out. > The first isn't interesting. Here is what looks like the relevant > snippet of Trace-parent.out, as I pressed PgUp and PgDn: > > Handle 7bit-key > Input keysym 0xFF9A, 0:'' 7bit KeypadKey > ...Input keypad before was 0xFF9A > ...Input keypad changed to 0x10000FF55 > Handle 7bit-key > Input keysym 0xFF9B, 0:'' 7bit KeypadKey > ...Input keypad before was 0xFF9B > ...Input keypad changed to 0x10000FF56 > > Unlike other keystrokes, it never hits a writePtyData. > I'll attach a compressed Trace-parent.out, where I simply > typed "cat -v\n", and then PageUp, PageDown, PgUp, PgDn, PageUp, PageDn, > return, ^D, ^D. Maybe there are clues other than the segment > above, such as in the setup. thanks - it seems to be working on my machine, so I should be able to see some difference in the trace. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
Attachment:
pgpF3n4blhBEZ.pgp
Description: PGP signature