Description of problem:
On UTF-8 terminal (gnome-terminal, xterm or console) luit often hangs.
Sometimes it just says "Couldn't copy terminal settings".
Version-Release number of selected component (if applicable):
At least 2 in 3 tries.
Steps to Reproduce:
1. LANG=en_US.UTF-8 gnome-terminal
2. luit date
3. luit date
4. luit date
5. luit date
6. luit date
7. luit date
8. luit date
Fri Jul 23 18:36:00 CEST 2004
Fri Jul 23 18:36:24 CEST 2004
Couldn't copy terminal settings
Fri Jul 23 18:39:51 CEST 2004
Fri Jul 23 18:39:52 CEST 2004
Fri Jul 23 18:39:53 CEST 2004
Fri Jul 23 18:39:54 CEST 2004
Fri Jul 23 18:39:55 CEST 2004
Fri Jul 23 18:39:56 CEST 2004
Fri Jul 23 18:39:57 CEST 2004
1. FC1 version of luit works
2. When I've copied FC2 version of luit and libfontenc.so.1.0 to FC1
computer and used "LD_PRELOAD=./libfontenc.so.1.0 ./luit date" it also
Just checked on Fedora Core 3 Test 3 - it also hangs. Changing product
version to fc3test3.
Does this problem occur in Fedora Core 3 final release, with
all FC3 updates applied?
Yes, this problem occurs in FC3 with xorg-x11-6.8.1-12.FC3.21,
glibc-2.3.4-2.fc3 and kernel-2.6.10-1.770_FC3 (Pentium III, 192MB
RAM). It also occurs in Fedora Rawhide with xorg-x11-6.8.2-7,
glibc-2.3.4-14 and kernel-2.6.11-1.1177_FC4 (Celeron 2.4GHz, 256MB RAM).
Changed version to devel. Or maybe I should change it to FC3?
It is significant bug I think - luit is very usefull for launching
no-UTF-aware console programs in UTF locale. This includes for example
slrn, pine etc. (LC_ALL=pl_PL luit slrn).
Ok, please file a bug report in the X.Org bugzilla located at
http://bugs.freedesktop.org in the "xorg" component, which will increase
the number of developers aware of the problem, and maximize an
Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.
Setting status to "NEEDINFO", awaiting upstream bug URL for tracking.
There hasn't been any feedback on this bug in just over 2 months now,
and no response to my previous request in comment #4 to file the issue
in X.Org bugzilla so that the official maintainers of the software
are aware of the issue.
As such, it is assumed that the latest update fixes the issue or that
there is no further interest in tracking this problem, so I am closing
it as "ERRATA". If this is an incorrect assumption, please follow
the steps in comment #4 if you are still interested in seeing the
problem resolved, and we will track the problem in X.Org bugzilla
and will review any bug fixes that become available for consideration
in future updates.
Setting status to "ERRATA"
This bug is covered in XOrg/XFree86 bugzilla:
and no, it is not resolved upstream, but there is a proposed patch:
If I find some spare time I can try to compile xorg RPM with this patch and
check it. I do not have much time lately though.
Thanks for the update. The first comment of the upstream bug report points
back to another Red Hat bugzilla ID, bug #141992, which is on our "UPSTREAM"
This bug report is a duplicate of bug #141992, so I'm going to close it as
a dupe as we're already tracking http://bugs.freedesktop.org/show_bug.cgi?id=2443
There is a proposed patch, but it has not been reviewed or accepted into the
Xorg CVS yet. We will continue to monitor the upstream bug report periodically,
and once a decision has been made by X.Org, if the patch (or some other fix)
gets committed to CVS head, we will review it and flag it for inclusion in
the stable branch as well. Eventually it should appear in a future update.
Please use the X.Org bugzilla for any updates, so everything is tracked in
the central X.Org tracker from now on. Thanks again for pointing out the bug
*** This bug has been marked as a duplicate of 141992 ***
Adding reference to another upstream bug: