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: problem with startxwin.exe and a possible solution
Marco Atzeri wrote: Today I start some experiments and I have found that changing the menu target from C:\cygwin2\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe to C:\cygwin2\bin\run.exe -p /usr/bin /usr/bin/startxwin.exe all the problems seem gone. The Xserver is stable and all the Xterms run smoothly. I suppose that my login shell redefine some parameters that startxwin.exe needs, while a much simpler run.exe -p /usr/bin is what is really needed. The real issue, I think, is that your mechanism doesn't allow you to set OTHER environment variables that might need to be defined before launching XWin, such as LC_ALL etc -- which would get set by the original formula, since 'bash -l' reads your startup files like ~/.bash_profile where they might get set. Another (untested!) possibility is to use run2.exe (which is kinda wierd: use a launcher to start a launcher that starts X...) == startxwin.xml === ?xml version=1.0 encoding=us-ascii? Run2Config xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:noNamespaceSchemaLocation=run2.xsd Global Environment !-- set environment variables here -- Append var=PATH value=/usr/bin/ Set var=LC_ALL value=en_US.UTF-8/ /Environment Target filename=/usr/bin/startxwin.exe startin=~ /Target /Global /Run2Config Shortcut target: C:/cygwin/bin/run2.exe --notty /usr/bin/startxwin.xml -- Chuck -- 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/
