when i try to start xterm with eightBitInput set to false it would display the following error message: xterm: Error 23, errno 22: Invalid argument Reason: spawn: ioctl() failed on TIOCSETP with eightBitInput set to true xterm starts up properly but it won't recognize my meta-keys (alt) Reproducible: Always Steps to Reproduce: 1. set xresource eightBitInput to false 2. start xterm Actual Results: i had to use another terminal emulator Expected Results: i expected xterm to run and recognize my meta-keys Portage 2.0.51.22-r2 (default-linux/ppc/2004.2, gcc-3.4.4, glibc-2.3.4.20041102-r1, 2.6.12-gentoo-r6 ppc) ================================================================= System uname: 2.6.12-gentoo-r6 ppc 7450, altivec supported Gentoo Base System version 1.6.13 dev-lang/python: 2.2.3-r5, 2.3.5 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.90.0.3-r5 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.4.19-r1, 2.6.8.1-r4 ACCEPT_KEYWORDS="ppc" AUTOCLEAN="yes" CBUILD="powerpc-unknown-linux-gnu" CFLAGS="-O2 -pipe -mcpu=7400 -maltivec -mabi=altivec" CHOST="powerpc-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/afs/C /etc/afs/afsws /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -fno-strict-aliasing -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://ftp.tu-clausthal.de/pub/linux/gentoo/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo http://www.fhh.opensource-mirror.de/gentoo.org/ ftp://ftp.fhh.opensource-mirror.de/pub/gentoo.org/ rsync://rsync.fhh.opensource-mirror.de/gentoo http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/ rsync://linux.rz.ruhr-uni-bochum.de/gentoo/ http://mirrors.sec.informatik.tu-darmstadt.de/gentoo rsync://mirrors.sec.informatik.tu-darmstadt.de/gentoo http://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="ppc X aac aalib airport alsa altivec bash-completion berkdb bitmap-fonts browserplugin bzip2 calendar cdparanoia cdr crypt cscope cups curl decss dga directfb dvd dvdread emboss encode ethereal fam fbcon ffmpeg font-server fortran gb gd gdbm gif gpg gphoto2 gtk gtk2 ieee1394 imagemagick imap imlib ipv6 jack java jpeg lcms ldap libg++ libwww lirc maildir mbox mikmod motif mozcalendar mozdevelop mozilla mozsvg mp3 mpeg mysql nas nasm ncurses network nls nntp offensive ogg oggvorbis opengl pam pcmcia pcsc-lite pda pdflib perl png pnp python qt readline samba sdl slang smartcard snmp spell ssl tcl tcltk tcpd tex theora tiff tk truetype truetype-fonts type1-fonts unicode userlocales vorbis wifi xine xml xml2 xmms xprint xv xvid zlib video_cards_radeon userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTDIR_OVERLAY
Please everyone, test xterm-204 that just went into this tree to see if it solves any of your issues. It works pretty nicely for me.
Adding Thomas to cc.
This sounds like the fix in #201 for Debian #298551.
(In reply to comment #3) > This sounds like the fix in #201 for Debian #298551. exactly. but #201 isn't in my portage-tree and #202 (which was masked) didn't solve the issue. it just seemed to ignore the "eightBitInput" resource and thus didn't recognize the meta-keys regardless of the resource being set to true or false. i'll try #204 as suggested and report on the results as soon as i get home.
Recognizing the meta-key and starting with eightBitInput are really two separate issues. For some cases, the meta-key won't be recognized, and I had added a metaSendsEscape resource to address that. Since it's been a while since I made changes to the handling of meta-keys, I'd need more information to see how to respond to that (whether it's an xterm bug, or X libraries, or configuration, et).
i tried the 204 ebuild and it behaves the same way as the 202 ebuilds. they would start with the eightBitInput recource set to false but the resource had no effect. also trying all possible combinations of eightBitInput and metaSendsEscape did not help anything.
Well bear in mind that I maintain xterm and am not running GenToo. So I'm not familiar with the details of the ebuild. But when I test xterm's eightBitInput option, it does what I expect it to. Here's what I have in xmodmap - the alt key is functioning as the meta key. Your configuration would probably be different. If I'm testing a bug, I compile xterm using the --enable-trace option of the configure script. That logs the information that it uses to decide which key is the meta key, etc: xmodmap: up to 3 keys per modifier, (keycodes in parentheses): shift Shift_L (0x32), Shift_R (0x3e) lock Caps_Lock (0x42) control Control_L (0x25), Control_R (0x6d) mod1 Alt_L (0x40), Alt_L (0x7d), Meta_L (0x9c) mod2 Num_Lock (0x4d) mod3 mod4 Super_L (0x7f), Hyper_L (0x80) mod5 Mode_switch (0x5d), ISO_Level3_Shift (0x7c)
after tweaking my .xmodmap the alt-keys now send the proper escape-sequences and everything is working fine. the bug from versionn #200 is solved since xterm no longer crashes when the eightBitinput resource is set to false in version #204. so regarding to me this bug is solved (at least in version #204). it is still present in #200 though so i'll leave the bug-status untouched and leave the decision about what to do whith it to the maintainer. thanks for your help everyone!
Arch teams -- xterm-204 is a candidate for stabling
Stable on ppc
Sorry, forgot to remove ppc@g.o
Stable on x86
Stable on alpha Cheers Ferdy
stable on ppc64
sparc stable.
Stable on mips.
thanks arch teams
