Re: Cygwin/X XDMCP Issue
On Sun, Feb 22, 2015 at 4:38 PM, Maarten Hoes hoes.maar...@gmail.com wrote: On 22-2-2015 22:09, Maarten Hoes wrote: 28 1.690209 192.168.0.21 - 192.168.178.20 TCP 74 60221â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=6862378 TSecr=0 WS=128 Wait, what ? send to 192.168.178.20 instead of 192.168.0.20 ? i changed the ip address range of my home network. thats whats wrong, now i guess i need to figure out where i forgot to update that ip range / address. Oh, well. I can think of 2 possible issues/solutions: With XDMCP under VcXsrv or Cygwin XWin, you often need to use this argument to, usually when you have multiple (virtual) network adapters: -from 192.168.0.20 XDMCP involves a forward-confirmed reverse DNS lookup. So if you have incorrect DNS records like the following: PTR: 192.168.0.20 - windows-pc A: windows-pc - 192.168.178.20 Then this problem will happen. -Mike -- 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: Cygwin/X XDMCP Issue
On 23-2-2015 16:33, Maarten Hoes wrote: On 23-2-2015 16:11, Maarten Hoes wrote: I suspect something strange is going on under the covers of my ISP supplied FRITZ!Box 7390, but I cant figure out what... Looks like I managed to seriously mess up my network settings, alright. From another Linux host on the same subnet (192.168.0.31), I get these ICMP messages when I try to start an X/XDMCP session to it: 4 0.000292 192.168.0.31 - 192.168.0.20 ICMP 77 Destination unreachable (Host administratively prohibited) 7 1.989470 192.168.0.31 - 192.168.0.20 ICMP 77 Destination unreachable (Host administratively prohibited) 12 5.989469 192.168.0.31 - 192.168.0.20 ICMP 77 Destination unreachable (Host administratively prohibited) Oh wait, thats just the default iptables ruleset on Fedora (phew). Well I changed the range back to 192.168.178.0/255.255.255.0, and now it works again. Guess ill do some digging around later looking for root causes when I have more time, but for now it's good enough for me. ;) Thanks for the help, - Maarten 1 0.0 192.168.178.20 - 192.168.178.21 XDMCP 49 Query 2 0.038915000 192.168.178.21 - 192.168.178.20 XDMCP 99 Willing 3 0.213517000 192.168.178.20 - 192.168.178.21 XDMCP 352 Request 4 0.213793000 192.168.178.21 - 192.168.178.20 XDMCP 94 Accept 5 0.213875000 192.168.178.20 - 192.168.178.21 XDMCP 71 Manage 6 0.221893000 192.168.178.21 - 192.168.178.20 TCP 74 42824â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=4294947644 TSecr=0 WS=128 7 0.221999000 192.168.178.20 - 192.168.178.21 TCP 74 6000â+'42824 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 WS=4 SACK_PERM=1 TSval=35608 TSecr=4294947644 8 0.222094000 192.168.178.21 - 192.168.178.20 TCP 66 42824â+'6000 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=4294947644 TSecr=35608 9 0.33000 192.168.178.21 - 192.168.178.20 X11 114 Initial connection request 10 0.222453000 192.168.178.20 - 192.168.178.21 TCP 74 [TCP segment of a reassembled PDU] 11 0.222515000 192.168.178.20 - 192.168.178.21 TCP 1514 [TCP segment of a reassembled PDU] 12 0.222529000 192.168.178.20 - 192.168.178.21 TCP 1514 [TCP segment of a reassembled PDU] 13 0.222536000 192.168.178.21 - 192.168.178.20 TCP 66 42824â+'6000 [ACK] Seq=49 Ack=9 Win=29312 Len=0 TSval=4294947645 TSecr=35608 14 0.222539000 192.168.178.20 - 192.168.178.21 X11 254 Initial connection reply 15 0.222602000 192.168.178.21 - 192.168.178.20 TCP 66 42824â+'6000 [ACK] Seq=49 Ack=3093 Win=35456 Len=0 TSval=4294947645 TSecr=35608 16 0.222715000 192.168.178.21 - 192.168.178.20 X11 86 Requests: QueryExtension 17 0.22282 192.168.178.20 - 192.168.178.21 X11 98 Reply: QueryExtension 18 0.222908000 192.168.178.21 - 192.168.178.20 X11 70 Requests: BIG-REQUESTS 19 0.223006000 192.168.178.20 - 192.168.178.21 X11 98 Reply: BIG-REQUESTS 20 0.223102000 192.168.178.21 - 192.168.178.20 X11 110 Requests: CreateGC, GetProperty 21 0.223186000 192.168.178.20 - 192.168.178.21 X11 98 Reply: GetProperty 22 0.22329 192.168.178.21 - 192.168.178.20 X11 86 Requests: QueryExtension 23 0.22347 192.168.178.20 - 192.168.178.21 X11 98 Reply: QueryExtension 24 0.22357 192.168.178.21 - 192.168.178.20 X11 74 Requests: XKEYBOARD 25 0.223659000 192.168.178.20 - 192.168.178.21 X11 98 Reply: XKEYBOARD 26 0.224025000 192.168.178.21 - 192.168.178.20 X11 102 Requests: OpenFont, QueryExtension 27 0.224145000 192.168.178.20 - 192.168.178.21 X11 98 Reply: QueryExtension 28 0.224244000 192.168.178.21 - 192.168.178.20 X11 82 Requests: RENDER, RENDER 29 0.224331000 192.168.178.20 - 192.168.178.21 X11 98 Reply: RENDER -- 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: Cygwin/X XDMCP Issue
On 20/02/2015 18:36, Maarten Hoes wrote: I am (again) experiencing some issues when running Cygwin/X in combination with XDMCP. Opening a cygwin prompt and running 'startxwin' works as expected. But when I try to connect to my remote Linux system with the command 'xwin -query 192.168.0.21' (or with the 'XLaunch' program and choose XDMCP) the screen stays black. Things used to work, but apparently something broke my setup. Im running the latest Cygwin/X, and applied all current updates on my Fedora 21 Linux system. Im running KDM. Any and all ideas are more than welcome, as I have no idea whats going on here. Package: version 1.16.3-1 built 2014-12-30 xwin -query 192.168.0.21 -logverbose 3 1 0.00 192.168.0.20 - 192.168.0.21 XDMCP 49 Query 2 0.013254 192.168.0.21 - 192.168.0.20 XDMCP 100 Willing 3 0.227426 192.168.0.20 - 192.168.0.21 XDMCP 360 Request 4 0.227831 192.168.0.21 - 192.168.0.20 XDMCP 94 Accept 5 0.227968 192.168.0.20 - 192.168.0.21 XDMCP 71 Manage Assuming your wireshark filter includes X11, you should be seeing a X11 connection request from 192.168.0.21 to the X server here. Since the same X server version was working for you before (to a different IP address), I can only suggest you examine what else has changed. You might want to check your firewall/network configuration. 6 2.225721 192.168.0.20 - 192.168.0.21 XDMCP 71 Manage 7 6.229538 192.168.0.20 - 192.168.0.21 XDMCP 71 Manage 8 14.230544 192.168.0.20 - 192.168.0.21 XDMCP 71 Manage 9 30.228625 192.168.0.20 - 192.168.0.21 XDMCP 71 Manage -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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: Cygwin/X XDMCP Issue
Hi, On 22-2-2015 14:55, Jon TURNEY wrote: Assuming your wireshark filter includes X11, you should be seeing a X11 connection request from 192.168.0.21 to the X server here. Hrm. wireshark (running in promisc mode on my desktop that runs cygwin) does show TCP sessions for port 6000 (that's X11, right ?). But somehow that doesnt seem to get through correctly. I tried opening up that range on my desktop firewall (Norton Internet Security), but that doesnt seem to change anything. - Maarten. 28 1.690209 192.168.0.21 - 192.168.178.20 TCP 74 60221â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=6862378 TSecr=0 WS=128 30 2.692531 192.168.0.21 - 192.168.178.20 TCP 74 [TCP Retransmission] 60221â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=6863380 TSecr=0 WS=128 32 4.696609 192.168.0.21 - 192.168.178.20 TCP 74 [TCP Retransmission] 60221â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=6865384 TSecr=0 WS=128 45 8.704426 192.168.0.21 - 192.168.178.20 TCP 74 [TCP Retransmission] 60221â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=6869392 TSecr=0 WS=128 69 16.719818 192.168.0.21 - 192.168.178.20 TCP 74 [TCP Retransmission] 60221â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=6877408 TSecr=0 WS=128 -- 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: Cygwin/X XDMCP Issue
On 22-2-2015 22:09, Maarten Hoes wrote: 28 1.690209 192.168.0.21 - 192.168.178.20 TCP 74 60221â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=6862378 TSecr=0 WS=128 Wait, what ? send to 192.168.178.20 instead of 192.168.0.20 ? i changed the ip address range of my home network. thats whats wrong, now i guess i need to figure out where i forgot to update that ip range / address. Oh, well. - Maarten -- 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: Cygwin/X XDMCP Issue
On 20-2-2015 19:36, Maarten Hoes wrote: ( I tried to included my XWin.log and a wireshark tracefile to this message, but the mail server keeps bouncing my messages). Perhaps this works: Xwin.log: http://ur1.ca/jrrmb wireshark tracefile (txt): http://ur1.ca/jrrmh - Maarten -- 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/
Cygwin/X XDMCP Issue
Hi, I am (again) experiencing some issues when running Cygwin/X in combination with XDMCP. Opening a cygwin prompt and running 'startxwin' works as expected. But when I try to connect to my remote Linux system with the command 'xwin -query 192.168.0.21' (or with the 'XLaunch' program and choose XDMCP) the screen stays black. Things used to work, but apparently something broke my setup. Im running the latest Cygwin/X, and applied all current updates on my Fedora 21 Linux system. Im running KDM. Any and all ideas are more than welcome, as I have no idea whats going on here. ( I tried to included my XWin.log and a wireshark tracefile to this message, but the mail server keeps bouncing my messages). - Maarten -- 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: Cygwin/X XDMCP Issue
On 13/02/2015 07:24, Maarten Hoes wrote: On 2-2-2015 16:20, Jon TURNEY wrote: If you can provide the details of the linux distribution and release you are using on your remote host, I can see if I can try to reproduce the problem. I was wondering if you managed to reproduce the issue ? Yes, I can reproduce it. It seems that the XRANDR data which XWin returns isn't quite complete, which tickles a bug in Gnome [1] primaryMonitor is undefined, which prevents the login greeter from being displayed. I've been testing a fix for that issue in XWin. This gets you the greeter login screen. Unfortunately there seem to be other bugs, which prevent login from working. These also occur when starting an XDMCP session from linux, so I don't think these are XWin issues. [1] https://bugzilla.gnome.org/show_bug.cgi?id=736054 -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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: Cygwin/X XDMCP Issue
Hi, On 2-2-2015 16:20, Jon TURNEY wrote: If you can provide the details of the linux distribution and release you are using on your remote host, I can see if I can try to reproduce the problem. I was wondering if you managed to reproduce the issue ? - Maarten -- 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: Cygwin/X XDMCP Issue
On 22/01/2015 07:46, Maarten Hoes wrote: Well I changed from GDM to KDM, and now everything is working as expected. Just one last question: are there any known issues with XDMCP and Gnome GDM ? Or is that combination supposed to just work ? Yes, XDMCP is supposed to work with GDM. No, there are no known issues, but we don't know about issues until someone reports them. :) If you can provide the details of the linux distribution and release you are using on your remote host, I can see if I can try to reproduce the problem. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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: Cygwin/X XDMCP Issue
Hi, On 2-2-2015 16:20, Jon TURNEY wrote: If you can provide the details of the linux distribution and release you are using on your remote host, I can see if I can try to reproduce the problem. I can reproduce the behavior with GDM on both Fedora 21 and Ubuntu 14.04. So im not too sure that it is distribution specific. Of course, it could just be a configuration error on my side that I made on both distributions thinking it was 'the right thing to do'. ;) Thanks for looking, - Maarten -- 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: Cygwin/X XDMCP Issue
Hi, Well I changed from GDM to KDM, and now everything is working as expected. Just one last question: are there any known issues with XDMCP and Gnome GDM ? Or is that combination supposed to just work ? Just for the record, here is the XWin.0.log of a working KDM session. - Maarten XWin.0.log Description: Binary data -- 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: Cygwin/X XDMCP Issue
Hi, Sorry, I forgot to include it in my previous posts: please find the contents of 'cygcheck -s -v -r' attached in 'cygcheck.out' - Maarten Cygwin Configuration Diagnostics Current System Time: Sun Jan 18 08:54:47 2015 Windows 8.1 Ver 6.3 Build 9600 Path: C:\cygwin64\usr\local\bin C:\cygwin64\bin C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common C:\PROGRAM FILES (X86)\INTEL\ICLS CLIENT C:\PROGRAM FILES\INTEL\ICLS CLIENT C:\Windows\SYSTEM32 C:\Windows C:\Windows\SYSTEM32\WBEM C:\Windows\SYSTEM32\WINDOWSPOWERSHELL\V1.0 C:\PROGRAM FILES\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\DAL C:\PROGRAM FILES\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\IPT C:\PROGRAM FILES (X86)\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\DAL C:\PROGRAM FILES (X86)\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\IPT D:\Progra~1\Java\jre7\bin C:\MinGW\bin D:\Program Files\Calibre2 C:\MinGW\bin C:\MinGW\mingw32\bin C:\MinGW\msys\1.0\bin C:\GnuWin32\bin C:\Program Files (x86)\QuickTime\QTSystem Output from C:\cygwin64\bin\id.exe UID: 1001(Maarten) GID: 513(Geen) 513(Geen) 545(Gebruikers) SysDir: C:\Windows\system32 WinDir: C:\Windows USER = 'Maarten' PWD = '/home/Maarten' HOME = '/home/Maarten' USERDOMAIN_ROAMINGPROFILE = 'DUSTY123' HOMEPATH = '\Users\Maarten' APPDATA = 'C:\Users\Maarten\AppData\Roaming' ProgramW6432 = 'C:\Program Files' HOSTNAME = 'DUSTY123' SHELL = '/bin/bash' TERM = 'xterm' PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 60 Stepping 3, GenuineIntel' PROFILEREAD = 'true' WINDIR = 'C:\Windows' PUBLIC = 'C:\Users\Public' OLDPWD = '/cygdrive/d/Users/Maarten/Desktop' ORIGINAL_PATH = '/cygdrive/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common:/cygdrive/c/PROGRAM FILES (X86)/INTEL/ICLS CLIENT:/cygdrive/c/PROGRAM FILES/INTEL/ICLS CLIENT:/cygdrive/c/Windows/SYSTEM32:/cygdrive/c/Windows:/cygdrive/c/Windows/SYSTEM32/WBEM:/cygdrive/c/Windows/SYSTEM32/WINDOWSPOWERSHELL/V1.0:/cygdrive/c/PROGRAM FILES/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/DAL:/cygdrive/c/PROGRAM FILES/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/IPT:/cygdrive/c/PROGRAM FILES (X86)/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/DAL:/cygdrive/c/PROGRAM FILES (X86)/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/IPT:/cygdrive/d/Progra~1/Java/jre7/bin:/cygdrive/c/MinGW/bin:/cygdrive/d/Program Files/Calibre2:/cygdrive/c/MinGW/bin:/cygdrive/c/MinGW/mingw32/bin:/cygdrive/c/MinGW/msys/1.0/bin:/cygdrive/c/GnuWin32/bin:/cygdrive/c/Program Files (x86)/QuickTime/QTSystem' USERDOMAIN = 'DUSTY123' CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\ProgramData' !:: = '::\' TEMP = '/tmp' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' USERNAME = 'Maarten' PROCESSOR_LEVEL = '6' ProgramFiles(x86) = 'C:\Program Files (x86)' PSModulePath = 'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\' FP_NO_HOST_CHECK = 'NO' SYSTEMDRIVE = 'C:' JAVA_HOME = 'D:\Progra~1\Java\jre7' LANG = 'en_US.UTF-8' USERPROFILE = 'C:\Users\Maarten' TZ = 'Europe/Amsterdam' PS1 = '\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = '\\DUSTY123' CommonProgramW6432 = 'C:\Program Files\Common Files' PROCESSOR_ARCHITECTURE = 'AMD64' LOCALAPPDATA = 'C:\Users\Maarten\AppData\Local' ProgramData = 'C:\ProgramData' EXECIGNORE = '*.dll' SHLVL = '1' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' HOMEDRIVE = 'C:' COMSPEC = 'C:\Windows\system32\cmd.exe' TMP = '/tmp' SYSTEMROOT = 'C:\Windows' PRINTER = 'HP Photosmart C5200 series' PROCESSOR_REVISION = '3c03' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info' PROGRAMFILES = 'C:\Program Files' NUMBER_OF_PROCESSORS = '8' asl.log = 'Destination=file' SESSIONNAME = 'Console' COMPUTERNAME = 'DUSTY123' _ = '/usr/bin/cygcheck' HKEY_CURRENT_USER\Software\Cygwin HKEY_CURRENT_USER\Software\Cygwin\Installations (default) = '\??\C:\cygwin64' c5e39b7a9d22bafb = '\??\C:\cygwin' HKEY_CURRENT_USER\Software\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\DefaultIcon (default) = 'C:\cygwin64\bin\xlaunch.exe,1' HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Edit HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Edit\command (default) = 'C:\cygwin64\bin\run C:\cygwin64\bin\bash -l -c xlaunch -load \%1\' HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Open HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Open\command (default) = 'C:\cygwin64\bin\run C:\cygwin64\bin\bash -l -c xlaunch -run \%1\' HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations (default) = '\??\C:\cygwin64' HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup (default) =
Re: Cygwin/X XDMCP Issue
Hi, Also, when I run wireshark/tshark, I seem to be watching a regular/successful XDCMP/X11 session ? : - Maarten 1 0.00 192.168.178.20 - 192.168.178.22 XDMCP 49 Query 2 0.013070 192.168.178.22 - 192.168.178.20 XDMCP 106 Willing 3 0.178469 192.168.178.20 - 192.168.178.22 XDMCP 312 Request 4 0.183798 192.168.178.22 - 192.168.178.20 XDMCP 94 Accept 5 0.183901 192.168.178.20 - 192.168.178.22 XDMCP 71 Manage 6 0.687156 192.168.178.22 - 192.168.178.20 TCP 74 49008→6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=8283439 TSecr=0 WS=128 7 0.687297 192.168.178.20 - 192.168.178.22 TCP 74 6000→49008 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 WS=4 SACK_PERM=1 TSval=1056917 TSecr=8283439 8 0.687462 192.168.178.22 - 192.168.178.20 TCP 66 49008→6000 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=8283439 TSecr=1056917 9 0.687695 192.168.178.22 - 192.168.178.20 X11 114 Initial connection request 10 0.687992 192.168.178.20 - 192.168.178.22 TCP 74 [TCP segment of a reassembled PDU] 11 0.688064 192.168.178.20 - 192.168.178.22 TCP 1514 [TCP segment of a reassembled PDU] 12 0.688086 192.168.178.20 - 192.168.178.22 TCP 1514 [TCP segment of a reassembled PDU] 13 0.688104 192.168.178.20 - 192.168.178.22 X11 254 Initial connection reply 14 0.688127 192.168.178.22 - 192.168.178.20 TCP 66 49008→6000 [ACK] Seq=49 Ack=9 Win=29312 Len=0 TSval=8283440 TSecr=1056917 15 0.688225 192.168.178.22 - 192.168.178.20 TCP 66 49008→6000 [ACK] Seq=49 Ack=3093 Win=35456 Len=0 TSval=8283440 TSecr=1056917 16 0.688451 192.168.178.22 - 192.168.178.20 X11 86 Requests: QueryExtension 17 0.688654 192.168.178.20 - 192.168.178.22 X11 98 Reply: QueryExtension 18 0.688823 192.168.178.22 - 192.168.178.20 X11 70 Requests: BIG-REQUESTS 19 0.688958 192.168.178.20 - 192.168.178.22 X11 98 Reply: BIG-REQUESTS 20 0.689164 192.168.178.22 - 192.168.178.20 X11 110 Requests: CreateGC, GetProperty 21 0.689567 192.168.178.20 - 192.168.178.22 X11 98 Reply: GetProperty 22 0.689752 192.168.178.22 - 192.168.178.20 X11 86 Requests: QueryExtension 23 0.690102 192.168.178.20 - 192.168.178.22 X11 98 Reply: QueryExtension 24 0.690259 192.168.178.22 - 192.168.178.20 X11 74 Requests: XKEYBOARD 25 0.690419 192.168.178.20 - 192.168.178.22 X11 98 Reply: XKEYBOARD 26 0.692905 192.168.178.22 - 192.168.178.20 X11 82 Requests: QueryExtension 27 0.693104 192.168.178.20 - 192.168.178.22 X11 98 Reply: QueryExtension 28 0.693326 192.168.178.22 - 192.168.178.20 X11 98 Requests: QueryExtension 29 0.693477 192.168.178.20 - 192.168.178.22 X11 98 Reply: QueryExtension 30 0.693627 192.168.178.22 - 192.168.178.20 X11 74 Requests: Generic Event Extension 31 0.693881 192.168.178.20 - 192.168.178.22 X11 98 Reply: Generic Event Extension 32 0.694061 192.168.178.22 - 192.168.178.20 X11 78 Requests: RANDR 33 0.694183 192.168.178.20 - 192.168.178.22 X11 98 Reply: RANDR 34 0.694334 192.168.178.22 - 192.168.178.20 X11 74 Requests: RANDR 35 0.694481 192.168.178.20 - 192.168.178.22 X11 98 Reply: RANDR 36 0.694628 192.168.178.22 - 192.168.178.20 X11 74 Requests: RANDR 37 0.694759 192.168.178.20 - 192.168.178.22 X11 98 Reply: RANDR 38 0.734457 192.168.178.22 - 192.168.178.20 TCP 66 49008→6000 [ACK] Seq=229 Ack=3445 Win=35456 Len=0 TSval=8283487 TSecr=1056918 39 0.774514 192.168.178.22 - 192.168.178.20 TCP 74 49009→6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=8283526 TSecr=0 WS=128 40 0.774620 192.168.178.20 - 192.168.178.22 TCP 74 6000→49009 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 WS=4 SACK_PERM=1 TSval=1056926 TSecr=8283526 41 0.774780 192.168.178.22 - 192.168.178.20 TCP 66 49009→6000 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=8283527 TSecr=1056926 42 0.774978 192.168.178.22 - 192.168.178.20 X11 114 Initial connection request 43 0.775254 192.168.178.20 - 192.168.178.22 TCP 74 [TCP segment of a reassembled PDU] 44 0.775304 192.168.178.20 - 192.168.178.22 TCP 1514 [TCP segment of a reassembled PDU] 45 0.775327 192.168.178.20 - 192.168.178.22 TCP 1514 [TCP segment of a reassembled PDU] 46 0.775336 192.168.178.20 - 192.168.178.22 X11 254 Initial connection reply 47 0.775382 192.168.178.22 - 192.168.178.20 TCP 66 49009→6000 [ACK] Seq=49 Ack=9 Win=29312 Len=0 TSval=8283527 TSecr=1056926 48 0.775458 192.168.178.22 - 192.168.178.20 TCP 66 49009→6000 [ACK] Seq=49 Ack=3093 Win=35456 Len=0 TSval=8283527 TSecr=1056926 49 0.775580 192.168.178.22 - 192.168.178.20 X11 86 Requests: QueryExtension 50 0.775697 192.168.178.20 - 192.168.178.22 X11 98 Reply: QueryExtension 51 0.775818 192.168.178.22 - 192.168.178.20 X11 70 Requests: BIG-REQUESTS 52 0.775916 192.168.178.20 - 192.168.178.22 X11 98 Reply: BIG-REQUESTS 53 0.776069 192.168.178.22 - 192.168.178.20 X11 110 Requests: CreateGC, GetProperty 54 0.776186 192.168.178.20 - 192.168.178.22 X11 98 Reply
Cygwin/X XDMCP Issue
Hi, Im having some issues when running Cygwin/X in combination with XDMCP. Opening a cygwin prompt and running 'startx' works as expected. When I try to connect to my remote Linux system with the command 'xwin -query 192.168.178.22' (or with the 'XLaunch' program and choose XDMCP) the screen stays black. I get the impression that I do get an connection, but that there is a display problem. When I try to close the blacked out Window, I get the message 'Exiting will close all screens on this display. There are currently 6 clients connected. Proceed with the shutdown of this display/server ?' When i specify 'xwin -retro -query 192.168.178.22', the cursor appears and the screen gets gray-ish, but mouse clicking has no effect. Setting 'xwin -engine 16 -query 192.168.178.22' results in a blue background and an error: 'Failed asserion key - size == 0 at line 147 of file /qip/cygport-git/x-org-server/x-org-server-1.16.3-1.x86_64/src/xserver-cygwin-1.16.3-1/include/privates.h in function dixSetPrivate' and a core dump. Any and all ideas are more than welcome, as I have no idea whats going on here. This is the output of the 'xwin -query 192.168.178.22' command : $ xwin -query 192.168.178.22 Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.16.3.0 OS: CYGWIN_NT-6.3 DUSTY123 1.7.33-2(0.280/5/3) 2014-11-13 15:47 x86_64 OS: Windows 8.1 [Windows NT 6.3 build 9600] (Win64) Package: version 1.16.3-1 built 2014-12-30 XWin was started with the following command line: xwin -query 192.168.178.22 (II) xorg.conf is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information LoadPreferences: /home/Maarten/.XWinrc not found LoadPreferences: Loading /etc/X11/system.XWinrc LoadPreferences: Done parsing the configuration file... winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL winDetectSupportedEngines - Returning, supported engines 0015 winSetEngine - Using Shadow DirectDraw NonLocking winScreenInit - Using Windows display depth of 32 bits per pixel winWindowProc - WM_SIZE - new client area w: 1424 h: 821 winFinishScreenInitFB - Masks: 00ff ff00 00ff 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 (EE) AIGLX: No native OpenGL in modes with a root window (II) AIGLX: enabled GLX_EXT_texture_from_pixmap (II) AIGLX: Loaded and initialized swrast (II) GLX: Initialized DRISWRAST GL provider for screen 0 winPointerWarpCursor - Discarding first warp: 712 410 (--) 3 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) Windows keyboard layout: 0409 (0409) US, type 4 (--) Found matching XKB configuration English (USA) (--) Model = pc105 Layout = us Variant = none Options = none Rules = base Model = pc105 Layout = us Variant = none Options = none winProcEstablishConnection - winInitClipboard returned. winClipboardThreadProc - DISPLAY=:0.0 OS maintains clipboard viewer chain: yes winClipboardProc - XOpenDisplay () returned and successfully opened the display. winWindowProc - WM_*KEYDOWN - Closekey hit, quitting winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. winDeinitMultiWindowWM - Noting shutdown in progress (EE) Server terminated successfully (0). Closing log file. Regards, - Maarten -- 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: Clipboard integration does not work with XDMCP
Thank you very much for your prompt intervention. I can confirm that your fix works for me too. I see that now, in the log, lines like the followings are appearing: client(60): Released pid(-1). client(60): Released cmdline(NULL) and cmdargs(NULL). client(60): Reserved pid(-1). client(60): Reserved cmdname(NULL) and cmdargs(NULL). AllocNewConnection: client index = 3, socket fd = 13 I guess you raised the trace/log levels for debug/reporting purposes, so probably this is not relevant. Thank you, Danilo Turina Il 22/02/2014 14:36, Jon TURNEY ha scritto: On 21/02/2014 16:51, Danilo Turina wrote: Hello, I need to connect from my PC to a Linux machine that runs KDE and I use the following command: XWin -from MY_PC_IP_ADDR -terminate -query LINUX_MACHINE_IP_ADDR It works well but the clipboard integration that fails. Notice that: 1) XWin alone (i.e. no XDMCP, i.e. local) works nicely with my Windows clipboard 2) Xming works (almost) fine with XDMCP + clipboard (with the same Linux machine) I gave a look at the XWin log in two cases: A) XWin alone B) XWin + XDMCP And the only differences I've found (apart from the different command line arguments) is the following lines that were at the end of the log of the XDMCP invokation: winProcEstablishConnection - winInitClipboard returned. winClipboardThreadProc - DISPLAY=:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardIOErrorHandler! winClipboardProc - setjmp returned for IO Error Handler. winClipboardProc - trying to restart clipboard thread winClipboardThreadProc - DISPLAY=:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. Thanks for reporting this problem, and the clear reproduction steps. The issue here is that the XDMCP login dialog kills all other X clients (including the clipboard integration client) for security. The clipboard integration client is supposed to restart and reconnect as necessary, but it seems this has been broken for a while. I've has a go at fixing this and uploaded a snapshot at [1]. Perhaps you could try that and see if it improves things for you? [1] ftp://cygwin.com/pub/cygwinx/XWin.20140222-git-c14d82e878fc884d.exe.bz2 -- DANILO TURINA Sesa S.p.A. Software Development Engineer Rieti (Italy) 3 mesi 23 giorni 24 minuti 22 secondi -- 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: Clipboard integration does not work with XDMCP
Il 22/02/2014 14:36, Jon TURNEY ha scritto: On 21/02/2014 16:51, Danilo Turina wrote: Hello, I need to connect from my PC to a Linux machine that runs KDE and I use the following command: XWin -from MY_PC_IP_ADDR -terminate -query LINUX_MACHINE_IP_ADDR It works well but the clipboard integration that fails. Notice that: 1) XWin alone (i.e. no XDMCP, i.e. local) works nicely with my Windows clipboard 2) Xming works (almost) fine with XDMCP + clipboard (with the same Linux machine) I gave a look at the XWin log in two cases: A) XWin alone B) XWin + XDMCP And the only differences I've found (apart from the different command line arguments) is the following lines that were at the end of the log of the XDMCP invokation: winProcEstablishConnection - winInitClipboard returned. winClipboardThreadProc - DISPLAY=:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardIOErrorHandler! winClipboardProc - setjmp returned for IO Error Handler. winClipboardProc - trying to restart clipboard thread winClipboardThreadProc - DISPLAY=:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. Thanks for reporting this problem, and the clear reproduction steps. The issue here is that the XDMCP login dialog kills all other X clients (including the clipboard integration client) for security. The clipboard integration client is supposed to restart and reconnect as necessary, but it seems this has been broken for a while. I've has a go at fixing this and uploaded a snapshot at [1]. Perhaps you could try that and see if it improves things for you? [1] ftp://cygwin.com/pub/cygwinx/XWin.20140222-git-c14d82e878fc884d.exe.bz2 Sorry for top posting... I resend here my previous e-mail, without top posting. --- Thank you very much for your prompt intervention. I can confirm that your fix works for me too. I see that now, in the log, lines like the followings are appearing: client(60): Released pid(-1). client(60): Released cmdline(NULL) and cmdargs(NULL). client(60): Reserved pid(-1). client(60): Reserved cmdname(NULL) and cmdargs(NULL). AllocNewConnection: client index = 3, socket fd = 13 I guess you raised the trace/log levels for debug/reporting purposes, so probably this is not relevant. Thank you, Danilo Turina -- DANILO TURINA Sesa S.p.A. Software Development Engineer Rieti (Italy) 3 mesi 23 giorni 34 minuti 43 secondi -- 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: Clipboard integration does not work with XDMCP
On 21/02/2014 16:51, Danilo Turina wrote: Hello, I need to connect from my PC to a Linux machine that runs KDE and I use the following command: XWin -from MY_PC_IP_ADDR -terminate -query LINUX_MACHINE_IP_ADDR It works well but the clipboard integration that fails. Notice that: 1) XWin alone (i.e. no XDMCP, i.e. local) works nicely with my Windows clipboard 2) Xming works (almost) fine with XDMCP + clipboard (with the same Linux machine) I gave a look at the XWin log in two cases: A) XWin alone B) XWin + XDMCP And the only differences I've found (apart from the different command line arguments) is the following lines that were at the end of the log of the XDMCP invokation: winProcEstablishConnection - winInitClipboard returned. winClipboardThreadProc - DISPLAY=:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardIOErrorHandler! winClipboardProc - setjmp returned for IO Error Handler. winClipboardProc - trying to restart clipboard thread winClipboardThreadProc - DISPLAY=:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. Thanks for reporting this problem, and the clear reproduction steps. The issue here is that the XDMCP login dialog kills all other X clients (including the clipboard integration client) for security. The clipboard integration client is supposed to restart and reconnect as necessary, but it seems this has been broken for a while. I've has a go at fixing this and uploaded a snapshot at [1]. Perhaps you could try that and see if it improves things for you? [1] ftp://cygwin.com/pub/cygwinx/XWin.20140222-git-c14d82e878fc884d.exe.bz2 -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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: Clipboard integration does not work with XDMCP
On 02/22/2014 08:36 AM, Jon TURNEY wrote: Thanks for reporting this problem, and the clear reproduction steps. The issue here is that the XDMCP login dialog kills all other X clients (including the clipboard integration client) for security. The clipboard integration client is supposed to restart and reconnect as necessary, but it seems this has been broken for a while. I've has a go at fixing this and uploaded a snapshot at [1]. Perhaps you could try that and see if it improves things for you? [1] ftp://cygwin.com/pub/cygwinx/XWin.20140222-git-c14d82e878fc884d.exe.bz2 I also noticed this problem, and tested your fix, above [1]. After applying your fix, Xwin clipboard transaction between local machine and remote machine (through XDMCP) seems to be functional. Claude -- 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/
Clipboard integration does not work with XDMCP
Hello, I need to connect from my PC to a Linux machine that runs KDE and I use the following command: XWin -from MY_PC_IP_ADDR -terminate -query LINUX_MACHINE_IP_ADDR It works well but the clipboard integration that fails. Notice that: 1) XWin alone (i.e. no XDMCP, i.e. local) works nicely with my Windows clipboard 2) Xming works (almost) fine with XDMCP + clipboard (with the same Linux machine) I gave a look at the XWin log in two cases: A) XWin alone B) XWin + XDMCP And the only differences I've found (apart from the different command line arguments) is the following lines that were at the end of the log of the XDMCP invokation: winProcEstablishConnection - winInitClipboard returned. winClipboardThreadProc - DISPLAY=:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardIOErrorHandler! winClipboardProc - setjmp returned for IO Error Handler. winClipboardProc - trying to restart clipboard thread winClipboardThreadProc - DISPLAY=:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. I've searched around (google) for this problem but I found almost nothing (and most of that was old stuff). The only relevant suggestion was a post on this same mailing list that suggested to create the file /etc/X0.hosts and put localhost inside it. This doesn't work for me. Any help is appreciated. Thank you, Danilo Turina -- DANILO TURINA Sesa S.p.A. Software Development Engineer Rieti (Italy) 3 mesi 20 giorni 8 ore 29 minuti 52 secondi -- 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: Unable to start session using XDMCP
On 13/07/2011 15:04, Alexander Pokluda wrote: I have attached two packet captures. In the first file, it appears that the remote GDM stops responding after sending the accept packet but the capture in the second file was taken immediately after the first capture and restarting XWin. Looking at those packet captures, I can't see anything that XWin is doing wrong. So I can only offer generic advice: Are the Manage requests arriving at and being accepted by the remote host? On Wed, Jul 13, 2011 at 8:29 AM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 12/07/2011 22:15, Alexander Pokluda wrote: I have run into a problem again where I am unable to start a session using XDMCP. I am trying to connect to multiple remote machines running CentOS 5.5 using XWin 1.10.2. [snip] This seemed to be working for you back in March (see [1]), so I guess the important question is what has changed? [1] http://cygwin.com/ml/cygwin-xfree/2011-03/msg00011.html -- 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: Unable to start session using XDMCP
On 12/07/2011 22:15, Alexander Pokluda wrote: I have run into a problem again where I am unable to start a session using XDMCP. I am trying to connect to multiple remote machines running CentOS 5.5 using XWin 1.10.2. When I run the command xwin -nodecoration +xinerama -screen 0 @1 -screen 1 @2 -from 10.3.12.47 -query 10.3.147.22 I get two black windows (with no titlebars) that do nothing for a while and then eventually close and reopen. If I watch what's happening using Wireshark, I see Local Machine Remote Machine --- --- Query Willing Request Accept Manage Manage Manage (many more times) This seems slightly different to that failures you were seeing before, where the Request packet did not arrive at the destination (although the reason for that was never clear) Can you send me the corresponding .pcap file, please. If I look in the XWin log, I see [...] [719987.046] XDM: too many retransmissions, declaring session dead [...] (the full log is pasted below). Oddly, for some remote machines, I occasionally see this behaviour while most of the time it works but for others, I seem to get this behaviour all the time and it never seems to work. Any help would be greatly appreciated. This seemed to be working for you back in March (see [1]), so I guess the important question is what has changed? [1] http://cygwin.com/ml/cygwin-xfree/2011-03/msg00011.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Unable to start session using XDMCP
I have run into a problem again where I am unable to start a session using XDMCP. I am trying to connect to multiple remote machines running CentOS 5.5 using XWin 1.10.2. When I run the command xwin -nodecoration +xinerama -screen 0 @1 -screen 1 @2 -from 10.3.12.47 -query 10.3.147.22 I get two black windows (with no titlebars) that do nothing for a while and then eventually close and reopen. If I watch what's happening using Wireshark, I see Local Machine Remote Machine --- --- Query Willing Request Accept Manage Manage Manage (many more times) If I look in the XWin log, I see [...] [719987.046] XDM: too many retransmissions, declaring session dead [...] (the full log is pasted below). Oddly, for some remote machines, I occasionally see this behaviour while most of the time it works but for others, I seem to get this behaviour all the time and it never seems to work. Any help would be greatly appreciated. -- Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.10.2.0 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64) Package: version 1.10.2-2 built 2011-07-07 XWin was started with the following command line: xwin -nodecoration +xinerama -screen 0 @1 -screen 1 @2 -from 10.3.12.47 -query 10.3.147.22 ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1680 h 1050 winInitializeDefaultScreens - native DPI x 96 y 96 winInitializeScreens - 1 winInitializeScreen - 0 ddxProcessArgument - screen - Found Valid ``@Monitor'' = 1 arg winInitializeScreens - 2 winInitializeScreen - 1 ddxProcessArgument - screen - Found Valid ``@Monitor'' = 2 arg [719859.484] (II) xorg.conf is not supported [719859.484] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [719859.484] LoadPreferences: /cygdrive/c/Users/alpokluda/.XWinrc not found [719859.484] LoadPreferences: Loading /etc/X11/system.XWinrc [719859.484] LoadPreferences: Done parsing the configuration file... [719859.515] winDetectSupportedEngines - DirectDraw installed, allowing ShadowDD [719859.515] winDetectSupportedEngines - Windows NT, allowing PrimaryDD [719859.515] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL [719859.562] winDetectSupportedEngines - Returning, supported engines 001f [719859.562] winSetEngine - Using Shadow DirectDraw NonLocking [719859.562] winScreenInit - Using Windows display depth of 32 bits per pixel [719859.749] winFinishScreenInitFB - Masks: 00ff ff00 00ff [719859.749] Screen 0 added at virtual desktop coordinate (1680,0). [719859.749] winSetEngine - Using Shadow DirectDraw NonLocking [719859.749] winScreenInit - Using Windows display depth of 32 bits per pixel [719859.905] winFinishScreenInitFB - Masks: 00ff ff00 00ff [719859.905] Screen 1 added at virtual desktop coordinate (0,0). [719859.905] MIT-SHM extension disabled due to lack of kernel support [719859.921] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [719859.952] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so [719859.952] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [719859.952] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so [719859.952] (II) GLX: Initialized DRISWRAST GL provider for screen 1 [719859.967] [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! [719859.967] [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [719859.967] [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! [719860.342] winPointerWarpCursor - Discarding first warp: 754 525 [719860.342] (--) 3 mouse buttons found [719860.342] (--) Setting autorepeat to delay=500, rate=31 [719860.342] (--) Windows keyboard layout: 00010409 (00010409) United States-Dvorak, type 4 [719860.342] (--) Found matching XKB configuration English (USA,Dvorak) [719860.342] (--) Model = pc105 Layout = dvorak Variant = none Options = none [719860.342] Rules = base Model = pc105 Layout = dvorak Variant = none Options = none [719860.654] winBlockHandler - pthread_mutex_unlock() [719860.654] winBlockHandler - pthread_mutex_unlock() [719987.046] XDM: too many retransmissions, declaring session dead [719987.202] 6 XSELINUXs still allocated at reset [719987.217] SCREEN: 0 objects of 92 bytes = 0 total bytes 0 private allocs [719987.217] DEVICE: 4 objects of 28 bytes = 112 total bytes 0 private allocs [719987.217] CLIENT: 0 objects of 148 bytes = 0 total bytes 0 private allocs [719987.217] WINDOW: 0 objects of 60 bytes = 0 total bytes 0 private allocs [719987.217] PIXMAP: 2 objects of 28 bytes = 56 total bytes 0 private allocs [719987.217] GC: 0 objects of 64 bytes = 0 total bytes 0 private allocs [719987.217] CURSOR: 0 objects of 8 bytes = 0 total bytes 0 private allocs [719987.217
Re: Can't use XDMCP, winProcEstablishConnection - ProcEstablishConnection failed, bailing shows in log
Thanks for all of your work Jon :) On Sat, Mar 5, 2011 at 1:15 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 15/02/2011 13:16, Alexander Pokluda wrote: I don't have any idea why the XDMCP request packets from XWin would be dropped by the network either. What I thought was interesting is that the value of Connection 4 in the XDMCP REQUEST packet from XWin in the Wireshark trace is fe80::5efe:a03:149f. I'm still familiarizing myself with IPv6, but the handy tool at ip-lookup.net shows this for that address: This IPv6 address contains an IPv4 address: Oh yes, this appears to be an ISATAP address. It seems there are some interesting things going on here, but, the modified XWin you link to at the bottom of your email works perfectly!! Thanks for testing. I'll include this change in the next release, since it seems to be doing the correct thing. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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: Can't use XDMCP, winProcEstablishConnection - ProcEstablishConnection failed, bailing shows in log
On 15/02/2011 13:16, Alexander Pokluda wrote: I don't have any idea why the XDMCP request packets from XWin would be dropped by the network either. What I thought was interesting is that the value of Connection 4 in the XDMCP REQUEST packet from XWin in the Wireshark trace is fe80::5efe:a03:149f. I'm still familiarizing myself with IPv6, but the handy tool at ip-lookup.net shows this for that address: This IPv6 address contains an IPv4 address: Oh yes, this appears to be an ISATAP address. It seems there are some interesting things going on here, but, the modified XWin you link to at the bottom of your email works perfectly!! Thanks for testing. I'll include this change in the next release, since it seems to be doing the correct thing. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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: Can't use XDMCP, winProcEstablishConnection - ProcEstablishConnection failed, bailing shows in log
Hi Jon, I don't have any idea why the XDMCP request packets from XWin would be dropped by the network either. What I thought was interesting is that the value of Connection 4 in the XDMCP REQUEST packet from XWin in the Wireshark trace is fe80::5efe:a03:149f. I'm still familiarizing myself with IPv6, but the handy tool at ip-lookup.net shows this for that address: This IPv6 address contains an IPv4 address: IPv6 compressed : FE80::5EFE:A03:149F IPv6 uncompressed : FE80:0:0:0:0:5EFE:A03:149F IPv6 fully uncompressed : FE80:::::5EFE:0A03:149F IP v4: decimal : 10.3.20.159 binary : 10100011000101001001 octal : 012.03.024.0237 hexadecimal : 0x0A.0x03.0x14.0x9F long : 167974047 IP v6 : 6 to 4 address : 2002:A03:149F:0:0:0:0:0 : 2002:A03:149F:: IPv4-mapped address : 0:0:0:0:0::10.3.20.159 : :::10.3.20.159 : :::0A03:149F IPv4-compatibility address : 0:0:0:0:0:0:10.3.20.159 : ::10.3.20.159 : ::0A03:149F It seems there are some interesting things going on here, but, the modified XWin you link to at the bottom of your email works perfectly!! Thanks for all of your help :-) On Mon, Feb 14, 2011 at 9:46 AM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On Wed, Feb 9, 2011 at 6:37 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: I wonder if you could send me privately the Wireshark .pcap files for these traces, I'd like to examine them further. On 11/02/2011 18:45, Alexander Pokluda wrote: I've attached a zip archive containing a number of files. The pcap files were created by running Wireshark on both ends while attempting to establish an XDMCP session between the hosts. Here is a description of the files: Thanks very much for these. Unfortunately, these seem to show that the XDMCP request packet leaves the machine running XWin, but doesn't arrive at the VM. I've no idea why that might be, but that suggests to me they are being dropped in your network, or between the host running the VM and the guest VM? After I took the above screenshot, I realized that I had a VirtualBox adapter with IPv6 enabled, so I disabled the VirtualBox adapter and ran the XWin command again, capturing packets on both ends. These files contain the captured packets. One interesting thing to note is that the request packet sent from XWin contains my IPv4 address converted to an IPv6 address even when IPv6 is disabled on my physical adapter. These look like link-local IPv6 addresses (prefix fe80::) to me, rather than IPv6 mapped IPv4 addresses (prefix :::)? However, this does look like a bug (or at least the code not doing what it says it does): when the -from option is used, the XDMCP request contains the specified address *and* any other addresses we have of different address families to the specified address (e.g., if we specify an IPv4 address, we get only that IPv4 address, but all the IPv6 addresses as well) I've built a snapshot which contains a change which modifies the behaviour of -from so only the specified address is included in the XDMCP request, and uploaded it at [1]. With this change, the XDMCP request sent by XWin and XMing should be nearly identical. Perhaps you could try that out and see if that makes a difference. ftp://cygwin.com/pub/cygwinx/XWin.20110214-git-d593beaadac1371e.exe.bz2 -- 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: Can't use XDMCP, winProcEstablishConnection - ProcEstablishConnection failed, bailing shows in log
On Wed, Feb 9, 2011 at 6:37 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: I wonder if you could send me privately the Wireshark .pcap files for these traces, I'd like to examine them further. On 11/02/2011 18:45, Alexander Pokluda wrote: I've attached a zip archive containing a number of files. The pcap files were created by running Wireshark on both ends while attempting to establish an XDMCP session between the hosts. Here is a description of the files: Thanks very much for these. Unfortunately, these seem to show that the XDMCP request packet leaves the machine running XWin, but doesn't arrive at the VM. I've no idea why that might be, but that suggests to me they are being dropped in your network, or between the host running the VM and the guest VM? After I took the above screenshot, I realized that I had a VirtualBox adapter with IPv6 enabled, so I disabled the VirtualBox adapter and ran the XWin command again, capturing packets on both ends. These files contain the captured packets. One interesting thing to note is that the request packet sent from XWin contains my IPv4 address converted to an IPv6 address even when IPv6 is disabled on my physical adapter. These look like link-local IPv6 addresses (prefix fe80::) to me, rather than IPv6 mapped IPv4 addresses (prefix :::)? However, this does look like a bug (or at least the code not doing what it says it does): when the -from option is used, the XDMCP request contains the specified address *and* any other addresses we have of different address families to the specified address (e.g., if we specify an IPv4 address, we get only that IPv4 address, but all the IPv6 addresses as well) I've built a snapshot which contains a change which modifies the behaviour of -from so only the specified address is included in the XDMCP request, and uploaded it at [1]. With this change, the XDMCP request sent by XWin and XMing should be nearly identical. Perhaps you could try that out and see if that makes a difference. ftp://cygwin.com/pub/cygwinx/XWin.20110214-git-d593beaadac1371e.exe.bz2 -- 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: Can't use XDMCP, winProcEstablishConnection - ProcEstablishConnection failed, bailing shows in log
PM, Alexander Pokluda apokl...@gmail.com wrote:
Sorry for the delay in my response.
No, I am not runnig the VMs locally. These VMs are being run and
managed in a lab that I don't have access to, but I am expected to use
VMs in the lab for development and testing on a new project.
I have one physical network adapter in my computer and several virtual
adapters since I do have VMware Workstation and Virtual Box installed.
The IP address of the physical adapter is a static IP address set to
10.3.20.159 with /24 subnet mask. The VM that I've been trying to
connect to has IP address 10.3.147.100 and /24 subnet mask. Running
XWin -from 10.3.20.159 -query 10.3.147.100
doesn't work. A blank window opens and eventually closes and re-opens.
This goes on indefinitely. In the attached Wireshark trace, you can
see a cycle of query-willing-request-request...-query-willing-request-request
after running this command in Cygwin:
No. Time Source Destination Protocol Info
3219 253.037685 10.3.20.159 10.3.147.100 XDMCP Query
No. Time Source Destination Protocol Info
3220 253.043332 10.3.147.100 10.3.20.159 XDMCP
Willing
No. Time Source Destination Protocol Info
3331 254.061501 10.3.20.159 10.3.147.100 XDMCP
Request
No. Time Source Destination Protocol Info
3361 257.044353 10.3.20.159 10.3.147.100 XDMCP
Request
[...]
I've also attached a Wireshark trace capturing when using XLaunch to
start an XDMCP session using Xming. In this trace, you can see the
expected query-willing-request-accept sequence:
No. Time Source Destination Protocol Info
129 14.553230 10.3.20.159 10.3.147.100 XDMCP Query
No. Time Source Destination Protocol Info
130 14.554923 10.3.147.100 10.3.20.159 XDMCP
Willing
No. Time Source Destination Protocol Info
135 15.226412 10.3.20.159 10.3.147.100 XDMCP
Request
No. Time Source Destination Protocol Info
136 15.231235 10.3.147.100 10.3.20.159 XDMCP Accept
Here is the output of ipconfig:
C:\Users\alpokludaipconfig
Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::71ea:6924:9397:cfc5%14
IPv4 Address. . . . . . . . . . . : 10.3.20.159
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.3.20.1
Ethernet adapter VMware Network Adapter VMnet1:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::39b9:7291:332c:73ee%16
IPv4 Address. . . . . . . . . . . : 192.168.245.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter VMware Network Adapter VMnet8:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::91b6:e77b:7aef:6d88%18
IPv4 Address. . . . . . . . . . . : 192.168.127.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::7cf6:24ee:7c05:7c06%22
IPv4 Address. . . . . . . . . . . : 192.168.68.1
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
Tunnel adapter isatap.{9D67124F-C8D9-45C5-9AC5-FCF5D2D8625F}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{D64E1692-0777-4BA9-AD59-6BC4B536D5AB}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{95AFDF32-DF73-4F97-A9E6-122D78033AED}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{31D1B58C-F013-4228-B2B6-C75660B9C6AA}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
and 'route print':
C:\Users\alpokludaroute print
===
Interface List
14...1c c1 de 5d bb 1b ..Intel(R) 82578DM Gigabit Network Connection
16...00 50 56 c0 00 01 ..VMware Virtual Ethernet Adapter for VMnet1
18...00 50 56 c0 00 08 ..VMware Virtual Ethernet Adapter for VMnet8
22...08 00 27 00 58 7b ..VirtualBox Host-Only Ethernet Adapter
1...Software Loopback Interface 1
24...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
17...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
19
Re: Can't use XDMCP, winProcEstablishConnection - ProcEstablishConnection failed, bailing shows in log
Firstly, thanks very much for taking the time to collect so much detailed information about this problem. On 09/02/2011 15:36, Alexander Pokluda wrote: Here is an excerpt from /var/log/messages on the VM that I'm trying to connect to with XWin. This is what appears in the log after running XWin -from 10.3.20.159 -query 10.3.147.100 Feb 8 11:22:08 dev01 gdm[4097]: gdm_xdmcp_decode: Received opcode QUERY from client 10.3.20.159 Feb 8 11:22:08 dev01 gdm[4097]: gdm_xdmcp_handle_query: Opcode 2 from 10.3.20.159 Feb 8 11:22:08 dev01 gdm[4097]: gdm_xdmcp_host_allow: client-hostname is ci001138531.xxx.net Feb 8 11:22:08 dev01 gdm[4097]: gdm_xdmcp_send_willing: Sending WILLING to 10.3.20.159 Feb 8 11:24:16 dev01 gdm[4097]: gdm_xdmcp_decode: Received opcode QUERY from client 10.3.20.159 Feb 8 11:24:16 dev01 gdm[4097]: gdm_xdmcp_handle_query: Opcode 2 from 10.3.20.159 [snip] It seems that the REQUEST message sent by XWin somehow gets lost. Although it shows up in the Wireshark trace, it never shows up in the log on the VM. The other alternative is that the REQUEST arrives at the VM, but gdm doesn't like the contents for some reason. Possibly you could check that by wiresharking at that end. On Tue, Feb 8, 2011 at 5:00 PM, Alexander Pokluda apokl...@gmail.com wrote: Sorry for the delay in my response. No, I am not runnig the VMs locally. These VMs are being run and managed in a lab that I don't have access to, but I am expected to use VMs in the lab for development and testing on a new project. I have one physical network adapter in my computer and several virtual adapters since I do have VMware Workstation and Virtual Box installed. The IP address of the physical adapter is a static IP address set to 10.3.20.159 with /24 subnet mask. The VM that I've been trying to connect to has IP address 10.3.147.100 and /24 subnet mask. Running XWin -from 10.3.20.159 -query 10.3.147.100 doesn't work. A blank window opens and eventually closes and re-opens. This goes on indefinitely. In the attached Wireshark trace, you can see a cycle of query-willing-request-request...-query-willing-request-request after running this command in Cygwin: No. TimeSourceDestination Protocol Info 3219 253.037685 10.3.20.159 10.3.147.100 XDMCPQuery No. TimeSourceDestination Protocol Info 3220 253.043332 10.3.147.100 10.3.20.159 XDMCP Willing No. TimeSourceDestination Protocol Info 3331 254.061501 10.3.20.159 10.3.147.100 XDMCP Request No. TimeSourceDestination Protocol Info 3361 257.044353 10.3.20.159 10.3.147.100 XDMCP Request [...] I've also attached a Wireshark trace capturing when using XLaunch to start an XDMCP session using Xming. In this trace, you can see the expected query-willing-request-accept sequence: No. TimeSourceDestination Protocol Info 129 14.553230 10.3.20.159 10.3.147.100 XDMCPQuery No. TimeSourceDestination Protocol Info 130 14.554923 10.3.147.100 10.3.20.159 XDMCP Willing No. TimeSourceDestination Protocol Info 135 15.226412 10.3.20.159 10.3.147.100 XDMCP Request No. TimeSourceDestination Protocol Info 136 15.231235 10.3.147.100 10.3.20.159 XDMCP Accept I wonder if you could send me privately the Wireshark .pcap files for these traces, I'd like to examine them further. A significant difference is in the Connections data sent in the REQUEST packet (which is a list of network addresses the requestor knows for itself) Xming 6.9: X Display Manager Control Protocol Version: 1 Opcode: Request (0x0007) Message length: 81 Display number: 0 Connections (1) Authentication name: Authentication data (0 bytes) Authorization names (3) Manufacturer display ID: vs. XWin X Display Manager Control Protocol Version: 1 Opcode: Request (0x0007) Message length: 220 Display number: 0 Connections (9) Authentication name: Authentication data (0 bytes) Authorization names (2) Manufacturer display ID: I could understand 8 (the total number of IPv4 and IPv6 interfaces your host has), if you weren't using -from, but 9 is a bit confusing. I would expect Xming 6.9 to report fewer interfaces, since it was built without IPv6 support, but I'm not sure why it's only reporting 1, if you aren't using -from. It seems likely that IPv6 support in XWin is the difference which prevents things from working correctly. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe
Re: Can't use XDMCP, winProcEstablishConnection - ProcEstablishConnection failed, bailing shows in log
On 28/01/2011 20:23, Alexander Pokluda wrote: The Windows PC that I'm using is on a different subnet from the VMs that I need to connect to (10.3.20.159/24), so does that mean it's not possible to use Cygwin/X in this case? (Changing either subnet is not an option). Ah, I had assumed that you were running the VMs locally with some form of virtual networking. It certainly should be possible to configure XWin to work in your case. If you have multiple network interfaces on your PC, then it's probably just a question of using the -from option to ensure traffic is sent with the correct source address. If that doesn't fix it, perhaps you could provide a wireshark trace of the connection attempt and some more details of the networking configuration (e.g. output of 'ipconfig' and 'route print') On Fri, Jan 28, 2011 at 3:16 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 28/01/2011 19:19, Alexander Pokluda wrote: I've been trying for a while to get Cygwin/X working with XDMCP for quite a while without any success; however, I am able to conenct without any any problem using Xming 6.9. I'm using a Windows 7 PC to connect to a different Linux VMs running CentOS 5.5. After starting XWin from the command line (either directly or using startxdmcp.bat), a window opens up that contains nothing but black. At first when I move the cursor over the winodow, it just disappears but after a while, the cursor will appear as an X and the following shows up in the log file: [266377.900] winProcEstablishConnection - Hello [266377.900] winProcEstablishConnection - ProcEstablishConnection failed, bailing. [266385.653] winAboutDlgProc - WM_COMMAND - IDOK or IDCANCEL [266489.784] XDM: too many retransmissions, declaring session dead Any help would be greatly appreciated. I've included part of the log from one attempt to connect to one of the CentOS 5.5 VMs that I can connect to with Xming using XDMCP. [266616.722] XDM: too many retransmissions, declaring session dead Possibly you need to use -query 10.3.147.100 -from corresponding local IP for the subnet containing that IP address Xming has a patch applied which adds some more intelligence to the way the local IP address is chosen, but unfortunately that is written to use the winsock API directly, so can't be used directly in XWin. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Can't use XDMCP, winProcEstablishConnection - ProcEstablishConnection failed, bailing shows in log
Hi, I've been trying for a while to get Cygwin/X working with XDMCP for quite a while without any success; however, I am able to conenct without any any problem using Xming 6.9. I'm using a Windows 7 PC to connect to a different Linux VMs running CentOS 5.5. After starting XWin from the command line (either directly or using startxdmcp.bat), a window opens up that contains nothing but black. At first when I move the cursor over the winodow, it just disappears but after a while, the cursor will appear as an X and the following shows up in the log file: [266377.900] winProcEstablishConnection - Hello [266377.900] winProcEstablishConnection - ProcEstablishConnection failed, bailing. [266385.653] winAboutDlgProc - WM_COMMAND - IDOK or IDCANCEL [266489.784] XDM: too many retransmissions, declaring session dead Any help would be greatly appreciated. I've included part of the log from one attempt to connect to one of the CentOS 5.5 VMs that I can connect to with Xming using XDMCP. Sincerely, Alexander Pokluda -- -- Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.9.3.0 (10903000) Package version 1.9.3-2 built 2011-01-05 XWin was started with the following command line: xwin -query 10.3.147.100 ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1680 h 1050 winInitializeDefaultScreens - native DPI x 96 y 96 [266361.832] winInitializeScreens - 1 [266361.832] winInitializeScreen - 0 [266361.832] (II) xorg.conf is not supported [266361.832] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [266361.832] LoadPreferences: /cygdrive/c/Users/alpokluda/.XWinrc not found [266361.832] LoadPreferences: Loading /etc/X11/system.XWinrc [266361.832] LoadPreferences: Done parsing the configuration file... [266361.832] winGetDisplay: DISPLAY=:0.0 [266361.832] winDetectSupportedEngines - Windows NT/2000/XP [266361.863] winDetectSupportedEngines - DirectDraw installed [266361.863] winDetectSupportedEngines - Allowing PrimaryDD [266361.863] winDetectSupportedEngines - DirectDraw4 installed [266361.894] winDetectSupportedEngines - Returning, supported engines 001f [266361.894] winSetEngine - Using Shadow DirectDraw NonLocking [266361.894] winScreenInit - Using Windows display depth of 32 bits per pixel [266362.019] winFinishScreenInitFB - Masks: 00ff ff00 00ff [266362.019] Screen 0 added at virtual desktop coordinate (1680,0). [266362.019] MIT-SHM extension disabled due to lack of kernel support [266362.035] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [266362.081] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so [266362.081] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [266362.097] [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! [266362.097] [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [266362.097] [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! [266362.440] winPointerWarpCursor - Discarding first warp: 837 496 [266362.440] (--) 3 mouse buttons found [266362.440] (--) Setting autorepeat to delay=500, rate=31 [266362.440] (--) Windows keyboard layout: 0409 (0409) US, type 4 [266362.440] (--) Found matching XKB configuration English (USA) [266362.440] (--) Model = pc105 Layout = us Variant = none Options = none [266362.440] Rules = base Model = pc105 Layout = us Variant = none Options = none [266377.900] winProcEstablishConnection - Hello [266377.900] winProcEstablishConnection - ProcEstablishConnection failed, bailing. [266385.653] winAboutDlgProc - WM_COMMAND - IDOK or IDCANCEL [266489.784] XDM: too many retransmissions, declaring session dead [266489.940] 5 XSELINUXs still allocated at reset [266489.940] SCREEN: 0 objects of 72 bytes = 0 total bytes 0 private allocs [266489.940] DEVICE: 4 objects of 16 bytes = 64 total bytes 0 private allocs [266489.940] CLIENT: 0 objects of 140 bytes = 0 total bytes 0 private allocs [266489.940] WINDOW: 0 objects of 64 bytes = 0 total bytes 0 private allocs [266489.940] PIXMAP: 1 objects of 28 bytes = 28 total bytes 0 private allocs [266489.940] GC: 0 objects of 52 bytes = 0 total bytes 0 private allocs [266489.940] CURSOR: 0 objects of 4 bytes = 0 total bytes 0 private allocs [266489.940] CURSOR_BITS: 0 objects of 4 bytes = 0 total bytes 0 private allocs [266489.940] DBE_WINDOW: 0 objects of 12 bytes = 0 total bytes 0 private allocs [266489.940] TOTAL: 5 objects, 92 bytes, 0 allocs [266489.940] 4 DEVICEs still allocated at reset [266489.940] DEVICE: 4 objects of 16 bytes = 64 total bytes 0 private allocs [266489.940] CLIENT: 0 objects of 140 bytes = 0 total bytes 0 private allocs [266489.940] WINDOW: 0 objects of 64 bytes = 0 total bytes 0 private allocs [266489.940] PIXMAP: 1 objects of 28 bytes = 28 total bytes 0 private allocs
Re: 1.7.1: no xdmcp login prompt after upgrade
Am 15.01.2010 21:32, schrieb Paxton, Michael: After upgrading to Cygwin/X 1.7.1, XDMCP query to any remote host no longer produces a login prompt. All XDMCP connections functioned correctly prior to upgrade. Examination of an iptrace report (ipreport10.out) on the remote host shows that Cygwin/X is not continuing the connection sequence after the remote host replies to the initial port 177 communication. Did you try to do use numeric ip addresses and the -from switch to see if it produces a different result? Like: XWin -query xdmcp.numeric.host.address -from your.own.numeric.address -- 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: 1.7.1: no xdmcp login prompt after upgrade
That is a good suggestion; I will try that this weekend. Should that prove to work, would that then suggest something in Cygwin/X's name resolution is broken? This worked as-is under 1.5.25; it is broken under 1.7.1 - what changed? Respectfully, D. Michael Paxton, Esq., MBA FBI/CJIS Systems Agency Information Security Officer Indiana State Police (317) 232-5686 -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Holger Krull Sent: Friday, 22 January 2010 08:47 To: cygwin-xfree@cygwin.com Subject: Re: 1.7.1: no xdmcp login prompt after upgrade Am 15.01.2010 21:32, schrieb Paxton, Michael: After upgrading to Cygwin/X 1.7.1, XDMCP query to any remote host no longer produces a login prompt. All XDMCP connections functioned correctly prior to upgrade. Examination of an iptrace report (ipreport10.out) on the remote host shows that Cygwin/X is not continuing the connection sequence after the remote host replies to the initial port 177 communication. Did you try to do use numeric ip addresses and the -from switch to see if it produces a different result? Like: XWin -query xdmcp.numeric.host.address -from your.own.numeric.address -- 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/ -- 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: 1.7.1: no xdmcp login prompt after upgrade
Tony, As I noted in my problem, the iptrace ran on the remote host and therefore is from the perspective of the remote. Nonetheless, each packet in the trace report displays both the source and destination IP addresses and TCP/UDP ports. You correctly observe that you are getting farther than I, in that I never receive the logon prompt. By the way, although my iptrace report is from an AIX remote host, I have tested this against RHEL3 and OEL5 remote hosts with the same results. Again, my Cygwin/X 1.5.25 client logs on and functions correctly to all remote hosts. Respectfully, D. Michael Paxton, Esq., MBA FBI/CJIS Systems Agency Information Security Officer Indiana State Police (317) 232-5686 -Original Message- From: Bennett, Tony bennett.t...@con-way.com Sent: Friday, 15 January 2010 17:45 To: 'cygwin-xfree@cygwin.com' Subject: 1.7.1: no xdmcp login prompt after upgrade Is your IPTRACE from the remote host's perspective, or from your cygwin-X perspective...??? I ask because I too am using 1.7.3 with -query and I'm having problems... but only after successfully logging onto the remote system. Meaning I'm getting further than you. Here's my startup (note I'm using a fontserver on the XDM host): XWin -logverbose 255 \ -ac \ -query dmsdev.con-way.com \ -fp \tcp/dmsdev.con-way.com:8000,/usr/share/fonts/100dpi/,/usr/share/fonts/ 75dpi/,/usr/share/fonts/Type1/\ Thanks, -tony -- 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: 1.7.1: no xdmcp login prompt after upgrade
D. Michael, I must admit that my frustration with this problem, accompanied by the loss of my windows box with the 1.5 install, has caused me to look elsewhere for a solution. I have installed XMING, and it seems to work just fine. Unfortunately, XMING is an XSERVER only... so, I've kept my Cygwin-xfree install for the other X tools. I'll keep monitoring this list in the hopes of a fix to the problem. I might add that I couldn't get XMING to work until I was able to specify to its Xserver the address of my Font-Server. -tony -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Paxton, Michael Sent: Thursday, January 21, 2010 9:53 AM To: cygwin-xfree@cygwin.com Subject: RE: 1.7.1: no xdmcp login prompt after upgrade Tony, As I noted in my problem, the iptrace ran on the remote host and therefore is from the perspective of the remote. Nonetheless, each packet in the trace report displays both the source and destination IP addresses and TCP/UDP ports. You correctly observe that you are getting farther than I, in that I never receive the logon prompt. By the way, although my iptrace report is from an AIX remote host, I have tested this against RHEL3 and OEL5 remote hosts with the same results. Again, my Cygwin/X 1.5.25 client logs on and functions correctly to all remote hosts. Respectfully, D. Michael Paxton, Esq., MBA FBI/CJIS Systems Agency Information Security Officer Indiana State Police (317) 232-5686 -Original Message- From: Bennett, Tony bennett.t...@con-way.com Sent: Friday, 15 January 2010 17:45 To: 'cygwin-xfree@cygwin.com' Subject: 1.7.1: no xdmcp login prompt after upgrade Is your IPTRACE from the remote host's perspective, or from your cygwin-X perspective...??? I ask because I too am using 1.7.3 with -query and I'm having problems... but only after successfully logging onto the remote system. Meaning I'm getting further than you. Here's my startup (note I'm using a fontserver on the XDM host): XWin -logverbose 255 \ -ac \ -query dmsdev.con-way.com \ -fp \tcp/dmsdev.con-way.com:8000,/usr/share/fonts/100dpi/,/usr/share/fonts/ 75dpi/,/usr/share/fonts/Type1/\ Thanks, -tony -- 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/ -- 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: 1.7.1: no xdmcp login prompt after upgrade
Tony, Try installing from http://cygwin.com/win-9x.html to get version 1.5.25. Although it states it is only for supporting Windows 95/98/Me, it may work to get your functionality back. As for me, should no solution be forthcoming to resolve my issue, I will likely do the same. Respectfully, D. Michael Paxton, Esq., MBA FBI/CJIS Systems Agency Information Security Officer Indiana State Police (317) 232-5686 -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Bennett, Tony Sent: Thursday, 21 January 2010 14:16 To: cygwin-xfree@cygwin.com Subject: RE: 1.7.1: no xdmcp login prompt after upgrade D. Michael, I must admit that my frustration with this problem, accompanied by the loss of my windows box with the 1.5 install, has caused me to look elsewhere for a solution. I have installed XMING, and it seems to work just fine. Unfortunately, XMING is an XSERVER only... so, I've kept my Cygwin-xfree install for the other X tools. I'll keep monitoring this list in the hopes of a fix to the problem. I might add that I couldn't get XMING to work until I was able to specify to its Xserver the address of my Font-Server. -tony -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Paxton, Michael Sent: Thursday, January 21, 2010 9:53 AM To: cygwin-xfree@cygwin.com Subject: RE: 1.7.1: no xdmcp login prompt after upgrade Tony, As I noted in my problem, the iptrace ran on the remote host and therefore is from the perspective of the remote. Nonetheless, each packet in the trace report displays both the source and destination IP addresses and TCP/UDP ports. You correctly observe that you are getting farther than I, in that I never receive the logon prompt. By the way, although my iptrace report is from an AIX remote host, I have tested this against RHEL3 and OEL5 remote hosts with the same results. Again, my Cygwin/X 1.5.25 client logs on and functions correctly to all remote hosts. Respectfully, D. Michael Paxton, Esq., MBA FBI/CJIS Systems Agency Information Security Officer Indiana State Police (317) 232-5686 -Original Message- From: Bennett, Tony Bennett dot Tony at con-way dot com Sent: Friday, 15 January 2010 17:45 To: 'cygwin-xfree@cygwin.com' Subject: 1.7.1: no xdmcp login prompt after upgrade Is your IPTRACE from the remote host's perspective, or from your cygwin-X perspective...??? I ask because I too am using 1.7.3 with -query and I'm having problems... but only after successfully logging onto the remote system. Meaning I'm getting further than you. Here's my startup (note I'm using a fontserver on the XDM host): XWin -logverbose 255 \ -ac \ -query dmsdev.con-way.com \ -fp \tcp/dmsdev.con-way.com:8000,/usr/share/fonts/100dpi/,/usr/share/fonts/ 75dpi/,/usr/share/fonts/Type1/\ Thanks, -tony -- 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: 1.7.1: no xdmcp login prompt after upgrade
On 01/21/2010 02:24 PM, Paxton, Michael wrote: Tony, Try installing from http://cygwin.com/win-9x.html to get version 1.5.25. Although it states it is only for supporting Windows 95/98/Me, it may work to get your functionality back. This is 1.5.25 as you noted and, as such, will work as well or as poorly as 1.5.25 always has. As a warning, 1.5.x doesn't have a great record on W7 machines. And I have to add the obligatory warning that 1.5.25 is a dead branch so you'll see no further development or bug fixes there. The take-away from this last statement is that you should keep an eye on 1.7.x and, to the extent possible, help resolve problems that you find there so you have an upgrade path if/when 1.5.25 lets you down. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: 1.7.1: no xdmcp login prompt after upgrade
Is your IPTRACE from the remote host's perspective, or from your cygwin-X perspective...??? I ask because I too am using 1.7.3 with -query and I'm having problems... but only after successfully logging onto the remote system. -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Paxton, Michael Sent: Friday, January 15, 2010 12:33 PM To: cygwin-xfree@cygwin.com Subject: 1.7.1: no xdmcp login prompt after upgrade After upgrading to Cygwin/X 1.7.1, XDMCP query to any remote host no longer produces a login prompt. All XDMCP connections functioned correctly prior to upgrade. Examination of an iptrace report (ipreport10.out) on the remote host shows that Cygwin/X is not continuing the connection sequence after the remote host replies to the initial port 177 communication. To verify that X connectivity was still available on the remote host, connection was attempted from another local system with Cygwin/X 1.5.25. That connection functioned as expected, and its IP exchange was also captured on the remote host as a benchmark. (An attempt to include that traced was rejected by mailer-dae...@sourceware.org). Please advise as to any fix or workaround available. Alternately, please advise as to the best way to revert to Cygwin/X 1.5.25. Respectfully, D. Michael Paxton, Esq., M.B.A. FBI/CJIS Systems Agency Information Security Officer Indiana State Police (317) 232-5686 Is your IPTRACE from the remote host's perspective, or from your cygwin-X perspective...??? I ask because I too am using 1.7.3 with -query and I'm having problems... but only after successfully logging onto the remote system. Meaning I'm getting further than you. Here's my startup (note I'm using a fontserver on the XDM host): XWin -logverbose 255 \ -ac \ -query dmsdev.con-way.com \ -fp \tcp/dmsdev.con-way.com:8000,/usr/share/fonts/100dpi/,/usr/share/fonts/75dpi/,/usr/share/fonts/Type1/\ Thanks, -tony -- 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/
XDMCP connects successfully but freezes shortly thereafter - Was: What is replacement for the -kb Xwin startup parameter
I thought I'd change the subject and describe the problem in a little better detail and perhaps get a response... Additional info: - On one PC, I have XWin release 1.5.3.0 (20090222) installed and working - That release uses the following command line: XWin -query my_AIX_SERVER_NAME -ac -clipboard -kb -fp FOLLOWED-BY-A-FONT-PATH-TO-A-FONTSERVER - On another PC, I have XWin Release 1.7.3.0 (10703000) installed - That release will NOT allow me to use the -kb argument, so I have eliminated the -kb Here is the behavior I get with 1.7.3.0: - Window opens up... the CDE logon window from the AIX_SERVER comes up - I can successfully logon to the CDE logon window - On the CDE Desktop (on my AIX 5.3 system), I can right-click to get up the root menu, and select an option that opens up an SSH aixterm window (an AIX version of xterm) - I can successfully sign-on to that aixterm window - I can successfully run commands on that window - BUT as soon as I click on anything other that the aixterm window everything freezes... - I have to exit by clicking the x in the upper right corner of the root window or right click on the X entry in the task-bar and select close - The XWin.0.log gives no clues to the problem - The CDE startlog only contains this: Mon Jan 11 11:13:19 2010 dtsession: Screen lock when the screen saver is turned on is not available on this server. Your screen will not be locked when the screen saver is turned on. Mon Jan 11 11:15:51 2010 dtsession: Connection to server lost - exiting. Any help will be greatly appreciated, since I can no longer use XWin... ...and am forced to use putty... Thanks, -tony -Original Message- From: Bennett, Tony Sent: Wednesday, January 06, 2010 9:14 PM To: 'cygwin-xfree@cygwin.com' Subject: What is replacement for the -kb Xwin startup parameter I a using Xwin to connect to an AIX system using XDMCP. This was working fine on an old version of Xwin, As long as I used the -kb command line argument (there was an old post in the FAQ, suggesting that parameter As the workaround for AIX not handling keyboard extensions). I just downloaded 1.7.3.0 on another Win-XP system, and discovered That -kb is no longer supported. Without that argument, I am able To successfully connect using XDMCP, but after opening my 2nd Xterm, the window freezes up... neither mouse or keyboard Seems to function with it (which was the same symptom I had on The old version prior to adding the -kb startup parm. Suggestions are welcome. -tony -- 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: 1.5.25-15: 100% CPU under xdmcp and Gnome
On 29/10/2009 00:08, Quinn Jones wrote: Larry Hall (Cygwin X) wrote: Any interest in trying Cygwin 1.7http://cygwin.com/#beta-test? I don't know if it would help but it has a newer X and friends and is actively maintained. One day in and it seems to be helping - no problems to report so far and the original problem has gone away with 1.7. Thanks for the suggestion. Yes, the clipboard integration code in 1.5.x has some known problems, but there will probably be no more X server releases for Cygwin/X unless someone else volunteers to do it. -- 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: 1.5.25-15: 100% CPU under xdmcp and Gnome
From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- ow...@cygwin.com] On Behalf Of Jon TURNEY Sent: Thursday, October 29, 2009 7:11 AM Yes, the clipboard integration code in 1.5.x has some known problems, but there will probably be no more X server releases for Cygwin/X unless someone else volunteers to do it. Do you mean just for 1.5, or also for 1.7? Thanks, Mike
Re: 1.5.25-15: 100% CPU under xdmcp and Gnome
On 29/10/2009 17:01, Mike Ayers wrote: From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- ow...@cygwin.com] On Behalf Of Jon TURNEY Sent: Thursday, October 29, 2009 7:11 AM Yes, the clipboard integration code in 1.5.x has some known problems, but there will probably be no more X server releases for Cygwin/X unless someone else volunteers to do it. Do you mean just for 1.5, or also for 1.7? Oops. Email proof reading failure there. Yes, I just meant to say that there are unlikely to be more X server releases made for Cygwin 1.5 -- 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: Re: 1.5.25-15: 100% CPU under xdmcp and Gnome
Larry Hall (Cygwin X) wrote: Any interest in trying Cygwin 1.7 http://cygwin.com/#beta-test? I don't know if it would help but it has a newer X and friends and is actively maintained. One day in and it seems to be helping - no problems to report so far and the original problem has gone away with 1.7. Thanks for the suggestion. Quinn -- 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/
1.5.25-15: 100% CPU under xdmcp and Gnome
I am running Cygwin-X on Windows XP, connecting to a Gentoo workstation via xdmcp. If I connect to a session running Gnome one processor on my Windows machine spikes to 100% usage and stays there. Memory use appears to remain constant and the X-session is responsive. The CPU doesn't spike while GDM is active, just while the Gnome session is active. If I use a different window manager, such as Blackbox, the CPU does not spike. Other activities on the XP machine seem normal and other programs seem normal. I have closed xdmcp session, close and restarted Cygwin, and rebooted XP. I ran Windows Update last Friday and shut down my Windows machine for the weekend. I didn't notice anything amiss before then, though I cannot guarantee there wasn't a problem. There were some Gnome updates in Gentoo that I emerged recently, I think it was just at the beginning of last week or the previous week, but I don't recall noticing the CPU spiking afterward. In order to try solving the problem I ran the Cygwin setup program and let it install all new updates; when that didn't work I re-ran and force-reinstalled everything. The core Cygwin DLL and X libraries were not updated - they're current according to the setup program and the updates that were found were for some utilities (I didn't record which ones). I have tried googling this with terms like cygwin xdmcp gnome cpu 100% and a few variations of that but I haven't found anything relevant (or recent). Is this a Cygwin problem? CPU usage is normal on the remote Linux box (the client, in X parlance), and it seems coincident with MS updates so it seems reasonable that it's not a direct problem with Gnome per se but with the XP machine (the server). Attached is the output of cygcheck Cygwin Configuration Diagnostics Current System Time: Tue Oct 27 16:28:06 2009 Windows XP Professional Ver 5.1 Build 2600 Service Pack 3 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\Perl\bin\ c:\WINDOWS\system32 c:\WINDOWS c:\WINDOWS\System32\Wbem c:\Program Files\PuTTY c:\Program Files\Sysinternals c:\Program Files\Support Tools\ c:\Program Files\QuickTime\QTSystem c:\Program Files\WinZip c:\Program Files\Common Files\GTK\2.0\bin c:\Program Files\Subversion\bin c:\Program Files\TortoiseSVN\bin c:\Program Files\QuickTime\QTSystem\ Output from C:\cygwin\bin\id.exe (nontsec) UID: 11862(username) GID: 10545(mkgroup-l-d) 0(root) 544(Administrators) 545(Users) 1004(Debugger Users)10545(mkgroup-l-d) Output from C:\cygwin\bin\id.exe (ntsec) UID: 11862(username) GID: 10545(mkgroup-l-d) 0(root) 544(Administrators) 545(Users) 1004(Debugger Users)10545(mkgroup-l-d) SysDir: C:\WINDOWS\system32 WinDir: C:\WINDOWS USER = 'username' PWD = '/cygdrive/c/Documents and Settings/username' HOME = '/cygdrive/c/Documents and Settings/username' MAKE_MODE = 'unix' HOMEPATH = '\Documents and Settings\username' MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man' APPDATA = 'C:\Documents and Settings\username\Application Data' HOSTNAME = 'hostname' TERM = 'cygwin' PROCESSOR_IDENTIFIER = 'x86 Family 15 Model 6 Stepping 4, GenuineIntel' WINDIR = 'C:\WINDOWS' OLDPWD = '/usr/bin' USERDOMAIN = 'domain' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\Documents and Settings\All Users' APR_ICONV_PATH = 'C:\Program Files\Subversion\iconv' TEMP = '/cygdrive/c/DOCUME~1/username/LOCALS~1/Temp' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' QTJAVA = 'C:\Program Files\Java\jre6\lib\ext\QTJava.zip' USERNAME = 'username' QWT_HOME = 'C:\Qantom\WET' PROCESSOR_LEVEL = '15' FP_NO_HOST_CHECK = 'NO' SYSTEMDRIVE = 'C:' __COMPAT_LAYER = 'EnableNXShowUI ' USERPROFILE = 'C:\Documents and Settings\username' CLIENTNAME = 'Console' PS1 = '\[\e]0;\w\a\]\n\[\e[32m\...@\h \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = '\\WZDC2' PROCESSOR_ARCHITECTURE = 'x86' !C: = 'C:\cygwin\bin' SHLVL = '1' USERDNSDOMAIN = 'localhost.localdomain' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' HOMEDRIVE = 'C:' PROMPT = '$P$G' COMSPEC = 'C:\WINDOWS\system32\cmd.exe' TMP = '/cygdrive/c/DOCUME~1/username/LOCALS~1/Temp' SYSTEMROOT = 'C:\WINDOWS' PRINTER = '\\WZFS1\HP LaserJet 4' CVS_RSH = '/bin/ssh' PROCESSOR_REVISION = '0604' CLASSPATH = '.;C:\Program Files\Java\jre6\lib\ext\QTJava.zip' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:' PROGRAMFILES = 'C:\Program Files' NUMBER_OF_PROCESSORS = '2' SESSIONNAME = 'Console' COMPUTERNAME = 'hostname' _ = '/usr/bin/cygcheck' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE
Re: 1.5.25-15: 100% CPU under xdmcp and Gnome
On 10/27/2009 06:21 PM, Quinn wrote: I am running Cygwin-X on Windows XP, connecting to a Gentoo workstation via xdmcp. If I connect to a session running Gnome one processor on my Windows machine spikes to 100% usage and stays there. Memory use appears to remain constant and the X-session is responsive. The CPU doesn't spike while GDM is active, just while the Gnome session is active. snip Any interest in trying Cygwin 1.7 http://cygwin.com/#beta-test? I don't know if it would help but it has a newer X and friends and is actively maintained. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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/
xdmcp cygwin 1.7 vista problem
When trying to connect to a linux sytem from a Vista using xdmcp i get a strange error. 2009-09-07 12:06:51 XDMCP fatal error: Session failed Session 173248003 failed for display 192.168.0.102:0: cannot open display As you can see from my network config, I have no adapter on this network address. I am using a wirless connection with ipadress 192.168.1.106. The same version of cygwin works flawlessly from a wired XP box. $ipconfig IP-konfiguration f”r Windows Ethernet-anslutning Anslutning till lokalt n„tverk 2: Anslutningsspecifika DNS-suffix . : IPv4-adress . . . . . . . . . . . : 169.254.2.2 N„tmask . . . . . . . . . . . . . : 255.255.255.0 Standard-gateway. . . . . . . . . : Tr†dl”s anslutning Tr†dl”s n„tverksanslutning: Anslutningsspecifika DNS-suffix . : L„nklokal IPv6-adress . . . . . . : fe80::348f:ddce:6dd8:ebe1%12 IPv4-adress . . . . . . . . . . . : 192.168.1.106 N„tmask . . . . . . . . . . . . . : 255.255.255.0 Standard-gateway. . . . . . . . . : 192.168.1.1 Ethernet-anslutning Anslutning till lokalt n„tverk: Tillst†nd . . . . . . . . . . . . : Fr†nkopplad Anslutningsspecifika DNS-suffix . : Ethernet-anslutning VMware Network Adapter VMnet1: Anslutningsspecifika DNS-suffix . : L„nklokal IPv6-adress . . . . . . : fe80::5d03:e9c0:3c9:faaa%21 IPv4-adress . . . . . . . . . . . : 192.168.223.1 N„tmask . . . . . . . . . . . . . : 255.255.255.0 Standard-gateway. . . . . . . . . : Ethernet-anslutning VMware Network Adapter VMnet8: Anslutningsspecifika DNS-suffix . : L„nklokal IPv6-adress . . . . . . : fe80::6167:7316:568a:d4bb%23 IPv4-adress . . . . . . . . . . . : 192.168.32.1 N„tmask . . . . . . . . . . . . . : 255.255.255.0 Standard-gateway. . . . . . . . . : Tunnelanslutning: Anslutning till lokalt n„tverk* 11: Tillst†nd . . . . . . . . . . . . : Fr†nkopplad Anslutningsspecifika DNS-suffix . : Tunnelanslutning: Anslutning till lokalt n„tverk* 6: Anslutningsspecifika DNS-suffix . : IPv6-adress . . . . . . . . . . . : 2001:0:cf2e:3096:1c79:bb9:3f57:fe95 L„nklokal IPv6-adress . . . . . . : fe80::1c79:bb9:3f57:fe95%10 Standard-gateway. . . . . . . . . : :: Tunnelanslutning: Anslutning till lokalt n„tverk* 7: Tillst†nd . . . . . . . . . . . . : Fr†nkopplad Anslutningsspecifika DNS-suffix . : Tunnelanslutning: Anslutning till lokalt n„tverk* 13: Tillst†nd . . . . . . . . . . . . : Fr†nkopplad Anslutningsspecifika DNS-suffix . : Tunnelanslutning: Anslutning till lokalt n„tverk* 15: Tillst†nd . . . . . . . . . . . . : Fr†nkopplad Anslutningsspecifika DNS-suffix . : Tunnelanslutning: Anslutning till lokalt n„tverk* 16: Tillst†nd . . . . . . . . . . . . : Fr†nkopplad Anslutningsspecifika DNS-suffix . : -- 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: xdmcp cygwin 1.7 vista problem
On 07/09/2009 11:37, Mårten Gustafsson wrote: When trying to connect to a linux sytem from a Vista using xdmcp i get a strange error. 2009-09-07 12:06:51 XDMCP fatal error: Session failed Session 173248003 failed for display 192.168.0.102:0: cannot open display As you can see from my network config, I have no adapter on this network address. I am using a wirless connection with ipadress 192.168.1.106. The same version of cygwin works flawlessly from a wired XP box. Hmm You may find that using the -from command line parameter (documented in 'man Xserver') to force the local address used may help, but it's still a bit mysterious where this address comes from... Perhaps you could oblige me with the output from Corinna's test program which dumps getaddrinfo output [1] [1] http://cygwin.com/ml/cygwin-xfree/2009-07/msg2.html −from local‐address specifies the local address to connect from (useful if the connecting host has multiple network interfaces). The local‐address may be expressed in any form acceptable to the host platform’s gethostbyname(3) implementation. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
Fwd: SV: xdmcp cygwin 1.7 vista problem
I forgot to set the Reply-To: correctly
Original Message
Subject: SV: xdmcp cygwin 1.7 vista problem
Date: Mon, 7 Sep 2009 15:37:23 +0200
From: Mårten Gustafsson
To: 'Jon TURNEY'
Hi Jon
There is a reported interface with this network address. I also have a VmWare
workstation installed using network addresses 192.168.233.0 and 192.168.32.0.
Name : {A25BE539-596E-4515-8BB0-1079F18C3634}
Flags: 11003
Addr : 0.0.0.0
Mask : 255.0.0.0
Bcast: NULL
Name : {41309F47-DA5B-4EDA-A59D-3E8462BAFE5B}
Flags: 11003
Addr : 0.0.0.0
Mask : 255.0.0.0
Bcast: NULL
Name : {AF453E9D-43D6-4BC0-8E7F-49301F590B70}
Flags: 11003
Addr : 192.168.0.102
Mask : 255.255.255.0
Bcast: NULL
Name : {72C1F9C4-DF75-46EF-8635-F5760B7E5000}
Flags: 11003
Addr : 169.254.2.2
Mask : 255.255.255.0
Bcast: NULL
Name : {9C2E8448-9C9A-48F2-A230-645A43C2DAD8}
Flags: 11041
Addr : fe80::348f:ddce:6dd8:ebe1
Mask : :::::
Bcast: NULL
Name : {9C2E8448-9C9A-48F2-A230-645A43C2DAD8}:1
Flags: 11043
Addr : 192.168.1.106
Mask : 255.255.255.0
Bcast: 192.168.1.255
Name : {B417521F-F617-462A-9E6A-599C0E6C88B4}
Flags: 11003
Addr : 192.168.1.101
Mask : 255.255.255.0
Bcast: NULL
Name : {E1997C5F-8B09-4D7C-9D94-A1673DD859A8}
Flags: 11041
Addr : fe80::5d03:e9c0:3c9:faaa
Mask : :::::
Bcast: NULL
Name : {E1997C5F-8B09-4D7C-9D94-A1673DD859A8}:1
Flags: 11043
Addr : 192.168.223.1
Mask : 255.255.255.0
Bcast: 192.168.223.255
Name : {2B1FA4AD-C7E5-4EC0-911B-05DDB952001E}
Flags: 11041
Addr : fe80::6167:7316:568a:d4bb
Mask : :::::
Bcast: NULL
Name : {2B1FA4AD-C7E5-4EC0-911B-05DDB952001E}:1
Flags: 11043
Addr : 192.168.32.1
Mask : 255.255.255.0
Bcast: 192.168.32.255
Name : {C328FED4-6A85-11DB-9FBD-806E6F6E6963}
Flags: 11049
Addr : ::1
Mask : :::::::
Bcast: NULL
Name : {C328FED4-6A85-11DB-9FBD-806E6F6E6963}:1
Flags: 11049
Addr : 127.0.0.1
Mask : 255.0.0.0
Bcast: 127.255.255.255
Name : {50C56876-75C8-4C5A-BE13-893910E544CC}
Flags: 11041
Addr : 2001:0:cf2e:3096:23:1262:3f57:fe95
Mask : :::::
Bcast: NULL
Name : {50C56876-75C8-4C5A-BE13-893910E544CC}
Flags: 11041
Addr : fe80::23:1262:3f57:fe95
Mask : :::::
Bcast: NULL
Name : {DA83C027-8281-440D-91F8-043EA42A7514}
Flags: 10001
Addr : fe80::5efe:c0a8:16a
Mask : :::::::
Bcast: NULL
Name : {4CCE0A40-1B0F-4309-828E-F97474CE69A6}
Flags: 10001
Addr : fe80::5efe:c0a8:df01
Mask : :::::::
Bcast: NULL
Name : {88EF0DCB-6011-465B-AA80-E77C50006365}
Flags: 10001
Addr : fe80::5efe:c0a8:2001
Mask : :::::::
Bcast: NULL
/Mårten
-Ursprungligt meddelande-
Från: Jon TURNEY [mailto:jon.tur...@dronecode.org.uk]
Skickat: den 7 september 2009 14:34
Till: cygwin-xfree@cygwin.com
Kopia: marten.gustafs...@holisticode.se
Ämne: Re: xdmcp cygwin 1.7 vista problem
On 07/09/2009 11:37, Mårten Gustafsson wrote:
When trying to connect to a linux sytem from a Vista using
xdmcp i get
a strange error.
2009-09-07 12:06:51 XDMCP fatal error: Session failed Session
173248003 failed for display 192.168.0.102:0: cannot open display
As you can see from my network config, I have no adapter on this
network address. I am using a wirless connection with ipadress
192.168.1.106. The same version of cygwin works flawlessly
from a wired XP box.
Hmm
You may find that using the -from command line parameter
(documented in 'man
Xserver') to force the local address used may help, but it's
still a bit mysterious where this address comes from...
Perhaps you could oblige me with the output from Corinna's
test program which dumps getaddrinfo output [1]
[1] http://cygwin.com/ml/cygwin-xfree/2009-07/msg2.html
−from local‐address
specifies the local address to connect from
(useful if the connecting host has multiple
network interfaces). The local‐address may
be expressed in any form acceptable to the
host platform’s gethostbyname(3) implementation.
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
__ Information frn ESET NOD32 Antivirus, version av
virussignaturdatabas 4401 (20090906) __
Meddelandet har kontrollerats av ESET NOD32 Antivirus.
http://www.esetscandinavia.com
--
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/
Fwd: SV: xdmcp cygwin 1.7 vista problem
I forgot to set the Reply-To: correctly Original Message Subject: SV: xdmcp cygwin 1.7 vista problem Date: Mon, 7 Sep 2009 15:41:52 +0200 From: Mårten Gustafsson To: 'Jon TURNEY' -from switch worked fine. Thanks /Mårten -Ursprungligt meddelande- Från: Jon TURNEY [mailto:jon.tur...@dronecode.org.uk] Skickat: den 7 september 2009 14:34 Till: cygwin-xfree@cygwin.com Kopia: marten.gustafs...@holisticode.se Ämne: Re: xdmcp cygwin 1.7 vista problem On 07/09/2009 11:37, Mårten Gustafsson wrote: When trying to connect to a linux sytem from a Vista using xdmcp i get a strange error. 2009-09-07 12:06:51 XDMCP fatal error: Session failed Session 173248003 failed for display 192.168.0.102:0: cannot open display As you can see from my network config, I have no adapter on this network address. I am using a wirless connection with ipadress 192.168.1.106. The same version of cygwin works flawlessly from a wired XP box. Hmm You may find that using the -from command line parameter (documented in 'man Xserver') to force the local address used may help, but it's still a bit mysterious where this address comes from... Perhaps you could oblige me with the output from Corinna's test program which dumps getaddrinfo output [1] [1] http://cygwin.com/ml/cygwin-xfree/2009-07/msg2.html −from local‐address specifies the local address to connect from (useful if the connecting host has multiple network interfaces). The local‐address may be expressed in any form acceptable to the host platform’s gethostbyname(3) implementation. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer __ Information frn ESET NOD32 Antivirus, version av virussignaturdatabas 4401 (20090906) __ Meddelandet har kontrollerats av ESET NOD32 Antivirus. http://www.esetscandinavia.com -- 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/
Dual Screen XDMCP Session
Hey Folks, I've been trying to use Xming with very little success for this task but apparently it can be done using cygwin too. Now this task could be impossible on both applications so I just wanted to check if anyone thought it was possible. On my computer at work I've got a dual head set up (two 1280x1024 screens side by side) and I've been blissfully using Linux on it for the last 2 years. Only now they've demanded all machines must run Vista so I've had to reinstall. I've installed Linux on a virtual machine on one of our ESXi servers (Vista makes the machine sluggish enough without running a virtual machine locally!). Now I can NX and XDMCP (using Xming thus far) into it just fine but that only gives me one fullscreen. I could VNC to it but theres not two 'virtual monitors' to poll, and VNC is slow even on a LAN anyway. So given NX, XDMCP, Cygwin/X, etc... are all miniature X servers that can tunnel over SSH... I was thinking maybe make a local xorg.conf on the Windows box and set up two screens with Xinerama or something like that. This is the closest I got with Xming... xming :0 -query 10.60.20.165 -clipboard -screen 0 @1 -screen 1 @2 This makes two seperate screens (like if Xinerama is turned off, and you get two GNOME panels)... and they arn't full screen either just maximized (can't seem to use the option -fullscreen when specifying two screens). I realise this isn't a Xming newsletter but I'm open to suggestions on how to achieve this with either Cygwin/X or Xming... Xming doesn't seem to have a forum, newsgroup, or indeed any kind of community. Any suggestions would be most definately appreciated! I need to cover up the fact I'm running Vista... it disgusts me! Thanks... Steven -- 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: Dual Screen XDMCP Session
On 06/08/2009 10:27, Steven Maddox wrote: Hey Folks, I've been trying to use Xming with very little success for this task but apparently it can be done using cygwin too. Now this task could be impossible on both applications so I just wanted to check if anyone thought it was possible. Cygwin/X and Xming share more or less the same codebase. On my computer at work I've got a dual head set up (two 1280x1024 screens side by side) and I've been blissfully using Linux on it for the last 2 years. Only now they've demanded all machines must run Vista so I've had to reinstall. I've installed Linux on a virtual machine on one of our ESXi servers (Vista makes the machine sluggish enough without running a virtual machine locally!). Now I can NX and XDMCP (using Xming thus far) into it just fine but that only gives me one fullscreen. I could VNC to it but theres not two 'virtual monitors' to poll, and VNC is slow even on a LAN anyway. So given NX, XDMCP, Cygwin/X, etc... are all miniature X servers that can tunnel over SSH... I was thinking maybe make a local xorg.conf on the Windows box and set up two screens with Xinerama or something like that. This is the closest I got with Xming... xming :0 -query 10.60.20.165 -clipboard -screen 0 @1 -screen 1 @2 This makes two seperate screens (like if Xinerama is turned off, and you get two GNOME panels)... and they arn't full screen either just maximized (can't seem to use the option -fullscreen when specifying two screens). Rather than naming all your screens, it sounds like you want to use the -multimonitors options, which gives you a single X screen which covers the entire Windows desktop Alternatively, if the applications you are running are Xinerama-aware, -screen 0 @1 -screen 1 @2 +xinerama may be better (although Xinerama mode has currently has a few restrictions, as noted in [2]) Add -nodecoration to remove the window borders As always, the man page [1] is your friend [1] http://x.cygwin.com/docs/man1/XWin.1.html [2] http://cygwin.com/ml/cygwin-xfree-announce/2009-02/msg7.html -- 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/
Solution to: -clipboard does not work when using XDMCP connection.
This e-mail is for documentation purposes, no further help is needed. With the default Cygwin/X install, the XWin.exe -clipboard option does not seem to work when connecting using the XDMCP protocol to a Linux server running GDM. The unix and Windows clipboards would not synchronized and copy/paste did not work across sessions. In /var/log/XWin.0.log, these messages were displayed: - winInitClipboard () winProcQueryTree - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 AUDIT: Fri Mar 6 13:23:07 2009: 4144 XWin: client 4 rejected from IP 127.0.0.1 winProcEstablishConnection - ProcEstablishConnection failed, bailing. winClipboardProc - Could not open display, try: 1, sleeping: 4 AUDIT: Fri Mar 6 13:23:11 2009: 4144 XWin: client 4 rejected from IP 127.0.0.1 winClipboardProc - Could not open display, try: 2, sleeping: 4 AUDIT: Fri Mar 6 13:23:15 2009: 4144 XWin: client 4 rejected from IP 127.0.0.1 winClipboardProc - Could not open display, try: 3, sleeping: 4 - My launch batch file for XWin.exe is fairly simple: @echo off start Title C:\cygwin\bin\XWin.exe -clipboard -query 192.168.0.1 I tried a number of solutions offered by others, but this one solved the problem. Create a text file in your Cygwin installation folder called: /etc/X0.hosts (that's X-zero dot hosts) It should contain one line: localhost Effectively, this permissions file allows the X server to access your Windows machine's local IP address (127.0.0.1). This file should probably be part of the standard Cygwin/X install. It also doesn't seem to be mentioned in the Cygwin/X documentation (maybe its there and I just missed it). Now the log file reports: - winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winProcEstablishConnection - Clipboard client already launched, returning. winClipboardProc - XOpenDisplay () returned and successfully opened the display. - and the clipboard now works properly. Copy and Paste between windows and X works as expected. For GDM users, you may also need to set an entry in your gdm config file located at: /etc/gdm/gdm.conf In the [daemon] section: [daemon] KillInitClients=false I haven't confirm the GDM requirement but this is how it's set up in my configuration. Hope this helps someone. Chris. -- 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/
cygwin and xdmcp extremly slow
Hi, I want to connect from my PC to a RHEL5 server. On my WinXP I installed the latest cygwin. On the server RHEL5 out of the box is installed, default window manager is KDE and xdmcp enabled. If I startxwin on my local machine, login to the server with ssh and export the DISPLAY to my PC everthing works fine. If I start xwin -query server the login windows appears and after login my KDE stats up. I can open a konsole, no problem up to now. But as soon as I press the first button on my keyboard the connection starts to react extremly slow. I takes about 10 seconds for keystrokes to appear. A tcpdump shows me that cygwin needs that time to send out the packets with the information. Is this problem a known bug? Where can I find out more to debug it? Thank you very much for any hint. Sincerely Yours, Michael Schwartzkopff -- 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: Xdmcp too slow with SOME Linux accounts.
Michael Giroux schrieb: Do the CygwinX developers watch this list? As far as i know xwin is unmaintained at the moment. -- 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: Xdmcp too slow with SOME Linux accounts.
I have retested this with connections to different Linux systems, and it (my xwin server hang) appears to be isolated to a single Linux. I find there is a difference in Fedora versions on the two systems. Although I'm surprosed that the version of Fedora would cause my local xwin.exe to stop reading the windows message queue, I will ask the system admin to look into this from a Linux config standpoint. -- 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: Xdmcp too slow with SOME Linux accounts.
Are there known issues with various versions of Fedora? -- 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: Xdmcp too slow with SOME Linux accounts.
Is there an alternative to XDCMP that I could try to see if that protocol is causing the problem? -- 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: Xdmcp too slow with SOME Linux accounts.
Michel, One alternative you could try is ssh-ing to the host you want to run the programs on and invoking the programs directly and comparing the graphics-update performance. In essence this means issuing the following command: ssh -Y [EMAIL PROTECTED] program The 'Y' parameter is very important, don't forget it. All this hinges on whether or not the host has SSH enabled, and if it does, it must also have X forwarding enabled. Still, it won't cost you that much to try. In the past, I have tried to use xdmcp like you have only to encounter the same sluggish performance you've reported, so I've opted to use X tunneling over SSH instead, which works great. The IS a drawback though, it doesn't give you the full desktop with the background and everything you might be looking for, but in practice the things you really want are the apps, anyway. J On Wed, 2007-09-12 at 06:56 -0700, Michael Giroux wrote: Is there an alternative to XDCMP that I could try to see if that protocol is causing the problem? -- 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/ -- 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: Xdmcp too slow with SOME Linux accounts.
Thanks for the tip. I was able to use the ssh, but that generated errors on the console (below). Before running the ssh command, I started xwin, but perhaps I need to specify some options? Michael (eclipse:29698): GLib-GObject-WARNING **: invalid (NULL) pointer instance (eclipse:29698): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_T YPE_CHECK_INSTANCE (instance)' failed (eclipse:29698): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS _SCREEN (screen)' failed (eclipse:29698): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (eclipse:29698): GLib-GObject-WARNING **: value TRUE of type `gboolean' is inv alid or out of range for property `visible' of type `gboolean' -- 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: Xdmcp too slow with SOME Linux accounts.
Michael, I am assuming you are invoking the ssh connection from a graphical xterm window, it won't work from a console-mode bash prompt. Other than that, it might mean that X forwarding is not enabled on the host you are connecting to. For the record, I just tried the scenario I outlined; ssh to a host and then invoking eclipse. It worked for me, so it has to be a configuration issue on your setup. J On Wed, 2007-09-12 at 07:45 -0700, Michael Giroux wrote: Thanks for the tip. I was able to use the ssh, but that generated errors on the console (below). Before running the ssh command, I started xwin, but perhaps I need to specify some options? Michael (eclipse:29698): GLib-GObject-WARNING **: invalid (NULL) pointer instance (eclipse:29698): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_T YPE_CHECK_INSTANCE (instance)' failed (eclipse:29698): Gtk-CRITICAL **: gtk_settings_get_for_screen: assertion `GDK_IS _SCREEN (screen)' failed (eclipse:29698): GLib-GObject-CRITICAL **: g_object_get: assertion `G_IS_OBJECT (object)' failed (eclipse:29698): GLib-GObject-WARNING **: value TRUE of type `gboolean' is inv alid or out of range for property `visible' of type `gboolean' -- 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/ -- 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: Xdmcp too slow with SOME Linux accounts.
Jean-Claude Gervais schrieb: The IS a drawback though, it doesn't give you the full desktop with the background and everything you might be looking for, but in practice the things you really want are the apps, anyway. That is not true, if you tunnel through ssh you can easily start kde, gnome or whatever window manager you like if you tell xwin not to start its own local window manager. (kde is startkde, gnome is gnome-session, icewm is icewm-session) -- 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: Xdmcp too slow with SOME Linux accounts.
Jean-Claude Gervais schrieb: Michael, I am assuming you are invoking the ssh connection from a graphical xterm window, it won't work from a console-mode bash prompt. It will if you set DISPLAY right before starting ssh. -- 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: Xdmcp too slow with SOME Linux accounts.
Have been watching this for a few days now and here is what we see. When I start an XWin session, response is excellent for about 1 minute. If I happen to close the XWin server in my cygwin desktop while the response is really good, I get a warning dialog that there are 4 clients connected. Repeat the test, start XWin, open Eclipse, use system until response degrades. Now close the XWin server while the response is poor. This time, I get a message box indicating that there are 17 clients connected. My network admin is seeing sessions connecting from the Linux box into my XWin server confirming that there are sessions being initiated on the Linux system. From this, it seems the response issue is somehow related to these clients. Since I'm only starting one client (Eclipse) the others I have no way of knowing what the others are. To test the theory that this is the cause of the problem, is there any way to prevent these clients from starting and connecting to my XWin server? Michael -- 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: Xdmcp too slow with SOME Linux accounts.
Michael Giroux schrieb: From this, it seems the response issue is somehow related to these clients. Since I'm only starting one client (Eclipse) the others I have no way of knowing what the others are. Yes you do. Make an addtional connection with ssh and make ps print all processes for your account. Or ask someone who is root to do so. To test the theory that this is the cause of the problem, is there any way to prevent these clients from starting and connecting to my XWin server? Yes. But these clients get started by the login process on the unix/linux computer so we would need to know exactly how you connect and start eclipse for further advice. -- 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: Xdmcp too slow with SOME Linux accounts.
Michael Giroux wrote on Tuesday, September 11, 2007 2:25 PM:: Since I'm only starting one client (Eclipse) the others I have no way of knowing what the others are. Try xlsclients -- 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: Xdmcp too slow with SOME Linux accounts.
I got a little help from my network admin. We started watching the traffic between my Windows desktop (XWin server) and the Linux box (client). What we see is interesting. When I start XWIN and then launch Eclipse, response is perfect. If I move the mouse, my system sends a message to the Linux box. When I see the performance problem, what I see is that if I move the mouse, nothing is sent from my system to Linux. The Linux box sends a keep-alive or something to my system every 15 seconds. When that happens, it appears that a mouse message is sent to Linux. To make matters a bit more interesting, the problem seems to occur shortly after I do something that effects the application windows on the XWin desktop. For example, if I start XWin, then start Eclipse, response remains good until I do almost anything to window. If I minimize Eclipse, I notice that shortly after that, my system stops sending messages to the Linux box when I move the mouse. Or, if I create a terminal window, then close it, the same happens, ... shortly later my system stops sending messages to the Linux box. Once this occurs, the only resolution is to abort XWin via the windows task manager (because it is not responding to mouse events) and restart it. All of this leads me to ask if maybe I have XWin installed incorrectly or maybe have the wrong version. Does any of this sound familiar to anyone who has used XWin for more than a few releases? On 9/11/07, Phil Betts [EMAIL PROTECTED] wrote: Michael Giroux wrote on Tuesday, September 11, 2007 2:25 PM:: Since I'm only starting one client (Eclipse) the others I have no way of knowing what the others are. Try xlsclients -- 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/ -- 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: Xdmcp too slow with SOME Linux accounts.
Thanks -swcursor has eliminated the console messages, and it manages to highlight the extremely slow response. It is taking several seconds for the mouse pointer to move when I move the physical mouse. In fact, I now realize that keyboard is non responsive as well. I'm not seeing any cpu utilization on either system, which gives me the feeling that there is a loop somewhere looking for events and the loop is using a timer or something. Using GUI on the physical Linux box does not have this problem, so I keep guessing that it has something to do with TCP/IP buffering or polling. Guess I'll have to ask a network admin to monitor this connection to confirm or discard that theory. Michael On 9/5/07, Holger Krull [EMAIL PROTECTED] wrote: winLoadCursor - Windows requires 32x32 cursor but X requires 39x26 That seems odd. I have never seen such a message. Does the working login get the same message? Maybe try to start with -swcursor -- 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: Xdmcp too slow with SOME Linux accounts.
Mario Scheble schrieb: Hello. Please, I need some help with the following problem. My PC has Windows XP and is part of a WorkGroup with a Debian Linux network. I installed Cygwin, and XDMCP properly works when I login on a remote machine to ONE Linux account. But when I login to ANOTHER account with the same privileges, the connection is very slow. What could it be wrong with the second account? Most likely this account is older and has some leftovers in its startup files. I had similar problems with a kde update (sound daemon related) Without knowing what is started when you login it is impossible to give further advice. Try a newly created account, if this has no problems, recreate the older ones. -- 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: Xdmcp too slow with SOME Linux accounts.
Michael Giroux schrieb: On 9/5/07, Holger Krull [EMAIL PROTECTED] wrote: Without knowing what is started when you login it is impossible to give further advice. Does stty have any effect? If yes, what options should be applied? Don't think so. As far as I can tell, my .bash_profile is not being executed when I login via xwin. Here is a PS to show what is running when I connect via telnet session. That is not relevant, the question is what is started: Gnome, KDE, WindowMaker or something similar. Here is the console output when I connect. Does this show anything? winLoadCursor - Windows requires 32x32 cursor but X requires 39x26 That seems odd. I have never seen such a message. Does the working login get the same message? Maybe try to start with -swcursor -- 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/
Xdmcp too slow with SOME Linux accounts.
Hello. Please, I need some help with the following problem. My PC has Windows XP and is part of a WorkGroup with a Debian Linux network. I installed Cygwin, and XDMCP properly works when I login on a remote machine to ONE Linux account. But when I login to ANOTHER account with the same privileges, the connection is very slow. What could it be wrong with the second account? I know nothing about Linux, and I'd appreciate your advice. Thank you very much. Sincerely yours, Mario Scheble -- 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: Xdmcp too slow with SOME Linux accounts.
I have a similar problem, but it is not limited to a specific account. In fact, it is fairly random. Sometimes I get pretty good performance, and then it just dies. In my case, it seems to get pretty bad when I launch Eclipse, but I have to admit that Eclipse is the only GUI app that I use, so it may be gui apps in general. What I see (reported in another message) is that mouse click and keyboard seem to be very responsive, but mouse move is non-responsive. If I open a menu and move the mouse, the menu items are not highlighted. If I move the mouse several more times over the menu, ultimately a menu item is highlighted. Once it is highlighted, I can click to select the item. From a pretty uninformed perspective, it appears that mouse move events are not being forwared from my server to the client, but I'm not sure how to determine that. I am pretty confident that the problem is limited to mouse move events, and that keyboard and mouse click events are being forwarded immediately. I've seen nothing on my other post. On 9/4/07, Mario Scheble [EMAIL PROTECTED] wrote: Hello. Please, I need some help with the following problem. My PC has Windows XP and is part of a WorkGroup with a Debian Linux network. I installed Cygwin, and XDMCP properly works when I login on a remote machine to ONE Linux account. But when I login to ANOTHER account with the same privileges, the connection is very slow. What could it be wrong with the second account? I know nothing about Linux, and I'd appreciate your advice. Thank you very much. Sincerely yours, Mario Scheble -- 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/ -- 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: XDMCP remote login freezes for Gnome desktop, but not XFCE.
Also Note: if I install packages tsclient and xnest in Ubuntu, I can successfully do a XDMCP login on the Ubuntu box to itself. In other words, I can have a gnome desktop within a gnome desktop just fine this way (which uses XDMCP). So maybe it is a Cygwin issue somehow after all... I'm not sure where the bug is: Cygwin? GDM? Some Gnome component? Maybe I need to install certain additional Cygwin packages related to X.org on the Windows box? Cheers, Dustin. On 4/29/07, Dustin Harriman [EMAIL PROTECTED] wrote: Hello, I have a Windows XP box where I've installed the latest version of Cygwin (as of two days ago). I want to have a remote Gnome desktop on an Ubuntu 6.10 box, where GDM has been configured to allow XDMCP logins. Using a Cygwin bash shell, I can log into an XFCE desktop just fine with the command X -query sila :1, (then I choose XFCE session at GDM). See attached screenshot cygwin_to_remote_xfce_no_problem.png. But If I choose Gnome session instead of XFCE, Gnome freezes as it starts up, showing only a grey rectangle in the upper left on a blue background. See attached screenshot cygwin_to_remote_gnome_has_problem.png Cygwin seems to be doing its job well, as the X server has not crashed. The problem seems to be in Ubuntu somewhere. I can't find any helpful error messages in /var/log/ however (on the Ubuntu machine). I've tail -f'ed syslog, messages, user.log, daemon.log. Has anyone one this mailing list seen this problem, and can you suggest a fix? I'll also be scouring Ubuntu's launchpad bug database and user forums, and perhaps file a bug there. My Blog: http://ca.blog.360.yahoo.com/dustinharriman RSS Feed: http://ca.blog.360.yahoo.com/rss-RkGSoVA1brWtXrVH9Gr5CzgVujwwGg--?cq=1 Freedom is not the capacity to do whatever we please; freedom is the capacity to make intelligent choices -Francis Moore Lappé -- 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: XDMCP remote login freezes for Gnome desktop, but not XFCE.
Dustin Harriman schrieb: Using a Cygwin bash shell, I can log into an XFCE desktop just fine with the command X -query sila :1, (then I choose XFCE session at GDM). See attached screenshot cygwin_to_remote_xfce_no_problem.png. Create a new user on the linux box (to make sure it is nothing in the profile) and try Xwin -query numeric.ip.address -from numeric.ip.address :1 -- 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.exe crashes when trying remote XDMCP login
Hi, I have a PC running Gentoo Linux which is accessed by many users who log into that computer using cygwin X and XDMCP. This has worked fine for a long time. One week ago I had to take the Gentoo Linux PC down (after 540 days uptime !) and used the oportunity to do some major upgrades, including X related stuff. After this upgrade I am unable to get up the remote login using cygwin/X work again. That is, I get the gdm login screen, I enter name and password but before the main GNOME desktop should come up XWin.exe crashes. Since I have done nothing with the PCs running cygwin/X I initially suspected something wrong with the Linux Gentoo PC. But every thing works OK if I log into the Linux PC both locally and from an other PC running Ubuntu Linux (using Xnest). Searching the net I have found a thread on Ubuntu forum where some very similar problems are reported. http://ubuntuforums.org/showthread.php?t=237132 Starting the xfs on the Gentoo Linux PC as suggested by doniv made no difference, so I still stuck. Next I have tried to strace XWin.exe to try to see why it is crashing. It sayes fatal error - called with threadlist_ix -1, seems I have managed to trig some error in XWin.exe. Listing of the last strace output is added. I have added the terminal ouput, the /var/log/messages output from the Gentoo Linux computer and the strace output. So I feel stuck. Anyone have any idea what I could try to isolate the problem ? LISTING START Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.99.901-4 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: XWin :0 -query gimli _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 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 32 bits per pixel winFinishScreenInitFB - Masks: 00ff ff00 00ff 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: 0414 (0414) (--) Using preset keyboard for Norwegian (414), type 4 Rules = xorg Model = pc105 Layout = no Variant = (null) Options = (null) The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Type ONE_LEVEL has 1 levels, but RALT has 2 symbols Ignoring extra symbols Errors from xkbcomp are not fatal to the X server (--) 3 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! winPointerWarpCursor - Discarding first warp: 637 481 winProcEstablishConnection - Hello winProcEstablishConnection - Clipboard is not enabled, returning. winProcQueryTree - Clipboard is not enabled, returning. Aborted (core dumped) LISTING STOP /var/log/messages output on the Gentoo Linux computer LISTING START Apr 19 11:28:08 gimli gdmgreeter[19458]: Got response: 'OK ' Apr 19 11:28:08 gimli gdmgreeter[19458]: Sending command: 'CLOSE' Apr 19 11:28:08 gimli gdm[3000]: Handling user message: 'CLOSE' Apr 19 11:28:09 gimli gdm[19449]: gdm_slave_wait_for_login: In loop Apr 19 11:28:16 gimli gdm[19449]: Sending QUERYLOGIN == secret for slave 19449 Apr 19 11:28:16 gimli gdm[3000]: Handling message: 'QUERYLOGIN 19449 hi' Apr 19 11:28:16 gimli gdm[3000]: Got QUERYLOGIN hi Apr 19 11:28:16 gimli gdm(pam_unix)[19449]: session opened for user hi by (uid=0) Apr 19 11:28:16 gimli gdm[19449]: gdm_slave_wait_for_login: end verify for 'hi' Apr 19 11:28:16 gimli gdm[19449]: gdm_slave_wait_for_login: got_login for 'hi' Apr 19 11:28:16 gimli gdm[19449]: Sending LOGGED_IN == 1 for slave 19449 Apr 19 11:28:16 gimli gdm[3000]: Handling message: 'LOGGED_IN 19449 1' Apr 19 11:28:16 gimli gdm[3000]: Got logged in == TRUE Apr 19 11:28:16 gimli gdm[19449]: Sending LOGIN == secret for slave 19449 Apr 19 11:28:16 gimli gdm[3000]: Handling message: 'LOGIN 19449 hi' Apr 19 11:28:16 gimli gdm[3000]: Got LOGIN == hi Apr 19 11:28:16 gimli gdm[19449]: gdm_slave_session_start: Attempting session for user 'hi' Apr 19 11:28:16 gimli gdm[19449]: Initial setting: session: 'gnome' language: '' Apr 19 11:28:16 gimli gdm[19449
XDMCP with cygwin kill kdesktop
Hi list, I use cygwin to open xdmcp session on my post windows XP. I connect myself on a RHEL3 server. I use commande line : $ XWin -query server -rootless -once Just after login, I open terminal to kill process kdesktop in order to delete the red hat wallpaper. The result is a windows desktop with windows task bar and red hat task bar. I recently try open SLES9-SP3 xdmcp session with same parameters. I kill kdesktop and obtain the same result like RHEL3. However, when I move a SLES9 windows, SLES9 wallpaper reappears on my windows' windows. Is there a better way to delete the Linux wallpaper that to to kill kdesktop ? Or do you know the difference between RHEL3 and SLES9-SP3 (XFree86 and Xorg) that entrains reappears of SLES9 wallpaper ? Thank you for help Cyril A -- 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: XDMCP with cygwin kill kdesktop
Cyril Aubert schrieb: Just after login, I open terminal to kill process kdesktop in order to delete the red hat wallpaper. A really weird method to change the background image. Is there a better way to delete the Linux wallpaper that to to kill kdesktop ? Yes. Use kcontrol / Appearance / Background -- 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: XDMCP with cygwin kill kdesktop
Why don't you just run kicker on the linux box (in a linux terminal and inactive X server on the windows machine)? Instead of the whole startx script which run many other programs (relatively slow). kicker is the task bar of kde. Sorry, I'm french, I don't explain my problem very well. I want to delete the linux desktop for just see the linux task bar on windows desktop. I join a window capture to be clear. Holger Krull a écrit : Cyril Aubert schrieb: Just after login, I open terminal to kill process kdesktop in order to delete the red hat wallpaper. A really weird method to change the background image. Is there a better way to delete the Linux wallpaper that to to kill kdesktop ? Yes. Use kcontrol / Appearance / Background -- 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/ -- Pavel Krustev Head of Management Systems Section, OM Division Globul mobile: (+359 89) 8400 842 phone: (+359 2 ) 9428 842 fax: (+359 2 ) 9428 802 e-mail: [EMAIL PROTECTED] -- 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: XDMCP with cygwin kill kdesktop
Thank you for reply. I find in last topic the way to display only kicker by running $ XWin -multiwindow -clipboard $ kdeinit +kicker But these launch kicker form cygwin platform, and I would like to access to my server application so to my server kicker. Can I write $HOME/.xinitrc in order to run only kicker ? Cyril A Pavel Krustev a écrit : Why don't you just run kicker on the linux box (in a linux terminal and inactive X server on the windows machine)? Instead of the whole startx script which run many other programs (relatively slow). kicker is the task bar of kde. Sorry, I'm french, I don't explain my problem very well. I want to delete the linux desktop for just see the linux task bar on windows desktop. I join a window capture to be clear. Holger Krull a écrit : Cyril Aubert schrieb: Just after login, I open terminal to kill process kdesktop in order to delete the red hat wallpaper. A really weird method to change the background image. Is there a better way to delete the Linux wallpaper that to to kill kdesktop ? Yes. Use kcontrol / Appearance / Background -- 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/ -- 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: XDMCP with cygwin kill kdesktop
Cyril Aubert schrieb: Thank you for reply. I find in last topic the way to display only kicker by running $ XWin -multiwindow -clipboard $ kdeinit +kicker But these launch kicker form cygwin platform, and I would like to access to my server application so to my server kicker. Well, you are starting kicker in cygwin, so no suprise here. If you want to start kicker on your linux computer you will have to use ssh or rsh. Remember to set DISPLAY if you are not using ssh tunnel. -- 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.exe freezes after login (XDMCP)
Hello, I installed a Cygwin that is able to connect through XDMCP to a linux Ubuntu server that runs KDE. I have several thin clients running Thinstation that work well with it, but on my personnal machine (Mac mini running Windows 2003 with disabled built-in firewall), when I run Xwin.exe, I can log on, see my desktop and apps opening, but after a few seconds, my Xwin window freezes and Windows tells me it's not responding. When I CTRL+C my Shell Cygwin application, the window closes. Here's my log : $ cat /tmp/Xwin.log (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information 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: 040C (040c) (--) Using preset keyboard for French (Standard) (40c), type 4 (--) 5 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from li st! winProcEstablishConnection - Hello winProcEstablishConnection - Clipboard is not enabled, returning. winProcQueryTree - Clipboard is not enabled, returning. I crawled the FAQ and the mailing list without results. Any ideas? Thx -- 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: XDMCP phenomenon
Hi Holger, thanks! That brought me onto the right track. I had checked for name resolution to work on the Cygwin box (nslookup in DOS window), so I never tried using the ip address directly; but in Windows' hosts file (which Cygwin symlinks) there was a wrong entry for my servers. Stupid mistake, sorry for disturbing, I should have found THAT on my own. Thanks for your help! Dirk --On 14. Dezember 2006 16:46:02 +0100 Holger Krull [EMAIL PROTECTED] wrote: Dirk H. Schulz schrieb: - using X -query HOSTNAME in all variants I know leads to a blank grey screen with no login of my servers, even if I substitute HOSTNAME with the one that always wins the race at X -broadcast. did you try X -query numeric.ip.address -from x.server.address ? -- 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/ -- Dirk H. Schulz IT Systems Service Wiesenweg 12, 85567 Grafing Tel. 0 80 92/86 25 68 Fax. 0 80 92/86 25 72 -- Intelligente Weblösungen: Weltweite Teamorganisation - Groupware im Browser -- 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: XDMCP pauses/delays
I found that reverting to the previous build (possible, though irritatingly difficult, using the setup tool) solves the problems. I had the same problem. I use XDMCP to connect to a Gnome server. Everything worked ok, but after less than 1 minute of using some applications, the system was becoming non-responsive, with abnormal delays of 1 or 2 seconds, just by moving the mouse in the menus. I've just reverted to the old package xorg-x11-win 6.8.2.0-4 as you suggested, and it fixed the problem ! Thank you for the solution. Vincent -- 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: XDMCP pauses/delays
Folks, https://bugs.freedesktop.org/show_bug.cgi?id=7911 Are there any updates on this bug? I'm getting hit by this now. I'm not sure why I'm just now seeing it (I've used Cygwin/X for years), but I have the problem on two different machines. If I just start XWin without XDMCP and just launch applications from a telnet session to remote host, I don't see the problem. I found that reverting to the previous build (possible, though irritatingly difficult, using the setup tool) solves the problems. I'm hoping that cygwin/xorg 7 might solve the problem whenever it appears. Ruth -- 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/
XDMCP and keepalive
Hi, we are currently facing a problem where an idle xdmcp session gets disconnect after a while. In Exceed there is an option to send keepalives to the server, so the connection doesn't close. I googled around but found nothing similar for cygwin. Is there really no option to enable a keepalive signal? -- View this message in context: http://www.nabble.com/XDMCP-and-keepalive-tf2558290.html#a7129187 Sent from the cygwin-xfree mailing list archive at Nabble.com. -- 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: W2k cygwin/x and XDMCP
Tajul Bashar wrote: Hi Ken, Sorry that I can not be of any use to your problem. I need some help instead. I was using CygwinX with Redhat 9 using XDMCP. But I can’t seem to get any screen from FC5 Workstation. I can see there are lot of changes in FC5 in terms of X configuration. But can’t seem to figure out what to do. Your reply will appreciated highly. Tajul Hi Tajul, Well the interesting thing is that after a couple of days the problem with W2K fixed itself. I have no idea why - nothing changed except it has been rebooted a couple of times! In FC5 the Fedora team have a X utility called gdmsetup which allows you to make the adjustments which you would otherwise need to do manually with vi. That should do what you need. Take care Ken -- 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/
W2k cygwin/x and XDMCP
Hi, I've been using cygwin/x for some time now on a W2K installation and on a WinXP laptop machine with XDMCP connected to various different FC3/4/5 hosts. A couple of days ago the W2K XDMCP sessions suddenly stopped working but the WinXP Laptop ones still work. The display shows the pattern that normally appears if the XDMCP server is off line. Both MS installations have MS's Automatic Updates enabled. I have re-installed cygwin on the W2K system with no improvement. Interestingly, ssh x-forwarded sessions still work fine on the W2K machine, its XDMCP that is failing. Netstat shows XWin.exe listening on port 6000 on the W2K box, which hasn't a firewall, and I can telnet to that port from the WinXP Laptop machine and that session connects. Port 177/udp is listening on the FC5 box I'm testing with. An Ethereal trace from the W2K box shows a port 177 exchange between the W2K and the FC5 box with the sequence - Query, Query, Willing, Request, Request, Accept, Accept, Manage, Manage, - then a brief pause - followed by Manage, Manage - then another pause - then Manage, Manage. All the manage packets have the same session ID in them. All this is on port 177/udp with no port 6000 traffic at all. I would have expected to see some port 6000 traffic from the FC5 box even if it was rejected/ignored by the W2K box. The ethereal log from theWinXP laptop shows - Query, Willing, Request, Accept, Manage on port 177 followed by a flurry of X11 packets on port 6000. Interestingly, no repeat packets like on the W2K box. I've noticed some other comments on the list, about XDMCP mysteriously stopping working, related to MS Updates. I have removed KB925486, despite its warnings about many things stopping working as a result, with no improvement, and put it back. The same hardware that runs the suspect W2K system also boots WinXP and FC5 (among others). Cygwin on the WinXP installation (also fully up to date with MS's patches) there also shows the same symptoms as the W2Ksystem, but the FC5 system on that hardware can connect to the remote FC5 XDMCP server just fine. Any ideas/help would be much appreciated. Thanks in advance Ken -- 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/
XDMCP pauses/delays
https://bugs.freedesktop.org/show_bug.cgi?id=7911 Are there any updates on this bug? I'm getting hit by this now. I'm not sure why I'm just now seeing it (I've used Cygwin/X for years), but I have the problem on two different machines. I've taken all of the usual steps of completely disabling and shutting down virus-scanning software, graphics card desktop tools, etc. to no avail. My symptoms are exactly as described in this bug - I can log into an XDMCP session and everything is fine until I press a key and then keyboard and mouse responsiveness becomes very choppy. If I just start XWin without XDMCP and just launch applications from a telnet session to remote host, I don't see the problem. -- 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/
XDMCP connection to (K)Ubuntu freezes
Hello. I have used Cygwin/X + XDMCP connection to Debian Linux computers in several Windows computers for several years, with no problems. However, I recently installed Kubuntu 6.0.6 to one computer and noticed that XDMCP connection freezes quite quickly. Symptoms are: - I get the login screen - I get the desktop - I can activate any program - after activating couple of windows, specially command shells, connection gets extremely slow and it eventually freezes - now when I try to close Cygwin/X, windows Task Manager just says program is not responding - the behaviour is exactly the same in two computers, both running Windows XP Pro SP2. If I just open X with startx, take ssh connection to Kubuntu computer and run anything from there (including command shells), there are no problems whatsoever. So this error seems to be isolated in XDMCP or handling of the desktop. To be honest, I have not tested the exactly same Cygwin/X setup to any Debian machine in the last few days, as I don't currently have an access to any Debian machine, which would run X. But, it was working fine still a couple of months ago. Here is a reference to Ubuntu web forum about same problem: http://www.ubuntuforums.org/showthread.php?t=237132 The cygcheck.out is attached. Any help is appreciated. If you need, I can activate some switches in Xwin to produce log files you need. Thanks, Kalle Tuulos cygcheck.out Description: Binary data -- 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/
XDMCP Problems
Hi all my first question to this forum so be gentle. I have two problems that seem to be related. I have a home LAN setup with two FC4 boxes. On the first FC4 box, I have setup XDMCP, and can connect to the XDMCP via Xnest on the second box. This works: Xnest :1 -query ip address This tells me that XDMCP seems to be working properly on the first FC4 machine. However, using cygwin/Xfree on an XP Pro notebook I cannot connect. I continue to get the 'Too many retransmissions' message. I've tried the following combinations of commands: Xwin -query ip address Xwin -query ip address -from local ip address I have disabled completely the firewall on the XP Pro laptop, and have no clue as to why it's not connecting. Curiously enough though, I can bring the same laptop into the office connect it to the lan and use Xwin -query ip address To start an XDMCP session to a Solaris 8 machine. The second question is related, it involves XDMCP from the same laptop to the same sun machine over a VPN. Whenever I initialize an openvpn connection to the office, I can ping, telnet, surf the local intranet, etc, etc. all over the vpn with no difficulty. However, when I try to connect to the Solaris 8 host via xdmcp, I get the Too many retransmissions error after a couple of minutes. I've tried every set of Xwin command combinations I can think of, with no success. Does anybody have any ideas ? -- 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/
XDMCP through a NAT firewall.
I need a fairly simple X server using XDMCP, that has one vital function, it can work from behind NAT! I would much prefer this to be a GPL based X server as well. I have a windows destop with the ipaddress 192.168.0.1 I also have an ADSL router with ipadress 192.168.0.254 on the local LAN and 216.239.59.147 on the internet. I want to connect to 72.14.205.19 with XDMCP. The command Xwin.exe -ac -from 216.239.59.147 -query 72.14.205.19 fails with an error message of Xserver: failed to bind to -from address: 216.239.59.147 My understanding of the problem. Although I can get the ADSL router to NAT 192.168.0.1 to 216.239.59.147 so the packet from 192.168.0.1 to 72.14.205.19 have the from address is 216.239.59.147. I understand the inital UDP 177 packet embeds the 192.168.0.1 address. This results in the remote server (72.14.205.19) sending the response to the windows desktop (192.168.0.1) which it cannot reach. I wish to be able to embed the router/firewall (216.239.59.147) ipaddress in the orginal conection from the windows desktop 192.168.0.1 so the remote server (72.14.205.19) replies to the router/firewall (216.239.59.147) How easy would it be to change the source code of Xwin.exe to do this? Thanks John P.S. x11 Tunnelling with ssh is not a option. The above ipaddress are complete fiction, and the connection is actually a private WAN link which reduces the security concerns. ___ The contents of this e-mail and any attachment(s) are strictly confidential and are solely for the person(s) at the e-mail address(es) above. If you are not an addressee, you may not disclose, distribute, copy or use this e-mail, and we request that you send an e-mail to [EMAIL PROTECTED] and delete this e-mail. Stirling Dynamics Ltd. accepts no legal liability for the contents of this e-mail including any errors, interception or interference, as internet communications are not secure. Any views or opinions presented are solely those of the author and do not necessarily represent those of Stirling Dynamics Ltd. ___ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk -- 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/
Unable to connect via XDMCP to VMWare/Fedora Core 5
Hi, I am running a Windows XP host with CygWin/X. On the same host I have a VMWare instance with Fedora Core 5. I'd like to connect to GDM via XDMCP. Things I did on the FC 5 guest: - Disabled iptables - Enabled remote login and debugging messages via gdmsetup On the windows host, I am entering XWin -query 192.168.1.129 where 192.168.1.129 is the guests IP address and .128 is the Windows hosts. In Ethereal, I can watch the following packet sequence: XDMCP Manage XDMCP Willing XDMCP Request XDMCP Manage XDMCP Manage XDMCP Manage XDMCP Manage but apparently nothing else. The gdm log can be found below. Any ideas, what might be wrong? Thanks, Jochen -- Whenever you find yourself on the side of the majority, it is time to pause and reflect. (Mark Twain) messages Description: Binary data -- 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 crash using XDMCP to Fedora Core 5 as root user
I've encountered a very strange crash since upgrading my linux box to FC5. If I connect from my WinXP box using the following command line: xwin -once -query 192.168.0.7 and login as root, then XWin crashes as Gnome starts up (just before displaying the actual desktop) but if I login as any other user, it works fine! Text dumped to bash console on crash is: winLoadCursor - Windows requires 32x32 cursor but X requires 39x26 winProcQueryTree - Clipboard is not enabled, returning. winLoadCursor - Windows requires 32x32 cursor but X requires 39x26 4 [sig] xwin 10540 C:\cygwin\usr\X11R6\bin\xwin.exe: *** fatal error - C:\ cygwin\usr\X11R6\bin\xwin.exe: *** called with threadlist_ix -1 Hangup Anyone else seen this? I have never seen this on any RedHat or Fedora version prior to this. Conor p.s. yeah, I know it's very naughty to have XDMCP for root enabled. -- 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/
Cygwin XDMCP suddenly stopped working
For some months now I've been using Cygwin/X on two different Windows XP computers to connect to an Ubuntu machine via XDMCP, and have had no problems. Now, seemingly out of the blue, the connection procedure has suddenly stopped working on one of the Windows computers. I say 'out of the blue' because I have not touched any cygwin files for months. The only things that I have done on the 'unsuccessful' computer between the time when it was working and not working is: a) Installed and promptly uninstalled JabberD 1.4.2. b) Installed ejabberd 0.7.5. (Disabling or uninstalling ejabberd had no effect.) c) Installed Gaim 2.0.0 beta 3 (no gtk). (Gaim 2.0 beta 2 was previously installed.) I have no idea how any of these actions would affect Cygwin, but then again I don't really know much, period, so I thought I'd mention them. Following is the Cygwin/X log file from the unsuccessful WinXP computer, split into two parts. The first appears in the log files of both the successful and unsuccessful WinXP computers -- in fact, it constitutes the entirety of the successful log file. The second part is the remainder of the unsuccessful log file, and appears only in that log. Does anyone have any clues about what might have gone wrong??? Thanks. --FIRST PART (common to both successful and unsuccessful log files)-- 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: /usr/X11R6/bin/XWin :0 -query 192.168.0.111 -nodecoration -lesspointer -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Cannot create /tmp/.X11-unix with root ownership (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/ 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: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 (--) 7 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! winProcEstablishConnection - Hello winProcEstablishConnection - Xdmcp enabled, waiting to start clipboard client until fourth call. winProcEstablishConnection - Hello winProcEstablishConnection - Xdmcp enabled, waiting to start clipboard client until fourth call. winProcEstablishConnection - Hello winProcEstablishConnection - Xdmcp enabled, waiting to start clipboard client until fourth call. winInitClipboard () winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winProcQueryTree - winInitClipboard returned. winClipboardProc - DISPLAY=127.0.0.1:0.0 winProcEstablishConnection - Hello winProcEstablishConnection - Clipboard client already launched, returning. winClipboardProc - XOpenDisplay () returned and successfully opened the display. --SECOND PART (remainder of unsuccessful log file)-- winProcSetSelectionOwner - Clipboard not yet started, aborting. winProcSetSelectionOwner - Clipboard not yet started, aborting. winClipboardIOErrorHandler! winClipboardProc - setjmp returned for IO Error Handler. winProcSetSelectionOwner - OpenClipboard () failed: 0578 winProcSetSelectionOwner - OpenClipboard () failed: 0578 winProcSetSelectionOwner - OpenClipboard () failed: 0578 winProcSetSelectionOwner - OpenClipboard () failed: 0578 winProcSetSelectionOwner - OpenClipboard () failed: 0578 (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/ 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: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap (--) 7 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing
xwin and clipboard using gdm with xdmcp
Hi, I use xwin.exe to connect my linux box via gdm and xdmcp. If i use xwin -multiwindow -clipboard i can pass the windows clipboard to the xwin window, but without the -multiwindow mode it get fails with something like: winProcEstablishConnection - ProcEstablishConnection failed, bailing. The xwin version is 6.8.99.901-4 How can i resolve this? Jorge Bastos -- 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/
XDMCP and Kerio Personal Firewall
Hello All, A while back I had some problems getting XDMCP working between Win XP and Ubuntu. The Ubuntu login screen loaded successfully, but upon logging in all I got was a blank brown screen. I've recently figured out that the problem all along was Kerio Personal Firewall, which was running at the Windows end. Apparently other users also have found that Kerio is somehow incompatible with XDMCP, even when an appropriate filter rule has been defined. I switched to another firewall (Jepico) and XDMCP now works beautifully with Cygwin/X. I just thought I'd report this in case other Kerio users have experienced the same problem and haven't suspected the firewall as the cause. Cheers. -- 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/
Strange keyboard behavior w/XDMCP and AIX
I start the XDMCP session and the keyboard works fine at the login screen. However, once the Motif window manager starts, the keyboard gets messed up. Typing s results in a on the screen. d gives s... and so on. Almost as if every key on the keyboard shifted by one. All mouse functions work as expected. The keyboard returns to normal after exiting MWM and returning to the login screen. Starting X with different keyboard maps does not affect problem. Suggestions/solutions on the Cygwin/X side (I have limited permissions on AIX system)? TIA. -- 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: connection to hostname:0.0 refused by server when running via XDMCP
Igor, Am Mittwoch, den 26.10.2005, 10:27 +0200 schrieb Reinhard Müller: $ su sabine xterm Xlib: connection to dhcp0.europe.localnet:0.0 refused by server Thanks for your hint. I tried to set xhost + localhost in the terminal before doing the su (didn't work), but I guess I have to do that on the Windows machine (the machine where the X server runs), so I wonder which is the correct place to add it. Thanks, Reinhard signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: connection to hostname:0.0 refused by server when running via XDMCP
On Fri, 28 Oct 2005, Reinhard Mueller wrote: Igor, Am Mittwoch, den 26.10.2005, 10:27 +0200 schrieb Reinhard Müller: $ su sabine xterm Xlib: connection to dhcp0.europe.localnet:0.0 refused by server Thanks for your hint. I tried to set xhost + localhost in the terminal before doing the su (didn't work), but I guess I have to do that on the Windows machine (the machine where the X server runs), so I wonder which is the correct place to add it. Sorry, I think I may have misunderstood what you were trying to do. Looks like you do su sabine on the *remote* machine -- I thought you tried this locally. By default, X (in XDMCP mode) limits the connections to the user logged in via XDMCP from the target machine. If you want other users to connect (whether those from the X server machine, or those from the XDMCP target machine), you'll need to add them to the access list with the xhost command. You may need to specify the host to add in the form that xhost understands (i.e., the full machine name instead of localhost). See the xhost manpage for details. The xhost command needs to be invoked by the user who has control over the X server (e.g., from the remote xterm). HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. /DA -- 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: connection to hostname:0.0 refused by server when running via XDMCP
Thanks again Igor, it worked like you described. I didn't expect to be able to enter the xhost command on the remote machine, I thought I had to enter it on the machine running the X server. However, I added xhost remote-machine to my ~/.gnomerc and it works perfectly. Thanks, Reinhard signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
connection to hostname:0.0 refused by server when running via XDMCP
Hello, all, I use cygwin/x to make my Windows PC a X Windows terminal: I connect to my GNU/Linux machine via XDMCP. Everything works fine as long as I don't want to change the user. However, when I try to execute a program as a different user, I get the following error message: $ su sabine xterm Xlib: connection to dhcp0.europe.localnet:0.0 refused by server Xlib: No protocol specified xterm Xt error: Can't open display: dhcp0.europe.localnet:0.0 (dhcp0.europe.localnet is the name of the Windows PC where cygwin/x runs) Any hint about how to fix this is highly appreciated. Thanks, Reinhard signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
