Red Hat Bugzilla – Bug 156470
xterm fails to start with "ioctl() failed on TIOCSETP"
Last modified: 2007-11-30 17:11:05 EST
Description of problem:
Trying to start xterm yields the following message:
xterm: Error 23, errno 22: Invalid argument
Reason: spawn: ioctl() failed on TIOCSETP
This just happens on my iBook, the athlon box is fine.
I cannot see anything obviously fishy in the strace (attached)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. open a different terminal program
2. try to start xterm
xterm fails to start
Created attachment 113895 [details]
strace -tt -f -F -s 128 xterm
Please file a bug report in X.Org bugzilla to track this issue,
which is located at http://bugs.freedesktop.org in the "xorg" component.
Once you've filed your report to X.Org, if you paste the URL here,
Red Hat will track the issue in X.Org bugzilla with upstream developers,
and will review any fixes that become available for potential inclusion
in future Fedora Core updates.
Setting status to "NEEDINFO", awaiting upstream bug report URL.
Bug has been added to fdo bugzilla.
Thanks for the URL.
I've added http://freedesktop.org/bugzilla/show_bug.cgi?id=3212
to our internal tracker.
Setting status to "UPSTREAM" for tracking via Xorg bugzilla.
perhaps this (xterm patch #202):
ignore error in the I/O initialization that tries to set the tty to 7-bit input
for the case where eightBitInput resource is false (Debian #298551).
Well, setting 'XTerm*eightBitInput: true' magically makes xterm work again, so
it looks like we have a winner here. The only thing that puzzles me is that
(according to the man page) this should be the default setting.
The manpage documents what the upstream source does.
downstream packages may change this (though it would
be nice if they updated the manpage as well).
The eightBitInput resource is probably being set false
to appease users of Midnight Commander, who want the
Alt key to send an ESC. A similar effect can be obtained
using the metaSendsEscape resource.
*** Bug 158853 has been marked as a duplicate of this bug. ***