[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#426364: xterm dies on popup-menu() action



Package: xterm
Version: 225-1

Using the mouse is cumbersome, so I added these to my X resource
database:

XTerm*vt100.translations: #override \n\
	Ctrl<Key>F1:popup-menu(mainMenu) \n\
	Ctrl<Key>F2:popup-menu(vtMenu)   \n\
	Ctrl<Key>F3:popup-menu(fontMenu) \n\
	Ctrl<Key>F4:popup-menu(tekMenu)

When I try to use one of the first three of these actions, XTerm
dies:

xterm:  warning, error event received:
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  38 (X_QueryPointer)
  Resource id in failed request:  0x0
  Serial number of failed request:  344
  Current serial number in output stream:  344

With the fourth, it segfaults.  Below is a backtrace.  I don't have
debugging symbols installed (I see no xterm-dbg package), but if it
would be helpful, I'm willing to go to some effort to get you a better
backtrace.

   #0  0x0000000000422a08 in ?? ()
   #1  0x0000000000422b51 in ?? ()
   #2  0x00002b38c04f77ce in ?? () from /usr/lib/libXt.so.6
   #3  0x00002b38c04f7aae in ?? () from /usr/lib/libXt.so.6
   #4  0x00002b38c04f819e in _XtTranslateEvent () from /usr/lib/libXt.so.6
   #5  0x00002b38c04d0794 in XtDispatchEventToWidget () from /usr/lib/libXt.so.6
   #6  0x00002b38c04d0e64 in ?? () from /usr/lib/libXt.so.6
   #7  0x00002b38c04cffab in XtDispatchEvent () from /usr/lib/libXt.so.6
   #8  0x0000000000425caf in ?? ()
   #9  0x0000000000414de0 in ?? ()
   #10 0x00000000004151cc in ?? ()
   #11 0x000000000041fff5 in ?? ()
   #12 0x00002b38c0bb88e4 in __libc_start_main () from /lib/libc.so.6
   #13 0x00000000004073fa in ?? ()
   #14 0x00007fffeacde378 in ?? ()
   #15 0x0000000000000000 in ?? ()

I imagine that it doesn't make much sense to try popup-menu(tekMenu)
from the main window, so feel free to call me silly for trying, but
doing so did find a segfault.

Much love,

-- 
Miciah Masters <miciah.masters@gmail.com> / <mdm0304@ecu.edu> / <miciah@myrealbox.com>



Reply to: