Red Hat Bugzilla – Bug 159562
xterm fails to start properly - ioctl() failed on TIOCSETP
Last modified: 2007-11-30 17:11:07 EST
+++ This bug was initially created as a clone of Bug #101472 +++
Please fill in each of the sections below.
Hardware Environment: iSeries 64bit
Software Environment: RHEL 3 Beta 1
Steps to Reproduce:
1. Attempt to start an xterm on a RHEL 3 Beta 1 system.
The following error is reported:
[root@rchlp530 mnt]# xterm
xterm: Error 23, errno 22: Invalid argument
Reason: spawn: ioctl() failed on TIOCSETP
I expected xterm to start.
I have recreated this same result when trying to export the display, with the
display forwarded over an ssh connection and within a VNC session running on the
The original bug was fixed long ago but the patch was recently removed from
Fedora's xterm package -- with a comment about testing to see whether it was
still necessary, but evidently without any such testing.
(In reply to comment #1)
> The original bug was fixed long ago but the patch was recently removed from
> Fedora's xterm package -- with a comment about testing to see whether it was
> still necessary, but evidently without any such testing.
You misunderstood the comment. I removed the patch because it no longer
applied, and it wasn't clear if it was still necessary or not. The
"testing" was not manual testing by myself, but testing by the community.
Nobody reported a problem until now, so the "testing" so far done by
the community did not yield results showing that it was still a problem
for PPC users.
This underscores the importance of end users testing things earlier, and
then reporting any bugs found directly to the upstream maintainers and
projects, so that fixes get incorporated directly into the official
sources, and do not need to be custom ported forward to each new
Once a patch that fixes this problem has been incorporated into upstream
xterm, and the new xterm released, we will add the patch to a future FC4
xterm update after it's had testing in rawhide for a while.
Thanks in advance.
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).
According to upstream maintainer, this bug is fixed by this code in main.c,
/* ignore errors here - some platforms don't work */
tio.c_cflag &= ~CSIZE;
tio.c_cflag |= CS8;
tio.c_cflag |= CS7;
(void) ttySetAttr(ttyfd, &tio);
Which is in xterm-205 submitted to rawhide-20051013. I cannot reproduce this
bug with this version. After a week or so of testing in rawhide, I'll submit
xterm-205 to FC-4 .
From User-Agent: XML-RPC
xterm-205-1.FC4 has been pushed for FC4, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.