Re: XWin hangs on opening xterms: Conflict with software FRITZ!DSL Startcenter

2005-10-24 Thread Norbert HArendt
Jack Tanner  hotmail.com> writes:

> Norbert Harendt wrote:
> >>Could it be a firewall of some sort? 
> > 
> > It is a kind of firewall used with german DSL-router
> 
> Cygwin/X is known to conflict with some software firewalls, like 
> ZoneAlarm, even if they are only installed and not running. It works 
> fine, however, with the Windows XP SP2 Personal Firewall. You may just 
> have to uninstall the Fritz software. Perhaps you could use a hardware 
> firewall built into a router like a Linksys WRT54G instead of the Fritz one.

Thanks for your hints. I tried out a similar strategy. I uninstalled the Fritz
software and installed agnitum firewall, now Cygwin/X is running fine. In
parallel i contacted AVM (the vendor of Fritz software) and informed them of the
malfunction. Perhaps one day in future i can use fritz software again ...



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: XWin hangs on opening xterms: Conflict with software FRITZ!DSL Startcenter

2005-10-24 Thread Norbert Harendt
Jack Tanner  hotmail.com> writes:

> $ strings sh.exe | grep dll
> dll_crt0__FP11per_process
> cygwin1.dll
> cygintl-3.dll
> cygreadline6.dll
> KERNEL32.dll
> 
> Could it be that the FRITZ!DSL software somehow inserts itself into the 
> loading process? 
Yes, i think so

> Could it be a firewall of some sort? 
It is a kind of firewall used with german DSL-router

> Can you play with 
> not loading the FRITZ stuff (without uninstalling it), and running Xwin 
> then?
Yes, i tried, but XWin showed the same failure





--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: XWin hangs on opening xterms: Conflict with software FRITZ!DSL Startcenter

2005-10-21 Thread Norbert Harendt
Larry Hall (Cygwin X  cygwin.com> writes:

> 
> Norbert Harendt wrote:
> > Larry Hall (Cygwin X  cygwin.com> writes:
> > 
> > 
> >>On 10/11/2005, Norbert Harendt wrote:
> >>
> >>>OK. What i can see, is that calling or running the shell causes the 
> >>>problems in my case. XWin is coming up and running fine, i get the logon 
> >>>screen of the remote server and everything seems to be fine. But if i try 
> >>>to open an xterm on the remote server, XWin seems to hang, no grafical 
> >>>update, nothing happens (with enough patience you can watch this going on 
> >>>forever). When i kill the second XWin.exe suddenly the xterm appears and 
> >>>everything is working fine again, except for the heavy cpu-load, which was 
> >>>not present in my former installation.
> >>
> >>Perhaps it makes sense to look at why you have a second XWin running.
> >>
> > 
> > 
> > 
> > OK. I don't know at that time, why there is a second XWin.exe starting. Yes
> > i also think, that this is the clue to the problem. The start of the 
> > second XWin.exe must happen internally, because the script starting 
> >XWin -clipboard -lesspointer -query 192.168.1.100 -once
> > calls XWin.exe only once. At the time of the program call is no other 
XWin.exe
> > running. Is there a possibility to view what is happening internally,
 extended
> > logging features or somethins else ??
> 
> I don't know.  But perhaps it's better to come at this from the other
> direction.  If you can provide a small test case/script that reproduces the
> problem for you, then others on the list could verify whether or not they
> see the same problem.
> 


I opened /bin/sh.exe with Microsoft Visual C++ in order to see, which
DLLs will be loaded on startup of sh.exe, the complete list follows:
"Q:\progs.win\cygwin\bin\sh.exe" wurde geladen. 
"C:\WINNT\system32\ntdll.dll" wurde geladen. 
"Q:\progs.win\cygwin\bin\cygwin1.dll" wurde geladen. 
"C:\WINNT\system32\advapi32.dll" wurde geladen. 
"C:\WINNT\system32\kernel32.dll" wurde geladen. 
"C:\WINNT\system32\rpcrt4.dll" wurde geladen. 
"Q:\progs.win\cygwin\bin\cygintl-3.dll" wurde geladen. 
"Q:\progs.win\cygwin\bin\cygiconv-2.dll" wurde geladen. 
"Q:\progs.win\cygwin\bin\cygreadline6.dll" wurde geladen. 
"Q:\progs.win\cygwin\bin\cygncurses-8.dll" wurde geladen. 
"C:\WINNT\system32\user32.dll" wurde geladen. 
"C:\WINNT\system32\gdi32.dll" wurde geladen. 
cYg 610EC77CcYgstd 22eeb0 d 3"C:\WINNT\system32\wsock32.dll" wurde
geladen. 
"C:\WINNT\system32\ws2_32.dll" wurde geladen. 
"C:\WINNT\system32\msvcrt.dll" wurde geladen. 
"C:\WINNT\system32\ws2help.dll" wurde geladen. 
"C:\WINNT\system32\winrnr.dll" wurde geladen. 
"C:\WINNT\system32\wldap32.dll" wurde geladen. 
"C:\Programme\FRITZ!DSL\SARAH.DLL" wurde geladen. 
"C:\WINNT\system32\msvcr71.dll" wurde geladen. 
"C:\Programme\FRITZ!DSL\BLOCK.DLL" wurde geladen. 
"C:\Programme\FRITZ!DSL\Avmcsock.dll" wurde geladen. 
"C:\Programme\FRITZ!DSL\AVMUFC.DLL" wurde geladen. 
"C:\WINNT\system32\MFC71.DLL" wurde geladen. 
"C:\WINNT\system32\shlwapi.dll" wurde geladen. 
"C:\WINNT\system32\comctl32.dll" wurde geladen. 
"C:\WINNT\system32\rnr20.dll" wurde geladen. 
"C:\WINNT\system32\dnsapi.dll" wurde geladen. 
"C:\WINNT\system32\iphlpapi.dll" wurde geladen. 
"C:\WINNT\system32\icmp.dll" wurde geladen. 
"C:\WINNT\system32\mprapi.dll" wurde geladen. 
"C:\WINNT\system32\samlib.dll" wurde geladen. 
"C:\WINNT\system32\netapi32.dll" wurde geladen. 
"C:\WINNT\system32\secur32.dll" wurde geladen. 
"C:\WINNT\system32\netrap.dll" wurde geladen. 
"C:\WINNT\system32\ole32.dll" wurde geladen. 
"C:\WINNT\system32\oleaut32.dll" wurde geladen. 
"C:\WINNT\system32\activeds.dll" wurde geladen. 
"C:\WINNT\system32\adsldpc.dll" wurde geladen. 
"C:\WINNT\system32\rtutils.dll" wurde geladen. 
"C:\WINNT\system32\setupapi.dll" wurde geladen. 
"C:\WINNT\system32\userenv.dll" wurde geladen. 
"C:\WINNT\system32\rasapi32.dll" wurde geladen. 
"C:\WINNT\system32\rasman.dll" wurde geladen. 
"C:\WINNT\system32\tapi32.dll" wurde geladen. 
"C:\WINNT\system32\dhcpcsvc.dll" wurde geladen. 

I was astonished to find the entries
"C:\Programme\FRITZ!DSL\DLL", so i tried to run XWin on a computer in our
network which hasn't FRITZ!DSL-software, and ... it was running without any
error or hang !!
There a two computers with FRITZ!DSL-software on it, and on both XWin 
and sh.exe hang on execution.

So i identified the third-party conflict with FRITZ!DSL startcenter 
(www.avm.de). What can i do now (except of deinstalling the 
FRITZ!DSL software ??


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: XWin hangs on opening xterms, correspondence with setup hangs ??

2005-10-12 Thread Norbert Harendt
Larry Hall (Cygwin X  cygwin.com> writes:

> 
> Norbert Harendt wrote:
> > Larry Hall (Cygwin X  cygwin.com> writes:
> > 
> > 
> >>On 10/11/2005, Norbert Harendt wrote:
> >>
> >>>OK. What i can see, is that calling or running the shell causes the 
> >>>problems in my case. XWin is coming up and running fine, i get the logon 
> >>>screen of the remote server and everything seems to be fine. But if i try 
> >>>to open an xterm on the remote server, XWin seems to hang, no grafical 
> >>>update, nothing happens (with enough patience you can watch this going on 
> >>>forever). When i kill the second XWin.exe suddenly the xterm appears and 
> >>>everything is working fine again, except for the heavy cpu-load, which 
> >>>was not present in my former installation.
> >>
> >>Perhaps it makes sense to look at why you have a second XWin running.
> >>
> > 
> > 
> > 
> > OK. I don't know at that time, why there is a second XWin.exe starting. 
> > Yes i also think, that this is the clue to the problem. The start of the 
> > second XWin.exe must happen internally, because the script starting 
> >XWin -clipboard -lesspointer -query 192.168.1.100 -once
> > calls XWin.exe only once. At the time of the program call is no other 
XWin.exe
> > running. Is there a possibility to view what is happening internally, 
extended
> > logging features or somethins else ??
> 
> I don't know.  But perhaps it's better to come at this from the other
> direction.  If you can provide a small test case/script that reproduces the
> problem for you, then others on the list could verify whether or not they
> see the same problem.
> 


That is very simple, i start cygwin calling
   bin\bash --login -i
Inside bash i call
   XWin -clipboard -lesspointer -query 192.168.1.100 -once
and that's all. 

Using my former installation of cygwin from that point on everything happend
without problems. I used Cygwin/X-window as the local display server for
the remote applications on our linux-server. And this changed with the
update of the local cygwin installation:

What is now happening is also described in the former postings:
the Cygwin/X-window opens and freezes just upon opening, so you can see 
only the frame of the window, but not the inside, which doesn't change 
even with much much patience. 
So, when i kill the second XWin.exe (which appears out of nowhere, i didn't 
call it!) in the task manager, the inside of the Cygwin/X-window fills as 
it should be: the login screen of our linux-server appears and everything 
is running fine, as if nothing unusal happened. 

I can login and open applications on the remote server sending their output 
to the Cygwin/X-window as it should be. But every time i start an xterm the 
Cygwin/X-window freezes again, without showing the xterm, and this doesn't 
change even with much patience. So after killing the second XWin.exe, which
seemingly was started by the call of the xterm, the Cygwin/X-window behaves
as usual: xterm window appears and Cygwin/X-window is fully functional (..
until the next call of xterm).

But i also encounter problems running cygwins setup.exe: when it comes to the
postinstalls, setup also hangs, because the envoced shells freeze on starting.
So i think, the real problem is the way shells are started in the actual 
version of cygwin.




--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: XWin hangs on opening xterms, correspondence with setup hangs ??

2005-10-12 Thread Norbert Harendt
Larry Hall (Cygwin X  cygwin.com> writes:

> 
> On 10/11/2005, Norbert Harendt wrote:
> > OK. What i can see, is that calling or running the shell causes the 
> > problems in my case. XWin is coming up and running fine, i get the logon 
> > screen of the remote server and everything seems to be fine. But if i try 
> > to open an xterm on the remote server, XWin seems to hang, no grafical 
> > update, nothing happens (with enough patience you can watch this going on 
> > forever). When i kill the second XWin.exe suddenly the xterm appears and 
> > everything is working fine again, except for the heavy cpu-load, which was 
> > not present in my former installation.
> 
> Perhaps it makes sense to look at why you have a second XWin running.
> 


OK. I don't know at that time, why there is a second XWin.exe starting. Yes
i also think, that this is the clue to the problem. The start of the 
second XWin.exe must happen internally, because the script starting 
   XWin -clipboard -lesspointer -query 192.168.1.100 -once
calls XWin.exe only once. At the time of the program call is no other XWin.exe
running. Is there a possibility to view what is happening internally, extended
logging features or somethins else ??


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: XWin hangs on opening xterms, correspondence with setup hangs ??

2005-10-11 Thread Norbert Harendt
Christopher Faylor  cygwin.com> writes:

> 
> On Mon, Oct 10, 2005 at 09:41:00AM +, Norbert Harendt wrote:
> >Norbert Harendt  ib-eckerl.de> writes:
> >I encounter shell-hangs with cygwin also when using cygwins setup, so i
> >post the problem also under
> >http://thread.gmane.org/gmane.os.cygwin/70104 because i think it has
> >something to do with deadlocks or errors in communication in
> >dll-subroutine calls
> 
> This is very unlikely.
> 
> You really don't seem to know anything about this issue so I don't
> think that postulating on the problem is going to be helpful.
> 
> --
> Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:   http://cygwin.com/problems.html
> Documentation: http://x.cygwin.com/docs/
> FAQ:   http://x.cygwin.com/docs/faq/
> 
> 

OK. What i can see, is that calling or running the shell causes the problems
in my case. XWin is coming up and running fine, i get the logon screen of the 
remote server and everything seems to be fine. But if i try to open an xterm
on the remote server, XWin seems to hang, no grafical update, nothing happens 
(with enough patience you can watch this going on forever). When i kill the 
second XWin.exe suddenly the xterm appears and everything is working fine 
again, except for the heavy cpu-load, which was not present in my former 
installation.
Summarizing this together with the problems running sh.exe during setup i 
think that some internal action during the invocation of the shell process
might cause the problem. I don't really know the details because i didn't 
examine the source code. But to me it doesn't look like a failure of the 
xserver or client window itself but like a problem of one type of process
(invoking the shell)



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: XWin hangs on opening xterms, correspondence with setup hangs ??

2005-10-10 Thread Norbert Harendt
Norbert Harendt  ib-eckerl.de> writes:

I encounter shell-hangs with cygwin also when using cygwins setup, 
so i post the problem also under 
http://thread.gmane.org/gmane.os.cygwin/70104
because i think it has something to do with deadlocks or 
errors in communication in dll-subroutine calls




--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



Re: XWin hangs on opening xterms

2005-10-06 Thread Norbert Harendt
Igor Pechtchanski  cs.nyu.edu> writes:

> Did you let it run long enough?  Looks like it's trying to fork, and the
> DLLs are being loaded.  Does the CPU show any activity during the "hang"?
> Does the disk?  Try running it under strace to see if it's really a hang,
> a busy loop, etc.  If you get any output at all during the "hang", XWin is
> probably doing something useful.

yes, i did. It will run forever with the Cygin/X-window still frozen
> 
> 
> Yes.  XWin forks to be able to spawn off a process (in this case, xterm).
> You have killed the forked child, thus XWin is not able to create the
> xterm process.  Don't do that.

Sorry, that is NOT correct, because xterm is showing in Cygwin/X-Window
immediately after killing the second XWin.exe. Xterm itself is NOT killed by
that action!

What is very atonishing is, that CPD-load under Windows is very heavy when
running XWin. And that is different to the former version i installed.

> HTH,
>   Igor





--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/



XWin hangs on opening xterms

2005-10-05 Thread Norbert Harendt
Hello,

I updated cygwin a few days ago, now my xwindow-remote sessions are often
hanging and are consuming a lot of cpu-power. In detail:

I am running a W2K-machine with 2 cpus and connect to a linux-X-server via 
cygwins 
   XWin -query 192.168.1.100 -once
in order to get the logon-screen of the linux-server. Before last days update
all was performing very will (but now i don't know which version that was)

Now i get the following output:

**
$ XWin -query 192.168.1.100 -once
Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.2.0-4

Contact: cygwin-xfree@cygwin.com

XWin was started with the following command line:

XWin -query 192.168.1.100 -once

_XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 0777
_XSERVTransmkdir: this may cause subsequent errors
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/,..."
winDetectSupportedEngines - Windows NT/2000/XP
winDetectSupportedEngines - DirectDraw installed
winDetectSupportedEngines - DirectDraw4 installed
winDetectSupportedEngines - Returning, supported engines 0007
winSetEngine - Using Shadow DirectDraw NonLocking
winAdjustVideoModeShadowDDNL - Using Windows display depth of 
   16 bits per pixel
winFinishScreenInitFB - Masks: f800 07e0 001f
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: "0407" (0407)
(--) Using preset keyboard for "German (Germany)" (407), type "4"
Rules = "xorg" Model = "pc105" Layout = "de" Variant = "(null)" 
  Options = "(null)"
**

At this point the Cygin/X-windows hangs.
Opening the windows taskmanager i killed the second running instance of 
   XWin.exe and get the output

**
 40 [main] XWin 804 fork_parent: child 1524 died waiting for dll loading
(EE) Couldn't load XKB keymap, falling back to pre-XKB keymap
(--) 3 mouse buttons found
winPointerWarpCursor - Discarding first warp: 637 499
winProcEstablishConnection - Hello
winProcEstablishConnection - Clipboard is not enabled, returning.
winProcQueryTree - Clipboard is not enabled, returning.
**

but than the logon screen of the linuxserver appears in the Cygwin/X-Window 
and i am able to login. The initialisation of the X-desktop is done as usual.
But every time i open an xterm, the Cygwin/X-Window hangs again. Again killing
the second XWin.exe brings Cygwin/X-Window back to life, producing an output 
similar to the following

**
332281787 [main] XWin 804 fork_parent: child 1476 died waiting for dll loading
**


Can anybody tell me, what is happening 

Thanks in advance
   Norbert


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/