From aliasghar.toraby@gmail.com Wed Jan 2 06:07:00 2008 From: aliasghar.toraby@gmail.com (Ali asghar Toraby) Date: Wed, 02 Jan 2008 06:07:00 -0000 Subject: [Fwd: xwin crashed when using "-depth 24 bpp" option] Message-ID: <477B29E9.6090007@gmail.com> -------------- next part -------------- An embedded message was scrubbed... From: Ali asghar Toraby Subject: xwin crashed when using "-depth 24 bpp" option Date: Mon, 31 Dec 2007 14:51:11 +0330 Size: 2145 URL: -------------- next part -------------- -- 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/ From aliasghar.toraby@gmail.com Wed Jan 2 06:12:00 2008 From: aliasghar.toraby@gmail.com (Ali asghar Toraby) Date: Wed, 02 Jan 2008 06:12:00 -0000 Subject: Xwin crashed when i use "-depth 24" Message-ID: <477B2B30.7060609@gmail.com> hi friends i use xwin to remote solaris8 CDE environment. when i use 24 bpp option it crashed and following is the output that it prompt to me: ############################################################## $ xwin -query 192.168.1.50 -fullscreen -engine 2 -depth 24 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 -query 192.168.1.50 -fullscreen -engine 2 -depth 24 _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 00000007 winSetEngine - Using user's preference: 2 winAdjustVideoModeShadowDD - FullScreen, using command line bpp: 24 winAllocateFBShadowDD - Changing video mode winAllocateFBShadowDD - Could not set full screen display mode: 80004001 winFinishScreenInitFB - Could not allocate framebuffer winScreenInit - winFinishScreenInit () failed Fatal server error: InitOutput - Couldn't add screen 0 Segmentation fault (core dumped) ############################################################## how to i can fix this problem? i want to use 24 bpp to have a right colors in CDE session. in other modes (8,16,32) colors not properly. in Xconnect-pro when i use 24 bpp it worked successfully but in cygwin/x it crashed and core dumped!! WHY?? :( please help me. thanks for any reply -- 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/ From support@ballouchi.com Wed Jan 2 08:09:00 2008 From: support@ballouchi.com (Ballouchi.com) Date: Wed, 02 Jan 2008 08:09:00 -0000 Subject: Meilleurs voeux! Message-ID: <200801020808.m02888KT026352@smtp.hexabyte.tn> Ballouchi.com vous souhaite une heureuse ann??e 2008 pleine de sant?? et de proposp??rit??. Ballouchi.com vous communique les statistiques du traffic r??alis?? en 2007. * Nombre de pages vues: 13 884 805 pages. * Nombre de visites uniques: 3 105 521 visites Tous nos meilleurs voeux. ------------------------------------ L'??quipe de http://www.Ballouchi.com Le portail des tunisiens. Assistance sur msn: support@ballouchi.com Hotline: +216 98 349 553 -- 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/ From cygwinx@bzzt.net Wed Jan 2 16:12:00 2008 From: cygwinx@bzzt.net (Arnout Engelen) Date: Wed, 02 Jan 2008 16:12:00 -0000 Subject: xterm(229-1) does not accept "-u8" Message-ID: <20080102160719.GB27723@bzzt.net> Hi, I read at http://cygwin.com/ml/cygwin-xfree/2007-08/threads.html#00068 that support for the -u8 option was dropped from newer versions of xterm for cygwin. I'd like to vote for keeping this option, it's quite useful to me, as it allows me to read my mail in mutt over ssh without the screen getting mangled :). Arnout -- 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/ From Phil.Betts@ascribe.com Thu Jan 3 12:08:00 2008 From: Phil.Betts@ascribe.com (Phil Betts) Date: Thu, 03 Jan 2008 12:08:00 -0000 Subject: Use remote graphical program In-Reply-To: <47730255.1080807@cygwin.com> Message-ID: <2D9E96311DCA4C48BF185EA6928BC7BB02FC860E@asc-mail.int.ascribe.com> Larry Hall (Cygwin X) wrote on Thursday, December 27, 2007 1:40 AM:: > horacioemilio wrote: >> Hi, >> >> I am trying to use a remote program which is installed on a remote >> linux machine. In these situations I usually do; >> >> 0) on my windows machine I start cygwin and afterwards use >> startxwin.sh >> >> 1) ssh -X name-of-the-gateway-machine >> >> 2) ssh -X name-of-the-linux-machine-inside-the-remote-network >> >> 3) program-name & >> >> and programs like emacs or firefox appear on my desktop. >> >> But for some other program which uses more advanced graphics it does >> not work, I get the following error message; >> >> user@machine:~> Xlib: extension "GLX" missing on display >> "localhost:10.0" . Xlib: extension "GLX" missing on display >> "localhost:10.0". > > > >> >> Do you know how could I overcome this situation ? > > This is more appropriately directed to the Cygwin X list. I've reset > the "Reply-To" there. Please send any follow-up the the Cygwin X > list. > > From the above, it's clear the application you're trying to use wants > to access the underlying hardware (via OpenGL). This is not supported > in the current Cygwin X server. I believe there is a MinGW version > which has some support for this though. You may want to investigate > that. > > -- > Larry Hall http://www.rfk.com > RFK Partners, Inc. (508) 893-9779 - RFK Office > 216 Dalton Rd. (508) 429-6305 - FAX > Holliston, MA 01746 There is an experimental, but (in my experience) very stable, version of XWin with GLX support. This is in package xorg-x11-xwin-gl and installs the executable XWin_GL.exe. You would need to alter your startxwin.sh to run this instead of XWin.exe. It works, just don't expect great performance. Phil -- 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/ From Phil.Betts@ascribe.com Thu Jan 3 12:22:00 2008 From: Phil.Betts@ascribe.com (Phil Betts) Date: Thu, 03 Jan 2008 12:22:00 -0000 Subject: Xwin crashed when i use "-depth 24" In-Reply-To: <477B2B30.7060609@gmail.com> Message-ID: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> Ali asghar Toraby wrote on Wednesday, January 02, 2008 6:12 AM:: > hi friends Asking the same question 3 times in quick succession without waiting for a response will not make you any friends here. > i use xwin to remote solaris8 CDE environment. when i use > 24 bpp option it crashed and following is the output that it prompt > to me: ############################################################## [snip] > winAllocateFBShadowDD - Changing video mode > winAllocateFBShadowDD - Could not set full screen display mode: > 80004001 winFinishScreenInitFB - Could not allocate framebuffer > winScreenInit - winFinishScreenInit () failed [snip] > how to i can fix this problem? The -depth parameter must match what your hardware is capable of displaying. It is usually safest to omit the depth option and let XWin use the current Windows mode. > i want to use 24 bpp to have a right > colors in CDE session. in other modes (8,16,32) colors not properly. > in Xconnect-pro when i use 24 bpp it worked successfully but in > cygwin/x it crashed and core dumped!! WHY?? :( > please help me. thanks for any reply If your Windows display is set to 32bpp, and XWin is started without the depth option, but CDE does not display the correct colours, I can only assume that CDE (or the Solaris X11 library) is making invalid assumptions about the pixel format. If so, then you should address your question to Sun. There is no problem when running X software from other vendors. Phil -- 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/ From aliasghar.toraby@gmail.com Thu Jan 3 12:58:00 2008 From: aliasghar.toraby@gmail.com (Ali Asghar Toraby) Date: Thu, 03 Jan 2008 12:58:00 -0000 Subject: Xwin crashed when i use "-depth 24" In-Reply-To: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> References: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> Message-ID: <477CDAE0.70501@gmail.com> hi thanks for your reply and excuse me for repeating the question i thought that they not delivered successfully so i resend them. but i think cygwin.cause that wrong colors appeared in screen. i use several demos of comerical packages like xconnect-pro and xWin32 and they are working properly. they can taste the settings of CDE. when i use auto detection option in xconnect-pro it run in 26 bpp automatically but in cygwin it runs in 32 by default. i tried to use -depth 26 but it crashed and stopped. you say that hardware must capable to perform 26 bpp. but both target and host computers really work by another tools. :-\ please suggest me a solution. thanks for your attention Phil Betts wrote: > Ali asghar Toraby wrote on Wednesday, January 02, 2008 6:12 AM:: > > >> hi friends >> > > Asking the same question 3 times in quick succession without waiting > for a response will not make you any friends here. > > >> i use xwin to remote solaris8 CDE environment. when i use >> 24 bpp option it crashed and following is the output that it prompt >> to me: ############################################################## >> > > [snip] > > >> winAllocateFBShadowDD - Changing video mode >> winAllocateFBShadowDD - Could not set full screen display mode: >> 80004001 winFinishScreenInitFB - Could not allocate framebuffer >> winScreenInit - winFinishScreenInit () failed >> > > [snip] > > >> how to i can fix this problem? >> > > The -depth parameter must match what your hardware is capable of > displaying. It is usually safest to omit the depth option and let > XWin use the current Windows mode. > > >> i want to use 24 bpp to have a right >> colors in CDE session. in other modes (8,16,32) colors not properly. >> in Xconnect-pro when i use 24 bpp it worked successfully but in >> cygwin/x it crashed and core dumped!! WHY?? :( >> please help me. thanks for any reply >> > > If your Windows display is set to 32bpp, and XWin is started without > the depth option, but CDE does not display the correct colours, I can > only assume that CDE (or the Solaris X11 library) is making invalid > assumptions about the pixel format. If so, then you should address > your question to Sun. There is no problem when running X software > from other vendors. > > Phil > > -- > 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/ From aliasghar.toraby@gmail.com Thu Jan 3 15:20:00 2008 From: aliasghar.toraby@gmail.com (Ali Asghar Toraby) Date: Thu, 03 Jan 2008 15:20:00 -0000 Subject: Xwin crashed when i use "-depth 24" In-Reply-To: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> References: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> Message-ID: <477CDAE0.70501@gmail.com> hi thanks for your reply and excuse me for repeating the question i thought that they not delivered successfully so i resend them. but i think cygwin.cause that wrong colors appeared in screen. i use several demos of comerical packages like xconnect-pro and xWin32 and they are working properly. they can taste the settings of CDE. when i use auto detection option in xconnect-pro it run in 26 bpp automatically but in cygwin it runs in 32 by default. i tried to use -depth 26 but it crashed and stopped. you say that hardware must capable to perform 26 bpp. but both target and host computers really work by another tools. :-\ please suggest me a solution. thanks for your attention Phil Betts wrote: > Ali asghar Toraby wrote on Wednesday, January 02, 2008 6:12 AM:: > > >> hi friends >> > > Asking the same question 3 times in quick succession without waiting > for a response will not make you any friends here. > > >> i use xwin to remote solaris8 CDE environment. when i use >> 24 bpp option it crashed and following is the output that it prompt >> to me: ############################################################## >> > > [snip] > > >> winAllocateFBShadowDD - Changing video mode >> winAllocateFBShadowDD - Could not set full screen display mode: >> 80004001 winFinishScreenInitFB - Could not allocate framebuffer >> winScreenInit - winFinishScreenInit () failed >> > > [snip] > > >> how to i can fix this problem? >> > > The -depth parameter must match what your hardware is capable of > displaying. It is usually safest to omit the depth option and let > XWin use the current Windows mode. > > >> i want to use 24 bpp to have a right >> colors in CDE session. in other modes (8,16,32) colors not properly. >> in Xconnect-pro when i use 24 bpp it worked successfully but in >> cygwin/x it crashed and core dumped!! WHY?? :( >> please help me. thanks for any reply >> > > If your Windows display is set to 32bpp, and XWin is started without > the depth option, but CDE does not display the correct colours, I can > only assume that CDE (or the Solaris X11 library) is making invalid > assumptions about the pixel format. If so, then you should address > your question to Sun. There is no problem when running X software > from other vendors. > > Phil > > -- > 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/ From aliasghar.toraby@gmail.com Thu Jan 3 16:22:00 2008 From: aliasghar.toraby@gmail.com (Ali Asghar Toraby) Date: Thu, 03 Jan 2008 16:22:00 -0000 Subject: Xwin crashed when i use "-depth 24" In-Reply-To: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> References: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> Message-ID: <477CDAE0.70501@gmail.com> hi thanks for your reply and excuse me for repeating the question i thought that they not delivered successfully so i resend them. but i think cygwin.cause that wrong colors appeared in screen. i use several demos of comerical packages like xconnect-pro and xWin32 and they are working properly. they can taste the settings of CDE. when i use auto detection option in xconnect-pro it run in 26 bpp automatically but in cygwin it runs in 32 by default. i tried to use -depth 26 but it crashed and stopped. you say that hardware must capable to perform 26 bpp. but both target and host computers really work by another tools. :-\ please suggest me a solution. thanks for your attention Phil Betts wrote: > Ali asghar Toraby wrote on Wednesday, January 02, 2008 6:12 AM:: > > >> hi friends >> > > Asking the same question 3 times in quick succession without waiting > for a response will not make you any friends here. > > >> i use xwin to remote solaris8 CDE environment. when i use >> 24 bpp option it crashed and following is the output that it prompt >> to me: ############################################################## >> > > [snip] > > >> winAllocateFBShadowDD - Changing video mode >> winAllocateFBShadowDD - Could not set full screen display mode: >> 80004001 winFinishScreenInitFB - Could not allocate framebuffer >> winScreenInit - winFinishScreenInit () failed >> > > [snip] > > >> how to i can fix this problem? >> > > The -depth parameter must match what your hardware is capable of > displaying. It is usually safest to omit the depth option and let > XWin use the current Windows mode. > > >> i want to use 24 bpp to have a right >> colors in CDE session. in other modes (8,16,32) colors not properly. >> in Xconnect-pro when i use 24 bpp it worked successfully but in >> cygwin/x it crashed and core dumped!! WHY?? :( >> please help me. thanks for any reply >> > > If your Windows display is set to 32bpp, and XWin is started without > the depth option, but CDE does not display the correct colours, I can > only assume that CDE (or the Solaris X11 library) is making invalid > assumptions about the pixel format. If so, then you should address > your question to Sun. There is no problem when running X software > from other vendors. > > Phil > > -- > 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/ From aliasghar.toraby@gmail.com Thu Jan 3 17:05:00 2008 From: aliasghar.toraby@gmail.com (Ali Asghar Toraby) Date: Thu, 03 Jan 2008 17:05:00 -0000 Subject: Xwin crashed when i use "-depth 24" In-Reply-To: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> References: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> Message-ID: <477CDAE0.70501@gmail.com> hi thanks for your reply and excuse me for repeating the question i thought that they not delivered successfully so i resend them. but i think cygwin.cause that wrong colors appeared in screen. i use several demos of comerical packages like xconnect-pro and xWin32 and they are working properly. they can taste the settings of CDE. when i use auto detection option in xconnect-pro it run in 26 bpp automatically but in cygwin it runs in 32 by default. i tried to use -depth 26 but it crashed and stopped. you say that hardware must capable to perform 26 bpp. but both target and host computers really work by another tools. :-\ please suggest me a solution. thanks for your attention Phil Betts wrote: > Ali asghar Toraby wrote on Wednesday, January 02, 2008 6:12 AM:: > > >> hi friends >> > > Asking the same question 3 times in quick succession without waiting > for a response will not make you any friends here. > > >> i use xwin to remote solaris8 CDE environment. when i use >> 24 bpp option it crashed and following is the output that it prompt >> to me: ############################################################## >> > > [snip] > > >> winAllocateFBShadowDD - Changing video mode >> winAllocateFBShadowDD - Could not set full screen display mode: >> 80004001 winFinishScreenInitFB - Could not allocate framebuffer >> winScreenInit - winFinishScreenInit () failed >> > > [snip] > > >> how to i can fix this problem? >> > > The -depth parameter must match what your hardware is capable of > displaying. It is usually safest to omit the depth option and let > XWin use the current Windows mode. > > >> i want to use 24 bpp to have a right >> colors in CDE session. in other modes (8,16,32) colors not properly. >> in Xconnect-pro when i use 24 bpp it worked successfully but in >> cygwin/x it crashed and core dumped!! WHY?? :( >> please help me. thanks for any reply >> > > If your Windows display is set to 32bpp, and XWin is started without > the depth option, but CDE does not display the correct colours, I can > only assume that CDE (or the Solaris X11 library) is making invalid > assumptions about the pixel format. If so, then you should address > your question to Sun. There is no problem when running X software > from other vendors. > > Phil > > -- > 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/ From aliasghar.toraby@gmail.com Thu Jan 3 17:38:00 2008 From: aliasghar.toraby@gmail.com (Ali Asghar Toraby) Date: Thu, 03 Jan 2008 17:38:00 -0000 Subject: Xwin crashed when i use "-depth 24" In-Reply-To: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> References: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> Message-ID: <477CDAE0.70501@gmail.com> hi thanks for your reply and excuse me for repeating the question i thought that they not delivered successfully so i resend them. but i think cygwin.cause that wrong colors appeared in screen. i use several demos of comerical packages like xconnect-pro and xWin32 and they are working properly. they can taste the settings of CDE. when i use auto detection option in xconnect-pro it run in 26 bpp automatically but in cygwin it runs in 32 by default. i tried to use -depth 26 but it crashed and stopped. you say that hardware must capable to perform 26 bpp. but both target and host computers really work by another tools. :-\ please suggest me a solution. thanks for your attention Phil Betts wrote: > Ali asghar Toraby wrote on Wednesday, January 02, 2008 6:12 AM:: > > >> hi friends >> > > Asking the same question 3 times in quick succession without waiting > for a response will not make you any friends here. > > >> i use xwin to remote solaris8 CDE environment. when i use >> 24 bpp option it crashed and following is the output that it prompt >> to me: ############################################################## >> > > [snip] > > >> winAllocateFBShadowDD - Changing video mode >> winAllocateFBShadowDD - Could not set full screen display mode: >> 80004001 winFinishScreenInitFB - Could not allocate framebuffer >> winScreenInit - winFinishScreenInit () failed >> > > [snip] > > >> how to i can fix this problem? >> > > The -depth parameter must match what your hardware is capable of > displaying. It is usually safest to omit the depth option and let > XWin use the current Windows mode. > > >> i want to use 24 bpp to have a right >> colors in CDE session. in other modes (8,16,32) colors not properly. >> in Xconnect-pro when i use 24 bpp it worked successfully but in >> cygwin/x it crashed and core dumped!! WHY?? :( >> please help me. thanks for any reply >> > > If your Windows display is set to 32bpp, and XWin is started without > the depth option, but CDE does not display the correct colours, I can > only assume that CDE (or the Solaris X11 library) is making invalid > assumptions about the pixel format. If so, then you should address > your question to Sun. There is no problem when running X software > from other vendors. > > Phil > > -- > 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/ From gustavo.seabra@gmail.com Fri Jan 4 16:19:00 2008 From: gustavo.seabra@gmail.com (Gustavo Seabra) Date: Fri, 04 Jan 2008 16:19:00 -0000 Subject: Use remote graphical program In-Reply-To: <2D9E96311DCA4C48BF185EA6928BC7BB02FC860E@asc-mail.int.ascribe.com> References: <47730255.1080807@cygwin.com> <2D9E96311DCA4C48BF185EA6928BC7BB02FC860E@asc-mail.int.ascribe.com> Message-ID: On Jan 3, 2008 7:08 AM, Phil Betts wrote: > Larry Hall (Cygwin X) wrote on Thursday, December 27, 2007 1:40 AM:: > > > horacioemilio wrote: > >> Hi, > >> > >> I am trying to use a remote program which is installed on a remote > >> linux machine. In these situations I usually do; > >> > >> 0) on my windows machine I start cygwin and afterwards use > >> startxwin.sh > >> > >> 1) ssh -X name-of-the-gateway-machine > >> > >> 2) ssh -X name-of-the-linux-machine-inside-the-remote-network > >> > >> 3) program-name & > >> > >> and programs like emacs or firefox appear on my desktop. > >> > >> But for some other program which uses more advanced graphics it does > >> not work, I get the following error message; > >> > >> user@machine:~> Xlib: extension "GLX" missing on display > >> "localhost:10.0" . Xlib: extension "GLX" missing on display > >> "localhost:10.0". > > > > > > > >> > >> Do you know how could I overcome this situation ? > > > > This is more appropriately directed to the Cygwin X list. I've reset > > the "Reply-To" there. Please send any follow-up the the Cygwin X > > list. > > > > From the above, it's clear the application you're trying to use wants > > to access the underlying hardware (via OpenGL). This is not supported > > in the current Cygwin X server. I believe there is a MinGW version > > which has some support for this though. You may want to investigate > > that. > > > > -- > > Larry Hall http://www.rfk.com > > RFK Partners, Inc. (508) 893-9779 - RFK Office > > 216 Dalton Rd. (508) 429-6305 - FAX > > Holliston, MA 01746 > > There is an experimental, but (in my experience) very stable, version > of XWin with GLX support. This is in package xorg-x11-xwin-gl and > installs the executable XWin_GL.exe. You would need to alter your > startxwin.sh to run this instead of XWin.exe. It works, just don't > expect great performance. > > Phil That's interesting... Last time I checked, there was no maintainer for X in Cygwin, but I do admit that was some time ago. So, I'm very curious to learn about this newer XWin version. If you don't mind, I'd like to ask a couple of questions: 1. Is this package available through setup.exe? Or do we need to recompile it for Cygwin ourselves? 2. What do you mean by "don't expect great performance."? Is it a GLX issue or something related to this particular version of XWin, as compared to the older ones? Thanks a lot! Gustavo. -- 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/ From aliasghar.toraby@gmail.com Sat Jan 5 01:04:00 2008 From: aliasghar.toraby@gmail.com (Ali Asghar Toraby) Date: Sat, 05 Jan 2008 01:04:00 -0000 Subject: Xwin crashed when i use "-depth 24" In-Reply-To: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> References: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> Message-ID: <477CDAE0.70501@gmail.com> hi thanks for your reply and excuse me for repeating the question i thought that they not delivered successfully so i resend them. but i think cygwin.cause that wrong colors appeared in screen. i use several demos of comerical packages like xconnect-pro and xWin32 and they are working properly. they can taste the settings of CDE. when i use auto detection option in xconnect-pro it run in 26 bpp automatically but in cygwin it runs in 32 by default. i tried to use -depth 26 but it crashed and stopped. you say that hardware must capable to perform 26 bpp. but both target and host computers really work by another tools. :-\ please suggest me a solution. thanks for your attention Phil Betts wrote: > Ali asghar Toraby wrote on Wednesday, January 02, 2008 6:12 AM:: > > >> hi friends >> > > Asking the same question 3 times in quick succession without waiting > for a response will not make you any friends here. > > >> i use xwin to remote solaris8 CDE environment. when i use >> 24 bpp option it crashed and following is the output that it prompt >> to me: ############################################################## >> > > [snip] > > >> winAllocateFBShadowDD - Changing video mode >> winAllocateFBShadowDD - Could not set full screen display mode: >> 80004001 winFinishScreenInitFB - Could not allocate framebuffer >> winScreenInit - winFinishScreenInit () failed >> > > [snip] > > >> how to i can fix this problem? >> > > The -depth parameter must match what your hardware is capable of > displaying. It is usually safest to omit the depth option and let > XWin use the current Windows mode. > > >> i want to use 24 bpp to have a right >> colors in CDE session. in other modes (8,16,32) colors not properly. >> in Xconnect-pro when i use 24 bpp it worked successfully but in >> cygwin/x it crashed and core dumped!! WHY?? :( >> please help me. thanks for any reply >> > > If your Windows display is set to 32bpp, and XWin is started without > the depth option, but CDE does not display the correct colours, I can > only assume that CDE (or the Solaris X11 library) is making invalid > assumptions about the pixel format. If so, then you should address > your question to Sun. There is no problem when running X software > from other vendors. > > Phil > > -- > 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/ From cgf-use-the-mailinglist-please@cygwin.com Sat Jan 5 19:53:00 2008 From: cgf-use-the-mailinglist-please@cygwin.com (Christopher Faylor) Date: Sat, 05 Jan 2008 19:53:00 -0000 Subject: Xwin crashed when i use "-depth 24" In-Reply-To: <477CDAE0.70501@gmail.com> References: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> <477CDAE0.70501@gmail.com> Message-ID: <20080103161606.GB27604@ednor.casa.cgf.cx> Please stop sending multiple duplicate messages to the cygwin-xfree mailing list. This is your first and only warning. cgf -- 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/ From aliasghar.toraby@gmail.com Sun Jan 6 18:55:00 2008 From: aliasghar.toraby@gmail.com (Ali Asghar Toraby) Date: Sun, 06 Jan 2008 18:55:00 -0000 Subject: Xwin crashed when i use "-depth 24" In-Reply-To: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> References: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> Message-ID: <477CDAE0.70501@gmail.com> hi thanks for your reply and excuse me for repeating the question i thought that they not delivered successfully so i resend them. but i think cygwin.cause that wrong colors appeared in screen. i use several demos of comerical packages like xconnect-pro and xWin32 and they are working properly. they can taste the settings of CDE. when i use auto detection option in xconnect-pro it run in 26 bpp automatically but in cygwin it runs in 32 by default. i tried to use -depth 26 but it crashed and stopped. you say that hardware must capable to perform 26 bpp. but both target and host computers really work by another tools. :-\ please suggest me a solution. thanks for your attention Phil Betts wrote: > Ali asghar Toraby wrote on Wednesday, January 02, 2008 6:12 AM:: > > >> hi friends >> > > Asking the same question 3 times in quick succession without waiting > for a response will not make you any friends here. > > >> i use xwin to remote solaris8 CDE environment. when i use >> 24 bpp option it crashed and following is the output that it prompt >> to me: ############################################################## >> > > [snip] > > >> winAllocateFBShadowDD - Changing video mode >> winAllocateFBShadowDD - Could not set full screen display mode: >> 80004001 winFinishScreenInitFB - Could not allocate framebuffer >> winScreenInit - winFinishScreenInit () failed >> > > [snip] > > >> how to i can fix this problem? >> > > The -depth parameter must match what your hardware is capable of > displaying. It is usually safest to omit the depth option and let > XWin use the current Windows mode. > > >> i want to use 24 bpp to have a right >> colors in CDE session. in other modes (8,16,32) colors not properly. >> in Xconnect-pro when i use 24 bpp it worked successfully but in >> cygwin/x it crashed and core dumped!! WHY?? :( >> please help me. thanks for any reply >> > > If your Windows display is set to 32bpp, and XWin is started without > the depth option, but CDE does not display the correct colours, I can > only assume that CDE (or the Solaris X11 library) is making invalid > assumptions about the pixel format. If so, then you should address > your question to Sun. There is no problem when running X software > from other vendors. > > Phil > > -- > 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/ From douglas@dhix.com.br Sun Jan 6 19:41:00 2008 From: douglas@dhix.com.br (Douglas Hipocreme) Date: Sun, 06 Jan 2008 19:41:00 -0000 Subject: CygwinX maintainer Message-ID: <477D1486.4090200@dhix.com.br> does need an maintainer until now ? Let me know ? Douglas -- 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/ From cgf-use-the-mailinglist-please@cygwin.com Thu Jan 10 10:07:00 2008 From: cgf-use-the-mailinglist-please@cygwin.com (Christopher Faylor) Date: Thu, 10 Jan 2008 10:07:00 -0000 Subject: CygwinX maintainer In-Reply-To: <477D1486.4090200@dhix.com.br> References: <477D1486.4090200@dhix.com.br> Message-ID: <20080103173246.GC27604@ednor.casa.cgf.cx> On Thu, Jan 03, 2008 at 02:59:50PM -0200, Douglas Hipocreme wrote: > does need an maintainer until now ? > > Let me know ? Yes, we need a maintainer. Are you volunteering? cgf -- 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/ From aliasghar.toraby@gmail.com Thu Jan 10 16:18:00 2008 From: aliasghar.toraby@gmail.com (Ali Asghar Toraby) Date: Thu, 10 Jan 2008 16:18:00 -0000 Subject: Xwin crashed when i use "-depth 24" In-Reply-To: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> References: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> Message-ID: <477CDAE0.70501@gmail.com> hi thanks for your reply and excuse me for repeating the question i thought that they not delivered successfully so i resend them. but i think cygwin.cause that wrong colors appeared in screen. i use several demos of comerical packages like xconnect-pro and xWin32 and they are working properly. they can taste the settings of CDE. when i use auto detection option in xconnect-pro it run in 26 bpp automatically but in cygwin it runs in 32 by default. i tried to use -depth 26 but it crashed and stopped. you say that hardware must capable to perform 26 bpp. but both target and host computers really work by another tools. :-\ please suggest me a solution. thanks for your attention Phil Betts wrote: > Ali asghar Toraby wrote on Wednesday, January 02, 2008 6:12 AM:: > > >> hi friends >> > > Asking the same question 3 times in quick succession without waiting > for a response will not make you any friends here. > > >> i use xwin to remote solaris8 CDE environment. when i use >> 24 bpp option it crashed and following is the output that it prompt >> to me: ############################################################## >> > > [snip] > > >> winAllocateFBShadowDD - Changing video mode >> winAllocateFBShadowDD - Could not set full screen display mode: >> 80004001 winFinishScreenInitFB - Could not allocate framebuffer >> winScreenInit - winFinishScreenInit () failed >> > > [snip] > > >> how to i can fix this problem? >> > > The -depth parameter must match what your hardware is capable of > displaying. It is usually safest to omit the depth option and let > XWin use the current Windows mode. > > >> i want to use 24 bpp to have a right >> colors in CDE session. in other modes (8,16,32) colors not properly. >> in Xconnect-pro when i use 24 bpp it worked successfully but in >> cygwin/x it crashed and core dumped!! WHY?? :( >> please help me. thanks for any reply >> > > If your Windows display is set to 32bpp, and XWin is started without > the depth option, but CDE does not display the correct colours, I can > only assume that CDE (or the Solaris X11 library) is making invalid > assumptions about the pixel format. If so, then you should address > your question to Sun. There is no problem when running X software > from other vendors. > > Phil > > -- > 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/ From aliasghar.toraby@gmail.com Thu Jan 10 19:42:00 2008 From: aliasghar.toraby@gmail.com (Ali Asghar Toraby) Date: Thu, 10 Jan 2008 19:42:00 -0000 Subject: Xwin crashed when i use "-depth 24" In-Reply-To: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> References: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> Message-ID: <477CDAE0.70501@gmail.com> hi thanks for your reply and excuse me for repeating the question i thought that they not delivered successfully so i resend them. but i think cygwin.cause that wrong colors appeared in screen. i use several demos of comerical packages like xconnect-pro and xWin32 and they are working properly. they can taste the settings of CDE. when i use auto detection option in xconnect-pro it run in 26 bpp automatically but in cygwin it runs in 32 by default. i tried to use -depth 26 but it crashed and stopped. you say that hardware must capable to perform 26 bpp. but both target and host computers really work by another tools. :-\ please suggest me a solution. thanks for your attention Phil Betts wrote: > Ali asghar Toraby wrote on Wednesday, January 02, 2008 6:12 AM:: > > >> hi friends >> > > Asking the same question 3 times in quick succession without waiting > for a response will not make you any friends here. > > >> i use xwin to remote solaris8 CDE environment. when i use >> 24 bpp option it crashed and following is the output that it prompt >> to me: ############################################################## >> > > [snip] > > >> winAllocateFBShadowDD - Changing video mode >> winAllocateFBShadowDD - Could not set full screen display mode: >> 80004001 winFinishScreenInitFB - Could not allocate framebuffer >> winScreenInit - winFinishScreenInit () failed >> > > [snip] > > >> how to i can fix this problem? >> > > The -depth parameter must match what your hardware is capable of > displaying. It is usually safest to omit the depth option and let > XWin use the current Windows mode. > > >> i want to use 24 bpp to have a right >> colors in CDE session. in other modes (8,16,32) colors not properly. >> in Xconnect-pro when i use 24 bpp it worked successfully but in >> cygwin/x it crashed and core dumped!! WHY?? :( >> please help me. thanks for any reply >> > > If your Windows display is set to 32bpp, and XWin is started without > the depth option, but CDE does not display the correct colours, I can > only assume that CDE (or the Solaris X11 library) is making invalid > assumptions about the pixel format. If so, then you should address > your question to Sun. There is no problem when running X software > from other vendors. > > Phil > > -- > 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/ From aliasghar.toraby@gmail.com Thu Jan 10 20:06:00 2008 From: aliasghar.toraby@gmail.com (Ali Asghar Toraby) Date: Thu, 10 Jan 2008 20:06:00 -0000 Subject: Xwin crashed when i use "-depth 24" In-Reply-To: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> References: <2D9E96311DCA4C48BF185EA6928BC7BB02FC8628@asc-mail.int.ascribe.com> Message-ID: <477CDAE0.70501@gmail.com> hi thanks for your reply and excuse me for repeating the question i thought that they not delivered successfully so i resend them. but i think cygwin.cause that wrong colors appeared in screen. i use several demos of comerical packages like xconnect-pro and xWin32 and they are working properly. they can taste the settings of CDE. when i use auto detection option in xconnect-pro it run in 26 bpp automatically but in cygwin it runs in 32 by default. i tried to use -depth 26 but it crashed and stopped. you say that hardware must capable to perform 26 bpp. but both target and host computers really work by another tools. :-\ please suggest me a solution. thanks for your attention Phil Betts wrote: > Ali asghar Toraby wrote on Wednesday, January 02, 2008 6:12 AM:: > > >> hi friends >> > > Asking the same question 3 times in quick succession without waiting > for a response will not make you any friends here. > > >> i use xwin to remote solaris8 CDE environment. when i use >> 24 bpp option it crashed and following is the output that it prompt >> to me: ############################################################## >> > > [snip] > > >> winAllocateFBShadowDD - Changing video mode >> winAllocateFBShadowDD - Could not set full screen display mode: >> 80004001 winFinishScreenInitFB - Could not allocate framebuffer >> winScreenInit - winFinishScreenInit () failed >> > > [snip] > > >> how to i can fix this problem? >> > > The -depth parameter must match what your hardware is capable of > displaying. It is usually safest to omit the depth option and let > XWin use the current Windows mode. > > >> i want to use 24 bpp to have a right >> colors in CDE session. in other modes (8,16,32) colors not properly. >> in Xconnect-pro when i use 24 bpp it worked successfully but in >> cygwin/x it crashed and core dumped!! WHY?? :( >> please help me. thanks for any reply >> > > If your Windows display is set to 32bpp, and XWin is started without > the depth option, but CDE does not display the correct colours, I can > only assume that CDE (or the Solaris X11 library) is making invalid > assumptions about the pixel format. If so, then you should address > your question to Sun. There is no problem when running X software > from other vendors. > > Phil > > -- > 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/ From herve.defoucault@siemens.com Fri Jan 11 12:55:00 2008 From: herve.defoucault@siemens.com (Defoucault, Herve) Date: Fri, 11 Jan 2008 12:55:00 -0000 Subject: pdfEdit versus cygwin/ X windows Message-ID: Hi, I try to run the 'pdfedit' application under cygwin. It seems that the problem is due to the 'X server' configuration as the 'pfedit' team guy has written me (see below). Would you mind having a look ? Thanks in advance. Herv? de Foucault Responsable de proposition - Division Automatismes Proposal Manager - Automation Division Siemens VAI Metals Technologies SAS BP 154 - 51, rue Sibert 42403 Saint-Chamond Cedex France Phone : +33 4 7729 8351 Fax : +33 4 7729 8393 Assist : +33 4 7729 8014 www.siemens-vai.com -----Message d'origine----- De?: Michal Hocko [mailto:msts@seznam.cz] Envoy??: 04/01/2008 17:11 ??: Defoucault, Herve Objet?: Re: pdfEdit versus cygwin/ X windows On Fri, Jan 04, 2008 at 03:39:36PM +0100, Defoucault, Herve wrote: > Hi Michal Hocko, Hi. > > Thanks for your answer of yesterday. Since then I have progressed a little bit. (I use my professional email to avoid HTML format ;-)) Thanks ;) Sometimes it is really hard (annoying) to read html emails in console... > I've got now a new question regarding 'pdfedit'. > > I was able to install cygwin on my windows XP computer. > I am able to start the shell. > > 1/ My error message is now: > ============================= > "PDFedit 0.3.2 > > Fatal error! > Environment variable DISPLAY is not set - cannot run GUI for PDFedit" I am not an expert on cygwin, but seems pretty like problem with your X server configuration under cygwin. DISPLAY property *should* be *always* set inside X session. > > I then tried to set the DISPLAY variable thanks to the command 'export': > Export DISPLAY=127.0.0.1:0.0 > This is the localhost address by default. > > 2/ A second error message: > ============================ > "Pdfedit: cannot connect to X server 127.0.0.1:0.0" > > 3/ After running 'xwin' > ========================= > I ran 'xwin' to launch the X window server. I had 1 new X window titled: "X cygwin/X - 0:0" but with the following error message: > > "A fatal error has occurred and cygwin/X wil now exit. Please open /tmp/XWin.log for more information. > Vendor: cygwin/X project > Release: 6.8.99.901-4 > Contact: cygwin-xfree@cygwin.com > XWIN was started with the following command line: xwin" > > 4/ Content of the xwin.log > ============================ > Welcome to the XWin X Server > Vendor: The Cygwin/X Project > Release: 6.8.99.901-4 > > Contact: cygwin-xfree@cygwin.com > > _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root > XWin was started with the following command line: > > xwin > > (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 shared memory support in the kernel > (--) Setting autorepeat to delay=500, rate=31 > (--) winConfigKeyboard - Layout: "0000040C" (0000040c) > (--) 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 list! > > Fatal server error: > could not open default font 'fixed' > > Conclusion. > =========== > Do you have any idea or should I contact the cygwin/X team ? > I suppose I missed a configuration somewhere I think that you should check some cygwin/X howtos. Best regards -- Michal Hocko -- 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/ From holger.krull@gmx.de Mon Jan 14 13:58:00 2008 From: holger.krull@gmx.de (Holger Krull) Date: Mon, 14 Jan 2008 13:58:00 -0000 Subject: pdfEdit versus cygwin/ X windows In-Reply-To: References: Message-ID: <477ED77D.5030103@gmx.de> Defoucault, Herve schrieb: >> >> Fatal server error: >> could not open default font 'fixed' >> >> Conclusion. >> =========== >> Do you have any idea or should I contact the cygwin/X team ? >> I suppose I missed a configuration somewhere > > I think that you should check some cygwin/X howtos. http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-error-font-eof -- 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/ From info@camminodiassisi.it Mon Jan 14 16:19:00 2008 From: info@camminodiassisi.it (info@camminodiassisi.it) Date: Mon, 14 Jan 2008 16:19:00 -0000 Subject: Pilgerweg nach Assisi Message-ID: <20080105205234.DB01AB581A9CF4D5@camminodiassisi.it> Comment=Warum ein Pilgerweg in Italien? Der heilige Franz und der heilige Antonius, der friedfertige Gr??nder und der gelehrte Apostel (??meo episcopus?? = mein Bischof) des Franziskanerordens, sind zwei unvergleichliche Figuren, die einen best??ndigen Motor angez??ndet haben einer dem??tigen und schlichten Geisteshaltung, der eine unversiegbare Quelle ist f??r alle, die an einer existenziellen D??rre leiden. Entsprechend diesen Voraussetzungen entsteht die Notwendigkeit, einen Pilgerweg anzubieten, der die neue geistige Anforderung erf??llt, der, anders als in der Vergangenheit, eine Suche nach ??Bewegung?? ist, wo der Pilger vor allem Ur-Erfahrungen suchen will, um sich ??ffnen zu k??nnen f??r das Mitleiden mit jener ??Liebe, die die Sonne und die andern Sterne bewegt??. Auf den ersten Blick ist es das Ziel des Pilger, nach Assisi zu gehen, aber in Wahrheit ??geht man in sein eigenes Innere??, um sich mit dem G??ttlichen, das in Ihm verborgen ist, zu vereinigen. Der Pilgerweg nach Assisi ist kein neu konzipierter Weg, wie man denken k??nnte, sondern es ist die Verkn??pfung von sehr vielen traditionsreichen Pilgerfahrten, die im lokalen Umkreis schon existieren ( siehe Assisi, La Verna, la Casella, Cerbaiolo, Montecasale, Montepaolo), verbunden mit eigenen Verehrungen, und die, wenn man sie in dieser Dimension wiederbelebt, einen neuen Antrieb f??r das Erforschen des eigenen Innern geben werden und dabei das Wesentliche der Lehre des Franziskus neu aufbl??hen lassen. Und es sollen nicht nur die Steine dem Fremdling Seine Lehre bezeugen, sondern es soll sich auf dem Pilgerweg und in derselben Gemeinschaft auch die urspr??ngliche franziskanische Bruderschaft erneuern. Die Stadt Assisi wird sich erheben zu einem ??Ort der universalen ??bereinstimmung?? f??r die Menschen, die guten Willens sind, indem jeglicher Unterschied von Kultur und Glauben entsprechend den Grundprinzipien jeder wahren Religion ??berwunden wird Mit den besten Gr????en Giordano f??r www.camminodiassisi.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/ From nwourms@gmail.com Thu Jan 17 04:05:00 2008 From: nwourms@gmail.com (Nicholas Wourms) Date: Thu, 17 Jan 2008 04:05:00 -0000 Subject: Compiling XWin (modular Xorg) In-Reply-To: <475F685A.6030504@users.sourceforge.net> References: <1197404086.30103.18.camel@zxvpslinux> <475F685A.6030504@users.sourceforge.net> Message-ID: On Dec 11, 2007 11:49 PM, Yaakov (Cygwin Ports) wrote: > Janjaap Bos wrote: > > The changes I made are all in the patch. Let me know when you have > > suggestions, and whether you're able to build it. Perhaps Yaakov is > > willing to check it with his findings. > > Thank you VERY much. I will try to look into this into the near future, > as the server is the only holdup in getting X11R7 finished on Cygwin. > Hi all, Have you guys checked out the Xming patches (http://www.straightrunning.com/XmingCode/)? Most of them modify code that is the same as we use and contain many fixes to current problems we are experiencing, such as the 24bpp issue. Also, a lot of AG's fixes he did not commit to either trunk or the cygwin branch. He's also come up with a rather unsavory, yet workable hack to the overloaded function issue. There are a ton of DD improvements to the GLX acceleration code, too. Admittedly, the person who runs that project is still using monolithic as the base and has a rather bizarre way of updating the sources uses modular code, but still, it ought to be worthwhile to check out. Unfortunately, he keeps his latest changes behind a "donation" paywall, but I'm sure if asked by a well know cygwin-xorg developer, he would be willing to part with them. As for the overloaded function problem, I do recall we had this same issue back in 2002-2003 with shared libXt. You might want to search through the archives on that one for the whole story. It was a real frustrating problem to deal with, but a good solution was found that worked well. I had a thought on packaging. Perhaps we should adopt the Fedora scheme? I mean they seem to have packaged it nicely without having 60+ packages. We would still want our versioned packages for the runtime, but it should help to cut down on the number of packages without having binary compatibility problems. You could then use the current cygwin x11-xorg package names as "collection" stubs for the individual ones. Just a thought. Cheers, Nicholas -- 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/ From cgf-use-the-mailinglist-please@cygwin.com Thu Jan 17 15:49:00 2008 From: cgf-use-the-mailinglist-please@cygwin.com (Christopher Faylor) Date: Thu, 17 Jan 2008 15:49:00 -0000 Subject: Compiling XWin (modular Xorg) In-Reply-To: References: <1197404086.30103.18.camel@zxvpslinux> <475F685A.6030504@users.sourceforge.net> Message-ID: <20080106194050.GA20794@ednor.casa.cgf.cx> On Sun, Jan 06, 2008 at 01:55:17PM -0500, Nicholas Wourms wrote: >On Dec 11, 2007 11:49 PM, Yaakov (Cygwin Ports) wrote: >> Janjaap Bos wrote: >> > The changes I made are all in the patch. Let me know when you have >> > suggestions, and whether you're able to build it. Perhaps Yaakov is >> > willing to check it with his findings. >> >> Thank you VERY much. I will try to look into this into the near future, >> as the server is the only holdup in getting X11R7 finished on Cygwin. >> >Hi all, > >Have you guys checked out the Xming patches >(http://www.straightrunning.com/XmingCode/)? Most of them modify code >that is the same as we use and contain many fixes to current problems >we are experiencing, such as the 24bpp issue. Also, a lot of AG's >fixes he did not commit to either trunk or the cygwin branch. He's >also come up with a rather unsavory, yet workable hack to the >overloaded function issue. There are a ton of DD improvements to the >GLX acceleration code, too. Admittedly, the person who runs that >project is still using monolithic as the base and has a rather bizarre >way of updating the sources uses modular code, but still, it ought to >be worthwhile to check out. Unfortunately, he keeps his latest changes >behind a "donation" paywall, but I'm sure if asked by a well know >cygwin-xorg developer, he would be willing to part with them. > >As for the overloaded function problem, I do recall we had this same >issue back in 2002-2003 with shared libXt. You might want to search >through the archives on that one for the whole story. It was a real >frustrating problem to deal with, but a good solution was found that >worked well. > >I had a thought on packaging. Perhaps we should adopt the Fedora >scheme? I mean they seem to have packaged it nicely without having 60+ >packages. We would still want our versioned packages for the runtime, >but it should help to cut down on the number of packages without >having binary compatibility problems. You could then use the current >cygwin x11-xorg package names as "collection" stubs for the individual >ones. Just a thought. Who are you talking to here exactly? We don't have a Cygwin/X maintainer so any suggestions or great ideas are guaranteed not to be implmenented. cgf -- 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/ From bengsig@yahoo.com Wed Jan 23 09:19:00 2008 From: bengsig@yahoo.com (B Engsig) Date: Wed, 23 Jan 2008 09:19:00 -0000 Subject: Workaround for foreign keyboard problem to be entered in FAQ section 4.1.6 In-Reply-To: <652404.85872.qm@web25414.mail.ukl.yahoo.com> References: <652404.85872.qm@web25414.mail.ukl.yahoo.com> Message-ID: <14730929.post@talk.nabble.com> rdiezmail-cygwinxfree wrote: > > Hi all: > > I recently hit the foreign keyboard problem described in section 4.1.6 > of the Cygwin/X FAQ. That is, I started with: > > $ setxkbmap.exe de -model pc105 > > Couldn't interpret _XKB_RULES_NAMES property > [...] > > and then I tried what the FAQ said, but I got the following error: > > $ xkbcomp -w 3 -xkm -m de /etc/X11/xkb/keymap/xfree86 localhost:0.0 > Error: Can't find file "xfree86" for keycodes include > Exiting > Abandoning keycodes file "it > > I googled for it, and after a while, I found the solution: > > > I had the same problem... > > By copying the /etc/X11/xkb directory > > into /usr/X11R6/lib/X11/xkb > > It seems to work pretty well now... > > (just in case, I renamed the existing file > C:\cygwin\usr\X11R6\lib\X11\xkb.lnk beforehand to xkb.bak.lnk before > copying over) > > ... > > Well, I _think_ I know what has happened here as it happened to me as well. I had to copy my cygwin environment, and I made a copy on a DVD (of my whole c:\cygwin directory), and re-installed on a freshly created system. When this is being done, I believe all symbolic links, that Windows doesn't know about are being changed to Windows shortcuts with a .lnk extension. Hence, what used to be real (from a cygwin perspective) symbolic links named e.g. "xkb" are changed into Windows shortcuts and renamed "xkb.lnk" during this process. Subsequently, X doesn't start properly and you can e.g. not use the setxkbmap command. -- View this message in context: http://www.nabble.com/Workaround-for-foreign-keyboard-problem-to-be-entered-in-FAQ-section-4.1.6-tp13797565p14730929.html 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/ From linhaiyxs@yahoo.com Fri Jan 25 08:16:00 2008 From: linhaiyxs@yahoo.com (yu xuesheng) Date: Fri, 25 Jan 2008 08:16:00 -0000 Subject: X win can't start under vista 64 bit Message-ID: <345614.83173.qm@web55308.mail.re4.yahoo.com> I am installing cygwin-x windows-gnuplot under vista 64 bit. After I finished installing x windows(X11R6),it can't open the black bash window. A "X" is on the right corner of the disktop. Can anyone help me on this? Thank you! ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping -- 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/ From nomojomofo@gmail.com Fri Jan 25 16:33:00 2008 From: nomojomofo@gmail.com (Erik Earle) Date: Fri, 25 Jan 2008 16:33:00 -0000 Subject: can I forward X packets for windows application to Linux Desktop? Message-ID: In other words, I want to do the opposite of everyone else. I want to run an application on windows and see it remotely from Linux machine. From linux I would: "ssh -Y machine.that.goes.ping" to windows host running cygwin/X. Then execute something like "explorer.exe" and have the windows explorer running remotely on the windows machine popup on my linux desktop. Is this possible? I know about VNC and RDesktop. I want to just have the application window not a window with the full desktop. -- 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/ From holger.krull@gmx.de Fri Jan 25 17:12:00 2008 From: holger.krull@gmx.de (Holger Krull) Date: Fri, 25 Jan 2008 17:12:00 -0000 Subject: can I forward X packets for windows application to Linux Desktop? In-Reply-To: References: Message-ID: <47867A9B.8070207@gmx.de> Erik Earle schrieb: > I want to run an application on windows and see it remotely from Linux > machine. From linux I would: > "ssh -Y machine.that.goes.ping" > to windows host running cygwin/X. > > Then execute something like > "explorer.exe" > and have the windows explorer running remotely on the windows machine > popup on my linux desktop. > > Is this possible? Not the way you want it. Explorer.exe doesn't use X11, so you can't forward it. The same is true for any normal Windows program. You can use cygwins X11 aware programs in that way of course. -- 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/ From mbardiaux@mediaxim.be Sun Jan 27 17:05:00 2008 From: mbardiaux@mediaxim.be (Michel Bardiaux) Date: Sun, 27 Jan 2008 17:05:00 -0000 Subject: can I forward X packets for windows application to Linux Desktop? In-Reply-To: <47867A9B.8070207@gmx.de> References: <47867A9B.8070207@gmx.de> Message-ID: <4787671B.1010101@mediaxim.be> Holger Krull a ??crit : > Erik Earle schrieb: >> I want to run an application on windows and see it remotely from >> Linux machine. From linux I would: "ssh -Y machine.that.goes.ping" >> to windows host running cygwin/X. >> >> Then execute something like "explorer.exe" and have the windows >> explorer running remotely on the windows machine popup on my linux >> desktop. >> >> Is this possible? > > Not the way you want it. Explorer.exe doesn't use X11, so you can't > forward it. The same is true for any normal Windows program. You can > use cygwins X11 aware programs in that way of course. > Once upon a time I read on winehq.org that they were testing running Windows apps inside wine, with wine running under cygwin/X. A bit extreme but if it works it should do what the OP wants. Greetings, -- Michel Bardiaux R&D Director T +32 [0] 2 790 29 41 F +32 [0] 2 790 29 02 E mailto:mbardiaux@mediaxim.be Mediaxim NV/SA Vorstlaan 191 Boulevard du Souverain Brussel 1160 Bruxelles http://www.mediaxim.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/ From Phil.Betts@ascribe.com Sun Jan 27 19:30:00 2008 From: Phil.Betts@ascribe.com (Phil Betts) Date: Sun, 27 Jan 2008 19:30:00 -0000 Subject: Use remote graphical program In-Reply-To: Message-ID: <2D9E96311DCA4C48BF185EA6928BC7BB0311281D@asc-mail.int.ascribe.com> Gustavo Seabra wrote on Thursday, January 03, 2008 3:16 PM:: > On Jan 3, 2008 7:08 AM, Phil Betts wrote: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ http://cygwin.com/acronyms/#PCYMTNQREAIYR >> There is an experimental, but (in my experience) very stable, version >> of XWin with GLX support. This is in package xorg-x11-xwin-gl and >> installs the executable XWin_GL.exe. You would need to alter your >> startxwin.sh to run this instead of XWin.exe. It works, just don't >> expect great performance. >> >> Phil > > That's interesting... Last time I checked, there was no maintainer for > X in Cygwin, but I do admit that was some time ago. So, I'm very > curious to learn about this newer XWin version. If you don't mind, I'd > like to ask a couple of questions: > > 1. Is this package available through setup.exe? Or do we need to > recompile it for Cygwin ourselves? > > 2. What do you mean by "don't expect great performance."? Is it a GLX > issue or something related to this particular version of XWin, as > compared to the older ones? > > Thanks a lot! > Gustavo. Sorry for the delay in replying. I thought I'd sent it thanks to Outlook telling me I had, when in fact it had only saved it in my drafts folder! This isn't new, it was experimental at the time Xwin last had a maintainer and just never got promoted to stable. It's available through setup.exe, but I guess you have to tick the "exp" radio button at the top to see it (once it's installed, it appears without selecting exp). In terms of performance, GL software is really designed for running on the local host, so you're never going to get blazing performance running clients on a remote host. The network overhead slows it down considerably. However, XWin's GLX is not particularly fast, even when running locally. Running glxgears.exe at the default size, on XWin running on my laptop, I get (approximately): 62 fps running locally 31 fps running on a linux box without using ssh forwarding 21 fps running on a linux box via ssh forwarding without compression. 47 fps running on a linux box via ssh forwarding with compression. None of these are stunning (IIRC, I get several hundreds of fps on a linux box at home), but it may be adequate for your purposes. My experience is that native GL applications running on Windows (e.g. Blender3D) run noticeably faster when running full screen (if they can), because there is no contention with DirectX. I haven't tested it, but if performance is a problem, it may be worth trying XWin full screen before giving up on it. I haven't looked at the code, but the locally run glxgears runs at 100% cpu on my laptop, which suggests that much of the GL code is handled in software, rather than hardware accelerated. The remote tests all run at about 92% cpu, so the network is (just) the limiting factor. Phil -- 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/ From Scott.Mohnkern@noaa.gov Sun Jan 27 23:18:00 2008 From: Scott.Mohnkern@noaa.gov (Scott Mohnkern) Date: Sun, 27 Jan 2008 23:18:00 -0000 Subject: Windowmaker, fullscreen, 8-bit video and problems In-Reply-To: References: Message-ID: <478B8B54.8040908@noaa.gov> We're in an environment where we're opening ssh connections to a box and running an application that needs 8 bit color. We realized that in order to do this, we needed to open up windowmaker in fullscreen mode, and set it to 8 bit video. This is the end of our startup script: run XWin :10 -clipboard -silent-dup-error -fullscreen -depth 8 run wmaker Windowmaker is opening, but when we ssh into the box, the color scheme for the entire computer gets completely unreadable, as do the fonts. Is there any other easy way to have an xterm session that does 8 bit video, just in that window? Scott Mohnkern -- 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/ From cw4279@yahoo.com Mon Jan 28 00:29:00 2008 From: cw4279@yahoo.com (A A) Date: Mon, 28 Jan 2008 00:29:00 -0000 Subject: xauth problem - "unable to link authority file" Message-ID: <754748.86945.qm@web46004.mail.sp1.yahoo.com> Uninstalling the "Embassy Trust Suite" that was pre-installed in my Dell fixed the problem described below. xauth works fine now. A search of the list revealed that this same Wave Systems Embassy Trust Suite software has caused other compatibility problems with cygwin as well. Does anybody know, if this software did something useful or even important? I am not using the fingerprint reader and I have not enabled the TPM chip. Did I loose something by uninstalling it? (I know this is a question for some other list but just in case somebody else has studied this during their cygwin problems.) Thank you very much and best regards. CW ----- Original Message ---- > From: A A > To: cygwin-xfree@cygwin.com > Sent: Thursday, December 27, 2007 2:36:17 PM > Subject: xauth problem - "unable to link authority file" > > I would greatly appreciate any help in resolving this issue. > > > > I have XP Professional (5.1.2600 SP2) updated with the latest > software > from Windows update. > > > cygwin was installed with setup.exe within the last week. > > > > Here is a simple way to reproduce the problem: > > > > $ xauth -v -f authfile generate :0 . untrusted timeout 1200 > > xauth: creating new authority file authfile > > Using authority file authfile > > authorization id is 66 > > Writing authority file authfile > > xauth: unable to link authority file authfile, use authfile-n > > > > I assume it is trying to "link authfile-n authfile". Manually > this > works fine and I can also "unlink authfile-n". > > > > What is a likely reason for the failure of "link authfile-n > authfile" > and is there a way to fix this? > > > > Thank you very much. > > > > CW > > > > > > > > > > ________________________________________________________________________________ > ____ > Never miss a thing. Make Yahoo your home page. > http://www.yahoo.com/r/hs > ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ -- 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/ From smukherjee@bloxx.com Mon Jan 28 03:51:00 2008 From: smukherjee@bloxx.com (Suman Mukherjee) Date: Mon, 28 Jan 2008 03:51:00 -0000 Subject: Key Stroke Mapping In-Reply-To: <77E47566413AE546903D21B53DCFEF030F9449@caesar.alba.local> Message-ID: <77E47566413AE546903D21B53DCFEF030F944A@caesar.alba.local> Hello I am using cygwin and X-window. >From cygwin terminal my keystrokes are proper. However from X window terminal, my keystrokes are totally mixed up. e.g. \ mapped to # # mapped to ? and so on. It is very difficult to keep the track. Would you please help me to reset those settings as normal one. I am using windows XP. Regards Suman PS: Below is the script I am using to run the X-terminals -------------------------------------------------- @echo off SET DISPLAY=127.0.0.1:0.0 REM REM The path in the CYGWIN_ROOT environment variable assignment assume REM that Cygwin is installed in a directory called 'cygwin' in the root REM directory of the current drive.? You will only need to modify REM CYGWIN_ROOT if you have installed Cygwin in another directory.? For REM example, if you installed Cygwin in \foo\bar\baz\cygwin, you will need REM to change \cygwin to \foo\bar\baz\cygwin. REM REM This batch file will almost always be run from the same drive (and REM directory) as the drive that contains Cygwin/X, therefore you will REM not need to add a drive letter to CYGWIN_ROOT.? For example, you do REM not need to change \cygwin to c:\cygwin if you are running this REM batch file from the C drive. REM SET CYGWIN_ROOT=\cygwin SET RUN=%CYGWIN_ROOT%\bin\run -p /usr/X11R6/bin SET PATH=.;%CYGWIN_ROOT%\bin;%CYGWIN_ROOT%\usr\X11R6\bin;%PATH% SET XAPPLRESDIR=/usr/X11R6/lib/X11/app-defaults SET XCMSDB=/usr/X11R6/lib/X11/Xcms.txt SET XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB SET XNLSPATH=/usr/X11R6/lib/X11/locale REM REM Cleanup after last run. REM if not exist %CYGWIN_ROOT%\tmp\.X11-unix\X0 goto CLEANUP-FINISH attrib -s %CYGWIN_ROOT%\tmp\.X11-unix\X0 del %CYGWIN_ROOT%\tmp\.X11-unix\X0 :CLEANUP-FINISH if exist %CYGWIN_ROOT%\tmp\.X11-unix rmdir %CYGWIN_ROOT%\tmp\.X11-unix REM REM The error "Fatal server error: could not open default font 'fixed'" is REM caused by using a DOS mode mount for the mount that the Cygwin/X REM fonts are accessed through.? See the Cygwin/X FAQ for more REM information: REM http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-error-font-eof REM REM if "%OS%" == "Windows_NT" goto OS_NT REM Windows 95/98/Me echo startxwin.bat - Starting on Windows 95/98/Me goto STARTUP :OS_NT REM Windows NT/2000/XP/2003 echo startxwin.bat - Starting on Windows NT/2000/XP/2003 :STARTUP REM Brief descriptions of XWin-specific options: REM REM -screen scr_num [width height] REM????? Enable screen scr_num and optionally specify a width and REM????? height for that screen. REM????? Most importantly, any parameters specified before the first -screen REM????? parameter apply to all screens.? Any options after the first -screen REM????? parameter apply only to the screen that precedes the parameter. REM????? Example: REM????????? XWin -fullscreen -screen 0 -screen 1 -depth 8 -screen 2 REM????? All screens will be fullscreen, but screen 2 will be depth 8, while REM????? screens 0 and 1 will be the default depth (whatever depth Windows REM????? is currently running at). REM -multiwindow REM????? Start an integrated Windows-based window manager.? Not to be used REM????? with -rootless nor -fullscreen. REM -rootless REM????? Use a transparent root window with an external window manager REM????? (such as twm).? Not to be used with -multiwindow nor REM????? with -fullscreen. REM -fullscreen REM????? Use a window as large as possible on the primary monitor. REM -multiplemonitors REM????? Create a root window that covers all monitors on a REM????? system with multiple monitors. REM -clipboard REM????? Enable the integrated version of xwinclip.? Do not use in REM????? conjunction with the xwinclip program. REM -depth bits_per_pixel REM????? Specify the screen depth to run at (in bits per pixel) using a REM????? DirectDraw-based engine in conjunction with the -fullscreen REM????? option, ignored if the -fullscreen option is not specified. REM????? By default, you will be using a DirectDraw based engine on any REM????? system that supports it. REM -unixkill REM????? Trap Ctrl+Alt+Backspace as a server shutdown key combination. REM -nounixkill REM????? Disable Ctrl+Alt+Backspace as a server shutdown key combination (default). REM????? Example: REM????????? XWin -unixkill -screen 0 -screen 1 -screen 2 -nounixkill REM????? Screens 0 and 1 will allow Ctrl+Alt+Backspace, but screen 2 will not. REM -winkill REM????? Trap Alt+F4 as a server shutdown key combination (default). REM -nowinkill REM????? Disable Alt+F4 as a server shutdown key combination. REM -scrollbars REM????? Enable resizing of the server display window.? Do not use in conjunction REM????? with -multiwindow nor with -rootless. REM -nodecoration REM????? Draw the server root window without a title bar or border. REM????? Do not use with -mutliwindow nor with -rootless. REM -lesspointer REM????? Hide the Windows mouse cursor anytime it is over any part of the REM????? window, even if Cygwin/X is not the window with the focus. REM -refresh rate_in_Hz REM????? Specify a refresh rate to use when used with the -fullscreen option. REM -trayicon REM????? Enable the tray icon (default). REM -notrayicon REM????? Disable the tray icon. REM????? Example: REM????????? XWin -notrayicon -screen 0 -screen 1 -screen 2 -trayicon REM????? Screens 0 and 1 will not have tray icons, but screen 2 will. REM -emulate3buttons [timeout] REM????? Emulate 3 button mouse with an optional timeout in milliseconds. REM -xf86config REM????? Specify an XF86Config-style configuration file. REN -keyboard REM????? Specify a keyboard device from the configuration file. REM REM Startup the programs REM REM Startup the X Server with the integrated Windows-based window manager. REM WARNING: Do not use 'xwinclip' in conjunction with the ``-clipboard'' REM command-line parameter for XWin.? Doing so would start two clipboard REM managers, which is never supposed to happen. %RUN% XWin -multiwindow -clipboard -silent-dup-error REM Startup an xterm, using bash as the shell. %RUN% xterm -e /usr/bin/bash -l REM REM Startup the twm window manager. REM WARNING: Do not use an external window manager in conjunction with REM the ``-multiwindow'' command-line parameter for XWin.? Doing so REM would start two window managers, which is never supposed to happen. REM REM %RUN% twm REM Set a background color.? Only needed when not using -multwindow for XWin. %RUN% xsetroot -solid aquamarine4 -- 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/ From giantolo@yahoo.it Mon Jan 28 06:52:00 2008 From: giantolo@yahoo.it (Giacomo Cerrai) Date: Mon, 28 Jan 2008 06:52:00 -0000 Subject: start gvim in X with Fatal IO error 104 Message-ID: <4180.78547.qm@web58705.mail.re1.yahoo.com> f gao wrote: > Dear all: > Does anyone know how to start gvim in cygwin/X? > Each time I start gvim, the GUI flashes and get closed > with error "gvim: Fatal IO error 104 (Connection reset > by peer) on X server 127.0.0.1:0.0". > Since the emacs can start and work in X11, I guess the > X is installed correctly. Is it a bug of gvim? (The Very same problem here. It looks like the detaching from the terminal does not work properly. > installed vim version is 7.0.122-1, gvim is > 7.0.035-2,X is 6.8.99.901-44) > Any suggestion is appreciated! Try this: $ gvim --nofork & g. ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping -- 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/ From francois.rappaz@unifr.ch Mon Jan 28 08:02:00 2008 From: francois.rappaz@unifr.ch (RAPPAZ Francois) Date: Mon, 28 Jan 2008 08:02:00 -0000 Subject: Swiss french keyboard problems Message-ID: <901E0425ED9984448E106CA3432E5CC55F28F2@EXCHANGE4.unifr.ch> Hi I got a wrong mapping with my keyboard: eg shit + 1 key gives ! instead of +. When I start X cygwin with the startxwin.bat file, the log file does not complain: (--) winConfigKeyboard - Layout: "0000100C" (0000100c) (--) Using preset keyboard for "French (Switzerland)" (100c), type "4" However the shift keys are wrong. In the Xterm running in the X windows, if tried $ setxkbmap fr_CH -model pc105 I got "Error loading new keyboard description" but the command xkbcomp -w 3 -xkm -m fr_CH /etc/X11/xkb/keymap/xfree86 localhost:0.0 cure the problems. However if I start a new session, the wrong mapping is there again. What should I do to avoid to have to recompile my keyboard layout for each new session ? Thanks for any help Fran?ois Rappaz -- 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/ From per.steffen@gmail.com Mon Jan 28 10:06:00 2008 From: per.steffen@gmail.com (Per Thorlacius) Date: Mon, 28 Jan 2008 10:06:00 -0000 Subject: Problem with arrow keys in x-based applications on cygwin In-Reply-To: <76f7fcad0801250826l65bf4a72iff58ed3d59499976@mail.gmail.com> References: <76f7fcad0801250826l65bf4a72iff58ed3d59499976@mail.gmail.com> Message-ID: <76f7fcad0801250833p80788efx1b77be58d908f445@mail.gmail.com> Hi Im running the newest version of Cygwin on Win 2k Pro. In the Cygwin standard shell my left and right arrow keys work fine. However, if I start an xterm or any other x-based application from the cygwin standard shell, the left and right arrow keys are not working in the x-based application. I am starting the x-server using the following parameters: XWin -multiwindow -clipboard -xkblayout dk -xkbmodel pc105 I have tried different keyboard layouts and models, including standard "us" without any luck. Looking at the man page for setxkblayout there are lots of possibilities for customisation, however it looks as if it will take quite an effort to get into all the details. Any ideas for a quick solution? Can I just use the standard keyboard layout from Win 2k without overriding it when starting my x-server? Best regards, Per -- 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/ From dickey@his.com Mon Jan 28 14:16:00 2008 From: dickey@his.com (Thomas Dickey) Date: Mon, 28 Jan 2008 14:16:00 -0000 Subject: Problem with arrow keys in x-based applications on cygwin In-Reply-To: <76f7fcad0801250833p80788efx1b77be58d908f445@mail.gmail.com> References: <76f7fcad0801250826l65bf4a72iff58ed3d59499976@mail.gmail.com> <76f7fcad0801250833p80788efx1b77be58d908f445@mail.gmail.com> Message-ID: <20080125120958.X65280@mail101.his.com> On Fri, 25 Jan 2008, Per Thorlacius wrote: > Hi > > Im running the newest version of Cygwin on Win 2k Pro. In the Cygwin > standard shell my left and right arrow keys work fine. However, if I > start an xterm or any other x-based application from the cygwin > standard shell, the left and right arrow keys are not working in the > x-based application. I am starting the x-server using the following > parameters: Do the arrow keys send escape sequences, or are they entirely ignored? (The latter is a keyboard problem as you're suggesting, the former may be simpler). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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/ From ohaya@cox.net Mon Jan 28 15:59:00 2008 From: ohaya@cox.net (ohaya) Date: Mon, 28 Jan 2008 15:59:00 -0000 Subject: Problem with X (disappears) and Sun Directory Server Console Message-ID: Hi, I'm new here, but I'm trying to use Cygwin X to access the administration console for Sun Directory Server 6.1. I run startxwin.bat, get the xterm window, run "xhost +" and then SSH to the server, export DISPLAY, and start the console using a command called "startconsole". This causes the console GUI to appear but when I type in my username/password, everything, including the original xterm window disappears. I've tried access the admin console using Hummingbird Exceed, and that seems to work fine. This problem only occurs when I use Cygwin X. The XWin.log file has the following in it after this happens: _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777 (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1024 height: 768 depth: 16 winInitVisualsShadowGDI - Masks 0000f800 000007e0 0000001f BPRGB 6 d 16 bpp 16 null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello winMultiWindowXMsgProc - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Calling pthread_mutex_lock () MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: "00000409" (00000409) (--) Using preset keyboard for "English (USA)" (409), type "4" (--) 3 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winInitMultiWindowWM - pthread_mutex_lock () returned. winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winClipboardProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winClipboardProc - XOpenDisplay () returned and successfully opened the display. winProcSetSelectionOwner - Clipboard not yet started, aborting. winProcSetSelectionOwner - Clipboard not yet started, aborting. winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter attributes) winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. winMultiWindowXMsgProcIOErrorHandler! winInitMultiWindowXMsgProc - Caught IO Error. Exiting. FreeFontPath: FPE "/usr/X11R6/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing. (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information Does anyone know what might be causing this problem, and also how to fix it? Thanks, Jim -- 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/ From per.steffen@gmail.com Tue Jan 29 06:00:00 2008 From: per.steffen@gmail.com (Per Thorlacius) Date: Tue, 29 Jan 2008 06:00:00 -0000 Subject: Problem with arrow keys in x-based applications on cygwin In-Reply-To: <76f7fcad0801250833p80788efx1b77be58d908f445@mail.gmail.com> References: <76f7fcad0801250826l65bf4a72iff58ed3d59499976@mail.gmail.com> <76f7fcad0801250833p80788efx1b77be58d908f445@mail.gmail.com> Message-ID: <76f7fcad0801271130n3a37edd0udcbba51010b3acc4@mail.gmail.com> >> Im running the newest version of Cygwin on Win 2k Pro. In the Cygwin >> standard shell my left and right arrow keys work fine. However, if I >> start an xterm or any other x-based application from the cygwin >> standard shell, the left and right arrow keys are not working in the >> x-based application. I am starting the x-server using the following >> parameters: >> >> XWin -multiwindow -clipboard -xkblayout dk -xkbmodel pc105 >> >> I have tried different keyboard layouts and models, including standard >> "us" without any luck. Looking at the man page for setxkblayout there >> are lots of possibilities for customisation, however it looks as if it >> will take quite an effort to get into all the details. Any ideas for a >> quick solution? Can I just use the standard keyboard layout from Win >> 2k without overriding it when starting my x-server? > Thomas E. Dickey: > Do the arrow keys send escape sequences, or are they entirely ignored? > (The latter is a keyboard problem as you're suggesting, the former may be simpler). The arrow keys are not sending escape sequences, they are entirely ignored. Best regards, Per -- 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/ From cabrera@wrc.xerox.com Tue Jan 29 17:47:00 2008 From: cabrera@wrc.xerox.com (jose isaias cabrera) Date: Tue, 29 Jan 2008 17:47:00 -0000 Subject: Problem with X (disappears) and Sun Directory Server Console References: Message-ID: <004801c8613a$f173e180$0a00a8c0@stso.mc.xerox.com> I don't know if it is the same or not, but I had a similar problem with a Gentoo server. I tried everything, but once I recreated the account, I was able to connect. Try creating a new account and give it a try. Just a thought... thanks, jic "ohaya" wrote, > Hi, > > I'm new here, but I'm trying to use Cygwin X to access the administration > console for Sun Directory Server 6.1. I run startxwin.bat, get the xterm > window, run "xhost +" and then SSH to the server, export DISPLAY, and > start the console using a command called "startconsole". This causes the > console GUI to appear but when I type in my username/password, everything, > including the original xterm window disappears. > > I've tried access the admin console using Hummingbird Exceed, and that > seems to work fine. This problem only occurs when I use Cygwin X. > > The XWin.log file has the following in it after this happens: > > _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root > _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777 (II) > XF86Config is not supported (II) See > http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information > winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per > pixel winAllocateFBShadowGDI - Creating DIB with width: 1024 height: 768 > depth: 16 winInitVisualsShadowGDI - Masks 0000f800 000007e0 0000001f BPRGB > 6 d 16 bpp 16 null screen fn ReparentWindow null screen fn RestackWindow > InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init > returned InitQueue - Calling pthread_cond_init InitQueue - > pthread_cond_init returned winInitMultiWindowWM - Hello > winMultiWindowXMsgProc - Hello winInitMultiWindowWM - Calling > pthread_mutex_lock () winMultiWindowXMsgProc - Calling pthread_mutex_lock > () MIT-SHM extension disabled due to lack of kernel support > XFree86-Bigfont extension local-client optimization disabled due to lack > of shared memory support in the kernel (--) Setting autorepeat to > delay=500, rate=31 (--) winConfigKeyboard - Layout: "00000409" (00000409) > (--) Using preset keyboard for "English (USA)" (409), type "4" (--) 3 > mouse buttons found Could not init font path element > /usr/X11R6/lib/X11/fonts/CID/, removing from list! winInitMultiWindowWM - > pthread_mutex_lock () returned. winProcEstablishConnection - Hello > winInitClipboard () winProcEstablishConnection - winInitClipboard > returned. winClipboardProc - Hello DetectUnicodeSupport - Windows > NT/2000/XP winInitMultiWindowWM - pthread_mutex_unlock () returned. > winMultiWindowXMsgProc - pthread_mutex_lock () returned. > winClipboardProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - > DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_unlock () > returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 > winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened > the display. winInitMultiWindowWM - XOpenDisplay () returned and > successfully opened the display. winClipboardProc - XOpenDisplay () > returned and successfully opened the display. winProcSetSelectionOwner - > Clipboard not yet started, aborting. winProcSetSelectionOwner - Clipboard > not yet started, aborting. winMultiWindowXMsgProcErrorHandler - ERROR: > BadMatch (invalid parameter attributes) > winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter > attributes) winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid > parameter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch > (invalid parameter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: > BadMatch (invalid parameter attributes) > winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter > attributes) winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid > parameter attributes) winClipboardProc - > winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main > loop. winClipboardProc - XDestroyWindow succeeded. > winMultiWindowXMsgProcIOErrorHandler! winInitMultiWindowXMsgProc - Caught > IO Error. Exiting. FreeFontPath: FPE "/usr/X11R6/lib/X11/fonts/misc/" > refcount is 2, should be 1; fixing. (II) XF86Config is not supported (II) > See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information > > Does anyone know what might be causing this problem, and also how to fix > it? > > Thanks, > Jim -- 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/ From ohaya@cox.net Tue Jan 29 18:55:00 2008 From: ohaya@cox.net (ohaya) Date: Tue, 29 Jan 2008 18:55:00 -0000 Subject: Problem with X (disappears) and Sun Directory Server Console In-Reply-To: <004801c8613a$f173e180$0a00a8c0@stso.mc.xerox.com> References: <004801c8613a$f173e180$0a00a8c0@stso.mc.xerox.com> Message-ID: Jose, When you say "create a new account", which account did you mean? FYI, both myself and two other colleagues tried this, each with our own Windows accounts and accounts on the Linux machine where Sun DS is on, and all 3 of us (so far) have had this problem. Jim jose isaias cabrera wrote: > > I don't know if it is the same or not, but I had a similar problem with > a Gentoo server. I tried everything, but once I recreated the account, > I was able to connect. Try creating a new account and give it a try. > Just a thought... > > thanks, > > jic > > "ohaya" wrote, > >> Hi, >> >> I'm new here, but I'm trying to use Cygwin X to access the >> administration console for Sun Directory Server 6.1. I run >> startxwin.bat, get the xterm window, run "xhost +" and then SSH to the >> server, export DISPLAY, and start the console using a command called >> "startconsole". This causes the console GUI to appear but when I type >> in my username/password, everything, including the original xterm >> window disappears. >> >> I've tried access the admin console using Hummingbird Exceed, and that >> seems to work fine. This problem only occurs when I use Cygwin X. >> >> The XWin.log file has the following in it after this happens: >> >> _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root >> _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777 (II) >> XF86Config is not supported (II) See >> http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information >> winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits >> per pixel winAllocateFBShadowGDI - Creating DIB with width: 1024 >> height: 768 depth: 16 winInitVisualsShadowGDI - Masks 0000f800 >> 000007e0 0000001f BPRGB 6 d 16 bpp 16 null screen fn ReparentWindow >> null screen fn RestackWindow InitQueue - Calling pthread_mutex_init >> InitQueue - pthread_mutex_init returned InitQueue - Calling >> pthread_cond_init InitQueue - pthread_cond_init returned >> winInitMultiWindowWM - Hello winMultiWindowXMsgProc - Hello >> winInitMultiWindowWM - Calling pthread_mutex_lock () >> winMultiWindowXMsgProc - Calling pthread_mutex_lock () MIT-SHM >> extension disabled due to lack of kernel support XFree86-Bigfont >> extension local-client optimization disabled due to lack of shared >> memory support in the kernel (--) Setting autorepeat to delay=500, >> rate=31 (--) winConfigKeyboard - Layout: "00000409" (00000409) (--) >> Using preset keyboard for "English (USA)" (409), type "4" (--) 3 mouse >> buttons found Could not init font path element >> /usr/X11R6/lib/X11/fonts/CID/, removing from list! >> winInitMultiWindowWM - pthread_mutex_lock () returned. >> winProcEstablishConnection - Hello winInitClipboard () >> winProcEstablishConnection - winInitClipboard returned. >> winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP >> winInitMultiWindowWM - pthread_mutex_unlock () returned. >> winMultiWindowXMsgProc - pthread_mutex_lock () returned. >> winClipboardProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - >> DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_unlock () >> returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 >> winMultiWindowXMsgProc - XOpenDisplay () returned and successfully >> opened the display. winInitMultiWindowWM - XOpenDisplay () returned >> and successfully opened the display. winClipboardProc - XOpenDisplay >> () returned and successfully opened the display. >> winProcSetSelectionOwner - Clipboard not yet started, aborting. >> winProcSetSelectionOwner - Clipboard not yet started, aborting. >> winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid >> parameter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: >> BadMatch (invalid parameter attributes) >> winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid >> parameter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: >> BadMatch (invalid parameter attributes) >> winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid >> parameter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: >> BadMatch (invalid parameter attributes) >> winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid >> parameter attributes) winClipboardProc - >> winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting >> main loop. winClipboardProc - XDestroyWindow succeeded. >> winMultiWindowXMsgProcIOErrorHandler! winInitMultiWindowXMsgProc - >> Caught IO Error. Exiting. FreeFontPath: FPE >> "/usr/X11R6/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing. >> (II) XF86Config is not supported (II) See >> http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information >> >> Does anyone know what might be causing this problem, and also how to >> fix it? >> >> Thanks, >> Jim > > > > -- > 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/ From cabrera@wrc.xerox.com Tue Jan 29 20:34:00 2008 From: cabrera@wrc.xerox.com (jose isaias cabrera) Date: Tue, 29 Jan 2008 20:34:00 -0000 Subject: Problem with X (disappears) and Sun Directory Server Console References: <004801c8613a$f173e180$0a00a8c0@stso.mc.xerox.com> Message-ID: <005701c86161$12d59b90$0a00a8c0@stso.mc.xerox.com> Sorry about that. I created the account at linux server which I wanted to connect to. ----- Original Message ----- From: "ohaya" To: Sent: Sunday, January 27, 2008 7:29 PM Subject: Re: Problem with X (disappears) and Sun Directory Server Console > Jose, > > When you say "create a new account", which account did you mean? > > FYI, both myself and two other colleagues tried this, each with our own > Windows accounts and accounts on the Linux machine where Sun DS is on, and > all 3 of us (so far) have had this problem. > > Jim > > > jose isaias cabrera wrote: >> >> I don't know if it is the same or not, but I had a similar problem with a >> Gentoo server. I tried everything, but once I recreated the account, I >> was able to connect. Try creating a new account and give it a try. Just >> a thought... >> >> thanks, >> >> jic >> >> "ohaya" wrote, >> >>> Hi, >>> >>> I'm new here, but I'm trying to use Cygwin X to access the >>> administration console for Sun Directory Server 6.1. I run >>> startxwin.bat, get the xterm window, run "xhost +" and then SSH to the >>> server, export DISPLAY, and start the console using a command called >>> "startconsole". This causes the console GUI to appear but when I type >>> in my username/password, everything, including the original xterm window >>> disappears. >>> >>> I've tried access the admin console using Hummingbird Exceed, and that >>> seems to work fine. This problem only occurs when I use Cygwin X. >>> >>> The XWin.log file has the following in it after this happens: >>> >>> _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root >>> _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777 (II) >>> XF86Config is not supported (II) See >>> http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information >>> winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per >>> pixel winAllocateFBShadowGDI - Creating DIB with width: 1024 height: 768 >>> depth: 16 winInitVisualsShadowGDI - Masks 0000f800 000007e0 0000001f >>> BPRGB 6 d 16 bpp 16 null screen fn ReparentWindow null screen fn >>> RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - >>> pthread_mutex_init returned InitQueue - Calling pthread_cond_init >>> InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello >>> winMultiWindowXMsgProc - Hello winInitMultiWindowWM - Calling >>> pthread_mutex_lock () winMultiWindowXMsgProc - Calling >>> pthread_mutex_lock () MIT-SHM extension disabled due to lack of kernel >>> support XFree86-Bigfont extension local-client optimization disabled due >>> to lack of shared memory support in the kernel (--) Setting autorepeat >>> to delay=500, rate=31 (--) winConfigKeyboard - Layout: "00000409" >>> (00000409) (--) Using preset keyboard for "English (USA)" (409), type >>> "4" (--) 3 mouse buttons found Could not init font path element >>> /usr/X11R6/lib/X11/fonts/CID/, removing from list! >>> winInitMultiWindowWM - pthread_mutex_lock () returned. >>> winProcEstablishConnection - Hello winInitClipboard () >>> winProcEstablishConnection - winInitClipboard returned. >>> winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP >>> winInitMultiWindowWM - pthread_mutex_unlock () returned. >>> winMultiWindowXMsgProc - pthread_mutex_lock () returned. >>> winClipboardProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - >>> DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_unlock () >>> returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 >>> winMultiWindowXMsgProc - XOpenDisplay () returned and successfully >>> opened the display. winInitMultiWindowWM - XOpenDisplay () returned and >>> successfully opened the display. winClipboardProc - XOpenDisplay () >>> returned and successfully opened the display. winProcSetSelectionOwner - >>> Clipboard not yet started, aborting. winProcSetSelectionOwner - >>> Clipboard not yet started, aborting. >>> winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter >>> attributes) winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch >>> (invalid parameter attributes) winMultiWindowXMsgProcErrorHandler - >>> ERROR: BadMatch (invalid parameter attributes) >>> winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter >>> attributes) winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch >>> (invalid parameter attributes) winMultiWindowXMsgProcErrorHandler - >>> ERROR: BadMatch (invalid parameter attributes) >>> winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid parameter >>> attributes) winClipboardProc - winClipboardFlushWindowsMessageQueue >>> trapped WM_QUIT message, exiting main loop. winClipboardProc - >>> XDestroyWindow succeeded. winMultiWindowXMsgProcIOErrorHandler! >>> winInitMultiWindowXMsgProc - Caught IO Error. Exiting. FreeFontPath: FPE >>> "/usr/X11R6/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing. >>> (II) XF86Config is not supported (II) See >>> http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information >>> >>> Does anyone know what might be causing this problem, and also how to fix >>> it? >>> >>> Thanks, >>> Jim >> >> >> >> -- >> 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/ > -- 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/ From ohaya@cox.net Wed Jan 30 10:35:00 2008 From: ohaya@cox.net (ohaya) Date: Wed, 30 Jan 2008 10:35:00 -0000 Subject: Problem with X (disappears) and Sun Directory Server Console In-Reply-To: <005701c86161$12d59b90$0a00a8c0@stso.mc.xerox.com> References: <004801c8613a$f173e180$0a00a8c0@stso.mc.xerox.com> <005701c86161$12d59b90$0a00a8c0@stso.mc.xerox.com> Message-ID: Jose, It doesn't seem that that would be the problem in our case, since, as I mentioned in original message, if I use Hummingbird Exceed as my X server (with logging into the server with Sun DS as the same Linux account), it works perfectly. That Xwin.log that I included in my msg seems to indicate that it's having a problem with starting the Clipboard. Would that cause this problem, and if so, how to fix it? Jim jose isaias cabrera wrote: > > Sorry about that. I created the account at linux server which I wanted > to connect to. > > > ----- Original Message ----- From: "ohaya" > To: > Sent: Sunday, January 27, 2008 7:29 PM > Subject: Re: Problem with X (disappears) and Sun Directory Server Console > > >> Jose, >> >> When you say "create a new account", which account did you mean? >> >> FYI, both myself and two other colleagues tried this, each with our >> own Windows accounts and accounts on the Linux machine where Sun DS is >> on, and all 3 of us (so far) have had this problem. >> >> Jim >> >> >> jose isaias cabrera wrote: >> >>> >>> I don't know if it is the same or not, but I had a similar problem >>> with a Gentoo server. I tried everything, but once I recreated the >>> account, I was able to connect. Try creating a new account and give >>> it a try. Just a thought... >>> >>> thanks, >>> >>> jic >>> >>> "ohaya" wrote, >>> >>>> Hi, >>>> >>>> I'm new here, but I'm trying to use Cygwin X to access the >>>> administration console for Sun Directory Server 6.1. I run >>>> startxwin.bat, get the xterm window, run "xhost +" and then SSH to >>>> the server, export DISPLAY, and start the console using a command >>>> called "startconsole". This causes the console GUI to appear but >>>> when I type in my username/password, everything, including the >>>> original xterm window disappears. >>>> >>>> I've tried access the admin console using Hummingbird Exceed, and >>>> that seems to work fine. This problem only occurs when I use Cygwin X. >>>> >>>> The XWin.log file has the following in it after this happens: >>>> >>>> _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root >>>> _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777 (II) >>>> XF86Config is not supported (II) See >>>> http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information >>>> winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits >>>> per pixel winAllocateFBShadowGDI - Creating DIB with width: 1024 >>>> height: 768 depth: 16 winInitVisualsShadowGDI - Masks 0000f800 >>>> 000007e0 0000001f BPRGB 6 d 16 bpp 16 null screen fn ReparentWindow >>>> null screen fn RestackWindow InitQueue - Calling pthread_mutex_init >>>> InitQueue - pthread_mutex_init returned InitQueue - Calling >>>> pthread_cond_init InitQueue - pthread_cond_init returned >>>> winInitMultiWindowWM - Hello winMultiWindowXMsgProc - Hello >>>> winInitMultiWindowWM - Calling pthread_mutex_lock () >>>> winMultiWindowXMsgProc - Calling pthread_mutex_lock () MIT-SHM >>>> extension disabled due to lack of kernel support XFree86-Bigfont >>>> extension local-client optimization disabled due to lack of shared >>>> memory support in the kernel (--) Setting autorepeat to delay=500, >>>> rate=31 (--) winConfigKeyboard - Layout: "00000409" (00000409) (--) >>>> Using preset keyboard for "English (USA)" (409), type "4" (--) 3 >>>> mouse buttons found Could not init font path element >>>> /usr/X11R6/lib/X11/fonts/CID/, removing from list! >>>> winInitMultiWindowWM - pthread_mutex_lock () returned. >>>> winProcEstablishConnection - Hello winInitClipboard () >>>> winProcEstablishConnection - winInitClipboard returned. >>>> winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP >>>> winInitMultiWindowWM - pthread_mutex_unlock () returned. >>>> winMultiWindowXMsgProc - pthread_mutex_lock () returned. >>>> winClipboardProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - >>>> DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_unlock >>>> () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 >>>> winMultiWindowXMsgProc - XOpenDisplay () returned and successfully >>>> opened the display. winInitMultiWindowWM - XOpenDisplay () returned >>>> and successfully opened the display. winClipboardProc - XOpenDisplay >>>> () returned and successfully opened the display. >>>> winProcSetSelectionOwner - Clipboard not yet started, aborting. >>>> winProcSetSelectionOwner - Clipboard not yet started, aborting. >>>> winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid >>>> parameter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: >>>> BadMatch (invalid parameter attributes) >>>> winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid >>>> parameter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: >>>> BadMatch (invalid parameter attributes) >>>> winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid >>>> parameter attributes) winMultiWindowXMsgProcErrorHandler - ERROR: >>>> BadMatch (invalid parameter attributes) >>>> winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch (invalid >>>> parameter attributes) winClipboardProc - >>>> winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, >>>> exiting main loop. winClipboardProc - XDestroyWindow succeeded. >>>> winMultiWindowXMsgProcIOErrorHandler! winInitMultiWindowXMsgProc - >>>> Caught IO Error. Exiting. FreeFontPath: FPE >>>> "/usr/X11R6/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing. >>>> (II) XF86Config is not supported (II) See >>>> http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information >>>> >>>> Does anyone know what might be causing this problem, and also how to >>>> fix it? >>>> >>>> Thanks, >>>> Jim >>> >>> >>> >>> >>> -- >>> 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/ >> > > > -- > 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/