Red Hat Bugzilla – Bug 138909
xinitrc bug causes kinput2 to be spawned twice
Last modified: 2010-10-21 22:41:22 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.3)
Description of problem:
Description of problem
When /etc/X11/xinit/xinitrc.d/xinput is executed by startx,
kinput2 is spawned twice. This makes one of two kinput2s to be killed.
If it's unfortunate, kinput2 which is connected to gnome-session is
and gnome cannot catch any keyboard input.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. set runlevel=3
2. login and type startx
3. sometimes, gnome will hang. (maybe on SMP system)
Actual Results: Sometimes, Gnome hangs
From the issue:
It seems that xinput just has debugging code. But It should be
removed, I think.
For the workaround, please comment out the following 4 lines from
if which $XIM_PROGRAM >/dev/null 2>&1 ; then
echo -n "XIM DEBUG: "
Adding to DesktopCustomerList
This one looks pretty trivial, is it something we can put on the 2.1U7
Hi Havoc-san, Steve-san,
Thank you for your help. Yes, this is pretty trivial, so the customer
had closed the IT ticket. However, if possible, I'd like you to fix
this problem for other CJK customers and me :-)
The changelog of xinitrc-3.22-1 says as follows,
* Tue Apr 09 2002 Mike A. Harris <firstname.lastname@example.org> 3.22-1
- Made changes for Leon (removed debugging code from xinput, etc)
--- xinput.org Thu Aug 23 01:29:23 2001
+++ xinput Fri Nov 12 22:17:54 2004
@@ -111,10 +111,6 @@
-# Nice temporary file vulnerability. If this is needed, use mkstemp
-# find what it was used for so I am clobbering it.
-#echo $PREFERRED > /tmp/start.txt
# set a proper XIM program with respect to $XIM
@@ -193,8 +189,3 @@
which $XIM_PROGRAM > /dev/null 2>&1 && LANG=$tmplang
$XIM_PROGRAM $XIM_ARGS &
-if which $XIM_PROGRAM >/dev/null 2>&1 ; then
- echo -n "XIM DEBUG: "
- $XIM_PROGRAM $XIM_ARGS&
Fix committed to CVS xinitrc-3.20.1 branched from 3.20 for RHEL 2.1.
Setting to MODIFIED state, pending QA, etc.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.