Discussion:
Multiple XWin.exe programs loading and no xterm
Scott Cegielski
2005-03-29 00:58:16 UTC
Permalink
Hello,
Please help. This is my first time trying to start X windows using cygwin
although I have been using cygwin for a while now. I am running it like this:

1. Open cygwin bash shell
2. Type startxwin.bat

The problem is that not much happens after that except that an X icon shows up
in the windows task bar. If I open the windows Task Manager, I can see that
there are two XWin.exe programs running. There is also an xterm.exe running,
although I cannot see it on my screen. I have tried killing one of the
XWin.exe processes, but the xterm never opens.

I have also tried startx from the cygwin shell. This produces the same results
described above, although it does print some information to the shell. Listed
below is a copy of this shell printout. Am I starting it the wrong way? I am
running this under Windows XP with service pack 2 installed. Any ideas? I
have seached the web and mailing list archive to try and find some answers for
this problem, but have found nothing. Thanks in advance for any help.

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.1.0-7
Contact: cygwin-***@cygwin.com
XWin was started with the following command line:
X :0 -multiwindow -clipboard
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
(II) XF86Config is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
(==) FontPath set to
"/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TT
F/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/
X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
winDetectSupportedEngines - Windows NT/2000/XP
winDetectSupportedEngines - DirectDraw installed
winDetectSupportedEngines - DirectDraw4 installed
winDetectSupportedEngines - Returning, supported engines 00000007
winSetEngine - Multi Window or Rootless => ShadowGDI
winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel
winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1024 depth: 32
winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32
null screen fn ReparentWindow
null screen fn RestackWindow
InitQueue - Calling pthread_mutex_init
InitQueue - pthread_mutex_init returned
InitQueue - Calling pthread_cond_init
InitQueue - pthread_cond_init returned
winInitMultiWindowWM - Hello
winMultiWindowXMsgProc - Hello
winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
winInitMultiWindowWM - Calling pthread_mutex_lock ()
MIT-SHM extension disabled due to lack of kernel support
XFree86-Bigfont extension local-client optimization disabled due to lack of
shar
ed memory support in the kernel
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: "00000409" (00000409)
(--) Using preset keyboard for "English (USA)" (409), type "4"
Rules = "xorg" Model = "pc105" Layout = "us" Variant = "(null)" Options =
"(null
)"
(EE) Couldn't load XKB keymap, falling back to pre-XKB keymap
(--) 16 mouse buttons found
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from
li
st!
winPointerWarpCursor - Discarding first warp: 640 512
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winProcEstablishConnection - Hello
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winInitMultiWindowWM - pthread_mutex_lock () returned.
winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0



Scott Cegielski
***@yahoo.com



__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Steven Boothe
2005-03-29 01:08:01 UTC
Permalink
Post by Scott Cegielski
Hello,
Please help. This is my first time trying to start X windows using cygwin
1. Open cygwin bash shell
2. Type startxwin.bat
Try typing startx at the command line. What happens then?
Alexander Gottwald
2005-03-29 11:09:10 UTC
Permalink
Post by Scott Cegielski
Hello,
Please help. This is my first time trying to start X windows using cygwin
1. Open cygwin bash shell
2. Type startxwin.bat
The problem is that not much happens after that except that an X icon shows up
in the windows task bar. If I open the windows Task Manager, I can see that
there are two XWin.exe programs running. There is also an xterm.exe running,
although I cannot see it on my screen. I have tried killing one of the
XWin.exe processes, but the xterm never opens.
Do you have ZoneAlarm or other Personal Firewalls or Live Virusscanners installed?
The interfere with the cygwin network handling and will break Cygwin/X.

bye
ago
--
***@s1999.tu-chemnitz.de
http://www.gotti.org ICQ: 126018723
Scott Cegielski
2005-03-29 17:44:47 UTC
Permalink
I did also try startx. Please see my original email for the output of startx.
thanks
Post by Steven Boothe
Post by Scott Cegielski
Hello,
Please help. This is my first time trying to start X windows using cygwin
although I have been using cygwin for a while now. I am running it like
1. Open cygwin bash shell
2. Type startxwin.bat
Try typing startx at the command line. What happens then?
Scott Cegielski
***@yahoo.com





__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Armbrust, Daniel C.
2005-03-29 22:59:19 UTC
Permalink
This happens to me all the time - I usually have to launch the X stuff 2 or 3 times before it actually works.

I have to manually kill off all xterm.exe, bash.exe, and other cygwin programs in between the launches. I keep meaning to look into it more, but since I start it less than once a week, I haven't had enough incentive to dig deeper yet.

I just set up cygwin on another machine this week, and it suffers the same problem.

Dan
Jack Tanner
2005-03-30 00:12:39 UTC
Permalink
Post by Armbrust, Daniel C.
This happens to me all the time - I usually have to launch the X stuff 2 or 3 times before it actually works.
I have to manually kill off all xterm.exe, bash.exe, and other cygwin programs in between the launches. I keep meaning to look into it more, but since I start it less than once a week, I haven't had enough incentive to dig deeper yet.
I guess I'm not alone. I've managed to solve this problem with the
following hack: I add a "pause" command to the end of startxwin.bat. I
forget why I tried this, but it works.
Scott Cegielski
2005-03-30 04:34:16 UTC
Permalink
For me, putting a pause at the end of startxwin.bat does not make it work.
However, I have found something that does seem to work for me. When I launch
statxwin.bat, in addition to the 2 XWin.exe processes, there is also a sh.exe
process that starts which I assume is from the MS-DOS shell that the .bat is
run from. Even though the shell window closes after the script finishes, the
sh.exe process is still running. If I open the task manger and end the sh.exe
process, the xterm pops open and the extra XWin.exe goes away. Does anyone
know why this sh.exe process whould linger around or how to kill it without
having to open the task manager and mouse to it every time?
Post by Armbrust, Daniel C.
Post by Armbrust, Daniel C.
This happens to me all the time - I usually have to launch the X stuff 2 or
3 times before it actually works.
Post by Armbrust, Daniel C.
I have to manually kill off all xterm.exe, bash.exe, and other cygwin
programs in between the launches. I keep meaning to look into it more, but
since I start it less than once a week, I haven't had enough incentive to dig
deeper yet.
I guess I'm not alone. I've managed to solve this problem with the
following hack: I add a "pause" command to the end of startxwin.bat. I
forget why I tried this, but it works.
Scott Cegielski
***@yahoo.com



__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Alexander Gottwald
2005-03-30 09:17:07 UTC
Permalink
Post by Scott Cegielski
For me, putting a pause at the end of startxwin.bat does not make it work.
However, I have found something that does seem to work for me. When I launch
statxwin.bat, in addition to the 2 XWin.exe processes, there is also a sh.exe
process that starts which I assume is from the MS-DOS shell that the .bat is
run from. Even though the shell window closes after the script finishes, the
sh.exe process is still running. If I open the task manger and end the sh.exe
process, the xterm pops open and the extra XWin.exe goes away. Does anyone
know why this sh.exe process whould linger around or how to kill it without
having to open the task manager and mouse to it every time?
This is from the xkbcomp call. Add -kb to the xwin commandline and it will not be
started but the keyboard layout will be us only.

bye
ago
--
***@s1999.tu-chemnitz.de
http://www.gotti.org ICQ: 126018723
Armbrust, Daniel C.
2005-03-30 22:37:02 UTC
Permalink
The -kb command helped with one of my machines that was having intermittent difficulties in launching.



On another machine, however, I always have to execute the following script twice before I get any Xwin windows:


--CUT--
All of the standard startXWin.bat environment setup stuff...
--CUT--

run XWin -multiwindow -clipboard -silent-dup-error -kb
run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash -l
run xterm -geometry 80x50-0-0 -sl 500 -sb -rightbar -e ssh -Y ***@some.server


The first time that I run it - Xwin.exe and two xterm.exe's appear in the process manager - then both xterm's disappear. Eventually the X finally appears in the lower right corner.

Then I run the script again, and this time the xterms actually launch.

Here is the log file from the first launch:

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.2.0-1

Contact: cygwin-***@cygwin.com

XWin was started with the following command line:

/usr/X11R6/bin/XWin -multiwindow -clipboard -silent-dup-error
-kb

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1280 h 1024
winInitializeDefaultScreens - Returning
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
(II) XF86Config is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
(==) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel
winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1024 depth: 32
winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32
null screen fn ReparentWindow
null screen fn RestackWindow
InitQueue - Calling pthread_mutex_init
InitQueue - pthread_mutex_init returned
InitQueue - Calling pthread_cond_init
InitQueue - pthread_cond_init returned
winInitMultiWindowWM - Hello
winMultiWindowXMsgProc - Hello
winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
winInitMultiWindowWM - Calling pthread_mutex_lock ()
MIT-SHM extension disabled due to lack of kernel support
XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: "00000409" (00000409)
(--) Using preset keyboard for "English (USA)" (409), type "4"
(++) XkbExtension disabled
(--) 3 mouse buttons found
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winInitMultiWindowWM - pthread_mutex_lock () returned.
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winProcEstablishConnection - Hello
winInitClipboard ()
winProcEstablishConnection - winInitClipboard returned.
winClipboardProc - Hello
DetectUnicodeSupport - Windows NT/2000/XP
winClipboardProc - DISPLAY=127.0.0.1:0.0
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display.
winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display.
winClipboardProc - XOpenDisplay () returned and successfully opened the display.


Does this shed any light on things?

Thanks,

Dan
Alexander Gottwald
2005-03-31 09:09:48 UTC
Permalink
Post by Armbrust, Daniel C.
The -kb command helped with one of my machines that was having intermittent difficulties in launching.
run XWin -multiwindow -clipboard -silent-dup-error -kb
run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash -l
The first time that I run it - Xwin.exe and two xterm.exe's appear in the process manager - then both xterm's disappear. Eventually the X finally appears in the lower right corner.
This means XWin is taking very long to startup. Maybe because of a virus scanner?
The xterms will timeout after no connection to the xserver could be established.
The second xserver will notice the first one and will silently exit but now the
xterms can connect to the first xserver.

Adding a sleep after run XWin might help by postponing the xterm startup.

bye
ago
--
***@s1999.tu-chemnitz.de
http://www.gotti.org ICQ: 126018723
Scott Cegielski
2005-03-31 02:44:18 UTC
Permalink
For me, adding -kb to the xwin command did work. Thanks much for the help.
Post by Armbrust, Daniel C.
The -kb command helped with one of my machines that was having intermittent
difficulties in launching.
On another machine, however, I always have to execute the following script
--CUT--
All of the standard startXWin.bat environment setup stuff...
--CUT--
run XWin -multiwindow -clipboard -silent-dup-error -kb
run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e
/usr/bin/bash -l
run xterm -geometry 80x50-0-0 -sl 500 -sb -rightbar -e ssh -Y
The first time that I run it - Xwin.exe and two xterm.exe's appear in the
process manager - then both xterm's disappear. Eventually the X finally
appears in the lower right corner.
Then I run the script again, and this time the xterms actually launch.
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.2.0-1
/usr/X11R6/bin/XWin -multiwindow -clipboard -silent-dup-error
-kb
ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1280 h 1024
winInitializeDefaultScreens - Returning
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be
created.
(II) XF86Config is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
(==) FontPath set to
"/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
Post by Armbrust, Daniel C.
winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per
pixel
winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1024 depth: 32
winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp
32
null screen fn ReparentWindow
null screen fn RestackWindow
InitQueue - Calling pthread_mutex_init
InitQueue - pthread_mutex_init returned
InitQueue - Calling pthread_cond_init
InitQueue - pthread_cond_init returned
winInitMultiWindowWM - Hello
winMultiWindowXMsgProc - Hello
winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
winInitMultiWindowWM - Calling pthread_mutex_lock ()
MIT-SHM extension disabled due to lack of kernel support
XFree86-Bigfont extension local-client optimization disabled due to lack of
shared memory support in the kernel
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: "00000409" (00000409)
(--) Using preset keyboard for "English (USA)" (409), type "4"
(++) XkbExtension disabled
(--) 3 mouse buttons found
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from
list!
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winInitMultiWindowWM - pthread_mutex_lock () returned.
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winProcEstablishConnection - Hello
winInitClipboard ()
winProcEstablishConnection - winInitClipboard returned.
winClipboardProc - Hello
DetectUnicodeSupport - Windows NT/2000/XP
winClipboardProc - DISPLAY=127.0.0.1:0.0
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the
display.
winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the
display.
winClipboardProc - XOpenDisplay () returned and successfully opened the
display.
Does this shed any light on things?
Thanks,
Dan
Scott Cegielski
***@yahoo.com



__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Scott Cegielski
2005-03-31 16:37:42 UTC
Permalink
I'm just trying to understand this even though it works for me now. Why are
two X servers launching in the first place?
Post by Armbrust, Daniel C.
Post by Armbrust, Daniel C.
The -kb command helped with one of my machines that was having intermittent
difficulties in launching.
Post by Armbrust, Daniel C.
On another machine, however, I always have to execute the following script
run XWin -multiwindow -clipboard -silent-dup-error -kb
run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e
/usr/bin/bash -l
Post by Armbrust, Daniel C.
run xterm -geometry 80x50-0-0 -sl 500 -sb -rightbar -e ssh -Y
The first time that I run it - Xwin.exe and two xterm.exe's appear in the
process manager - then both xterm's disappear. Eventually the X finally
appears in the lower right corner.
This means XWin is taking very long to startup. Maybe because of a virus
scanner?
The xterms will timeout after no connection to the xserver could be
established.
The second xserver will notice the first one and will silently exit but now
the
xterms can connect to the first xserver.
Adding a sleep after run XWin might help by postponing the xterm startup.
bye
ago
--
http://www.gotti.org ICQ: 126018723
Scott Cegielski
***@yahoo.com





__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Armbrust, Daniel C.
2005-03-31 16:49:16 UTC
Permalink
Because I execute the entire script twice, since the first execution doesn't bring up any xterms.

Still not sure what is causing it to take so long to launch the xwin.exe.

Can I set the timeout values on the xterm's with a flag?

Dan


-----Original Message-----
From: cygwin-xfree-***@cygwin.com [mailto:cygwin-xfree-***@cygwin.com] On Behalf Of Scott Cegielski
Sent: Thursday, March 31, 2005 10:38 AM
To: cygwin-***@cygwin.com
Subject: RE: Multiple XWin.exe programs loading and no xterm

I'm just trying to understand this even though it works for me now. Why are
two X servers launching in the first place?
Post by Armbrust, Daniel C.
Post by Armbrust, Daniel C.
The -kb command helped with one of my machines that was having intermittent
difficulties in launching.
Post by Armbrust, Daniel C.
On another machine, however, I always have to execute the following script
run XWin -multiwindow -clipboard -silent-dup-error -kb
run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e
/usr/bin/bash -l
Post by Armbrust, Daniel C.
run xterm -geometry 80x50-0-0 -sl 500 -sb -rightbar -e ssh -Y
The first time that I run it - Xwin.exe and two xterm.exe's appear in the
process manager - then both xterm's disappear. Eventually the X finally
appears in the lower right corner.
This means XWin is taking very long to startup. Maybe because of a virus
scanner?
The xterms will timeout after no connection to the xserver could be
established.
The second xserver will notice the first one and will silently exit but now
the
xterms can connect to the first xserver.
Adding a sleep after run XWin might help by postponing the xterm startup.
bye
ago
--
http://www.gotti.org ICQ: 126018723
Scott Cegielski
***@yahoo.com





__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Alexander Gottwald
2005-03-31 18:10:24 UTC
Permalink
Post by Armbrust, Daniel C.
Because I execute the entire script twice, since the first execution doesn't bring up any xterms.
Still not sure what is causing it to take so long to launch the xwin.exe.
Can I set the timeout values on the xterm's with a flag?
no. Use sleep to delay starting the xterms

bye
ago
--
***@s1999.tu-chemnitz.de
http://www.gotti.org ICQ: 126018723
Scott Cegielski
2005-03-31 17:40:47 UTC
Permalink
I wasn'y reffering to your situation specifically. Even when the script is not
executed twice, two Xwin.exe processes launch. That is what I described in the
first post of this thread. As I learned, adding the -kb flag makes the second
Xwin.exe die shortly after the initial launch, but my question is why two are
loading in the first place.
Post by Armbrust, Daniel C.
Because I execute the entire script twice, since the first execution doesn't
bring up any xterms.
Still not sure what is causing it to take so long to launch the xwin.exe.
Can I set the timeout values on the xterm's with a flag?
Dan
-----Original Message-----
Behalf Of Scott Cegielski
Sent: Thursday, March 31, 2005 10:38 AM
Subject: RE: Multiple XWin.exe programs loading and no xterm
I'm just trying to understand this even though it works for me now. Why are
two X servers launching in the first place?
Post by Armbrust, Daniel C.
Post by Armbrust, Daniel C.
The -kb command helped with one of my machines that was having
intermittent
Post by Armbrust, Daniel C.
difficulties in launching.
Post by Armbrust, Daniel C.
On another machine, however, I always have to execute the following
script
Post by Armbrust, Daniel C.
Post by Armbrust, Daniel C.
run XWin -multiwindow -clipboard -silent-dup-error -kb
run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e
/usr/bin/bash -l
Post by Armbrust, Daniel C.
run xterm -geometry 80x50-0-0 -sl 500 -sb -rightbar -e ssh -Y
The first time that I run it - Xwin.exe and two xterm.exe's appear in the
process manager - then both xterm's disappear. Eventually the X finally
appears in the lower right corner.
This means XWin is taking very long to startup. Maybe because of a virus
scanner?
The xterms will timeout after no connection to the xserver could be
established.
The second xserver will notice the first one and will silently exit but now
the
xterms can connect to the first xserver.
Adding a sleep after run XWin might help by postponing the xterm startup.
bye
ago
--
http://www.gotti.org ICQ: 126018723
Scott Cegielski
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Scott Cegielski
***@yahoo.com





__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
Alexander Gottwald
2005-03-31 18:09:23 UTC
Permalink
Post by Scott Cegielski
I wasn'y reffering to your situation specifically. Even when the script is not
executed twice, two Xwin.exe processes launch. That is what I described in the
first post of this thread. As I learned, adding the -kb flag makes the second
Xwin.exe die shortly after the initial launch, but my question is why two are
loading in the first place.
The XKB extension calls xkbcomp (an external program). This is done via fork. This
means for a short time there are two XWin processes but one of them is transformed
into an xkbcomp process later (check unix semantics for fork and exec for details).
In some cases (textmode mounted /tmp, Personal firewalls and virus scanners) break
the fork/exec calls. BTW: I've not heard any definitive answer if you have any of
the above mentiond programs running.
Disabling the XKB extension will result in not calling xkbcomp, so the lock disappears.

bye
ago
--
***@s1999.tu-chemnitz.de
http://www.gotti.org ICQ: 126018723
Loading...