#230787 xterm: dies when kinput2 (XIM) process is killed

Package:
libx11-6
Source:
libx11
Description:
X11 client-side library
Submitter:
Rauli Ruohonen
Date:
2015-04-18 08:09:11 UTC
Severity:
important
#230787#5
Date:
2004-02-02 14:32:15 UTC
From:
To:
When using kinput2 with xterm, if kinput2 is killed, xterm dies, too.
Very undesirable, as kinput2 needs to be restarted when its
configuration options are changed. GTK2 programs work fine with kinput2
restarts, so xterm should, too.

#230787#14
Date:
2004-07-15 17:31:08 UTC
From:
To:
retitle 230787 xterm: dies when kinput2 (XIM) process is killed
severity 230787 important
tag 230787 + moreinfo upstream
thanks

The current version of XTerm in Debian testing ("sarge") is XTerm #187
(2004-04-27).

The current version of XTerm in Debian unstable ("sid") is XTerm #190
(2004-05-25).

Can you still reproduce this problem?

#230787#17
Date:
2004-07-18 16:12:36 UTC
From:
To:
I tried to reproduce the problem today but could not.  (If it's still a bug,
I'll need more information about the environment, procedure, etc).

#230787#22
Date:
2004-07-24 02:25:03 UTC
From:
To:
This was harder to reproduce than I expected. I thought it'd always
happen, but that's not true (I just tried xterm briefly, noticed a
problem, and went back to using gnome-terminal). I haven't checked how XIM
works, but apparently you need to have sent some request to kinput2,
after which kinput2 has to die before responding, and *then* the client
application freezes. When I said xterm "dies", I was being unclear.. It
doesn't exit.

A way to reproduce this for all X apps I tested:

1. kill -STOP <kinput2pid>
2. freeze application xyzzy by causing it to use XIM
3a. if you still wish to use the app, kill -CONT <kinput2pid>
3b. otherwise, kill -9 <kinput2pid>. Prepare to kill -9 the app, too.
     Nothing seems to help at this point. If you strace the app, you'll
     see that it does selects, reads, etc. to get X events, but some of
     those reads just return EAGAIN, even if that doesn't normally happen.
     EAGAIN isn't supposed to be a fatal error, but a kill -9:ed process
     won't ever be responding again, now will it? :-)

The difference between gnome-terminal and xterm is that it only takes one
keystroke in step 2 to temporarily freeze xterm, while gnome-terminal
requires pressing shift-space (the conversion mode switch key).

The way to freeze xterm without kill -STOPping kinput2:

1. Start kinput2.
2. Start a new xterm.
3. Type "kill <kinput2pid>" in the xterm and press enter.
4. If you're lucky (and I seem to always be), xterm is now permanently frozen.
    Probably because of the final enter key press..

The right thing to do would IMHO be to fix XIM usage, or XIM itself if
this is an inherent problem, but I've no idea if this is feasible. At
least xterm is not alone in this. Not routing everything through XIM would
be one "solution", but is it really better than just saying "Don't Do
That, Then"? Dunno, really.. Would seem like an ugly workaround to me.
Programs just shouldn't freeze (semi)permanently if a XIM server dies or
is kill -STOPped. OTOH, XIM has its flaws, and some people are working on
a replacement.. (see iimf)

As you can avoid problems just by being careful to restart kinput2 from a
non-XIM-using terminal, this is just a mild annoyance. In any case, if it
isn't fixed in some fashion, it should probably be documented in the BUGS
section on the man page.

#230787#25
Date:
2004-07-24 14:03:25 UTC
From:
To:
yes - when I tried it, I wasn't in the middle of a request, but only had
verified that XIM was talking to xterm.

thanks (there's lots of details here - seems enough for me to do the same)

#230787#32
Date:
2011-12-29 01:09:05 UTC
From:
To:
I spent some time studying this and came to the conclusion that the
hanging is within the X11 library, in the (potentially) infinite loop
in _XimRead.  The bug should be reassigned to libx11-6

(I'll document the problem in xterm's manpage, as well).

#230787#35
Date:
2011-12-29 01:09:05 UTC
From:
To:
I spent some time studying this and came to the conclusion that the
hanging is within the X11 library, in the (potentially) infinite loop
in _XimRead.  The bug should be reassigned to libx11-6

(I'll document the problem in xterm's manpage, as well).

#230787#44
Date:
2015-04-18 08:06:15 UTC
From:
To:
Herzlichen Gruß,

die Arbeitsvermittlung stellt Ihnen nachfolgend eine interessante Tätigkeit in einem internationalen Team von zu Hause aus vor, ohne Fahrtkosten, ohne Anfahrt, ohne Verkehrsstress:

Wir bieten qualifizierte und attraktive Stellen auch in ländlichen Regionen im ganzen europäischen Raum und bieten gleichzeitig hochwertige Qualität für unsere Auftraggeber.

Ab sofort sind nachfolgende Stellen frei:
Mitarbeiter (m/w) für den Support im Home Office in der Abteilung Office und Kommunikation

Ihre Tätigkeitsschwerpunkte wären:

- Dokumente empfangen, bearbeiten und weiterleiten
- Dokumente einscannen/kopieren
- Mails bearbeiten
- Arbeit im Home Office in freien Zeiteinteilung
- Umgang mit zur Verfügung gestellten Systemen

Anforderungen an Sie:

- Problemloser Umgang mit Email, PC und Internet
- Deutsch fließend, Fremdsprachen wären von Vorteil
- kundenorientiertes Teamwork
- Genauigkeit und Zielstrebigkeit

Wir bieten Ihnen eine Stelle als Festangestellter oder als Selbständige mit einem Stundenlohn von 20 Euro Brutto in der Stunde in selbständigen Arbeitsweise und einer modernen Beschäftigungsform, sowie eine abwechslungsreiche Tätigkeit ohne Fahrzeit mit flexiblen Arbeitszeiten.

Es werden keine Fachkenntnisse vorausgesetzt. Die Einarbeitung findet schrittweise durch professionelle Mitarbeiten statt. Die nötige technische Ausstattung stellen wir Ihnen ohne weitere Kosten zur Verfügung. Die Stelle kann gerne nebenberuflich aufgenommen werden sowie von Rentnern und Hausfrauen.

Sie sind offen für flexible Arbeitszeitmodelle und die Arbeit im Home-office? Wenn wir Ihr Interesse geweckt haben, senden Sie uns Ihre Bewerbung per E-Mail an: ABORI1332@acdcfan.com


Wir freuen uns auf Ihre Bewerbung.

Es grüßt Sie Ihre

Hoffmann SA