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

Bug#354278: uxterm only starts sometimes on Thinkpad



On Sat, 25 Feb 2006, Dan Jacobson wrote:

Package: xterm
Version: 6.8.2.dfsg.1-11
Severity: normal
File: /usr/X11R6/bin/uxterm

No idea why uxterm dies half a second after started in about 2/3rds on
invocations on Linux 2.6.12 on Thinkpad r50e. However, on Linux
2.6.14-2-k7 it starts every time.

nor I - I don't recall seeing a report like that.

$ xterm -class UXTerm -title uxterm -u8: same problem.

Anyways, on Thinkpad one must do
uxterm ^P RET uxterm ^P RET uxterm ^P RET several times until one
finally gets one that doesn't die at birth.

Yes, LANG=zh_TW.utf8, LC_CTYPE=zh_TW.utf8, which pulls in luit.

strace shows:
< --- SIGCHLD (Child exited) @ 0 (0) ---
< wait4(-1, NULL, 0, NULL)                = 6019
< rt_sigaction(SIGCHLD, {0x8074f00, [CHLD], SA_RESTART}, {0x8074f00,
[], SA_RESTART|SA_NOCLDSTOP}, 8) = 0
< kill(-6019, SIGHUP)                     = -1 ESRCH (No such process)
< access("/var/run/utmpx", F_OK)          = -1 ENOENT (No such file or
directory)

$ nice uxterm and even nice -n 0 uxterm do help somewhat I found.

By the way, the first two of the below must not be used, even if they
instead don't cause the above crash on birth.
$ c=zh_TW.Utf8 ;LC_CTYPE=$c LANG=$c LC_ALL=$c xterm -u8
Warning: locale not supported by Xlib, locale set to C
$ c=zh_TW.UTF8 ;LC_CTYPE=$c LANG=$c LC_ALL=$c xterm -u8
Warning: locale not supported by Xlib, locale set to C
$ c=zh_TW.utf8 ;LC_CTYPE=$c LANG=$c LC_ALL=$c xterm -u8
#uses luit .... and indeed the only way to see unicode

With #209, I'm not seeing a warning from any of those flavors.

Then "how dare" /usr/X11R6/bin/uxterm do
 value=`echo ${value} |sed -e 's/[.@].*//'`.UTF-8
when isn't lowercase .utf-8 right? locale -a seems to says so.

iirc, glibc converts the case (and other systems seem to generally use the uppercase). I've been using the values in /etc/locale.gen

Anyway, the
 Warning: locale not supported by Xlib, locale set to C
won't often be seen as the new window covers up the old.

that depends on the geometry settings (and window manager).

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net



Reply to: