Re: Xwin.log error
hey chuck, I'll give that a try but I am still wondering what changed. XWin.exe used to be able to determine that another instance was running and just quietly exit. i had the same problem as you and i totally understand why toi run the .bat file each because there are lots of conf settings i would not try to pack in the xterm-link. since i also found no solution for that problem with version 6.?.99, i just downgraded to my previous version 6.?.2. you can do this by running setup and click on the 'Keep' word until there appears version 6.?.2. best, andi -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Xwin.log error
Peter Farley wrote: PMFJI here, but why in the world are you using startxwin.bat a 2nd time to start a 2nd xterm? That was the only icon/xterm-starter installed In all my cygwin-X experience, starting a second xterm is just a matter of using the xterm icon distributed with the other X-server pieces from setup.exe. I think it is an optional install item, so you may have missed it if you only specified the defaults to install. The item is labeled X-start-menu-icons. Once it is installed, go to Start/All Programs/Cygwin-X, there is an xterm icon there you can use to start another xterm. Or you can extract the xterm startup line from startxwin.bat and store it as startxterm.bat. HTH Peter I'll give that a try but I am still wondering what changed. XWin.exe used to be able to determine that another instance was running and just quietly exit. Thanks. Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Xwin.log error
X11 has been working fine on my PC for 2 years. This week I started getting an error message box whenever I try to run startxwin.bat a 2nd time in order to launch a 2nd xterm. The xterm comes up but only after the error message box appears. XWin.log contains this... Fatal server error: Cannot establish any listening sockets - Make sure an X server isn't already running winDeinitMultiWindowWM - Noting shutdown in progress Of course there's another X server running. I'm trying to open a 2nd xterm. Never had a problem doing this until this week though. It's almost like XWin.exe can't determine that another instance of itself is already running. Coincidentally I also installed util-linux this week. Could that have caused this? I know there's an mcookie program that's part of that package. TIA -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Can anyone help with this XWin.log error?
I tried to Google this with no luck! Any help appreciated ... VNC Server is running, but not in use. XWin.log == Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.2.0-4 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: /usr/X11R6/bin/XWin -query 192.168.0.104 -nodecoration -lesspointer ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Cannot create /tmp/.X11-unix with root ownership winCheckDisplayNumber - Cygwin/X is already running on display 0 Fatal server error: InitOutput - Duplicate invocation on display number: 0. Exiting. winDeinitMultiWindowWM - Noting shutdown in progress -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Can anyone help with this XWin.log error?
Alan Guedeney wrote: I tried to Google this with no luck! Any help appreciated ... VNC Server is running, but not in use. XWin.log == Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.2.0-4 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: /usr/X11R6/bin/XWin -query 192.168.0.104 -nodecoration -lesspointer ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Cannot create /tmp/.X11-unix with root ownership winCheckDisplayNumber - Cygwin/X is already running on display 0 Fatal server error: InitOutput - Duplicate invocation on display number: 0. Exiting. Consult the FAQ: http://x.cygwin.com/docs/faq/cygwin-x-faq.html#duplicate-invocation -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Xwin.log question
On Wed, 29 Dec 2004, VandenBosch, Richard wrote: Hey there... When trying to run startxwin.bat or startxwin.sh I get the error below. Any ideas what causes this? Thx RV Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 4.3.0.54 This one is rather old! Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: XWin -multiwindow -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1600 h 1084 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransSocketCreateListener: failed to bind listener _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: failed to create listener for tcp _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Fatal server error: Cannot establish any listening sockets - Make sure an X server isn't already running winDeinitMultiWindowWM - Noting shutdown in progress you either have another XWin or a program which uses port 600 running or this might be a problem with a firewall. Make sure XWin has full access to the network. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Xwin.log question
Xwin.log question
Hey there... When trying to run startxwin.bat or startxwin.sh I get the error below. Any ideas what causes this? Thx RV Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 4.3.0.54 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: XWin -multiwindow -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1600 h 1084 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransSocketCreateListener: failed to bind listener _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: failed to create listener for tcp _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Fatal server error: Cannot establish any listening sockets - Make sure an X server isn't already running winDeinitMultiWindowWM - Noting shutdown in progress
XWin.log
Welcome to the XWin X Server (BVendor: The Cygwin/X Project (BRelease: 4.3.0.67 (BContact: [EMAIL PROTECTED] (B (BXWin was started with the following command line: (B (BX -query 192.168.0.3 (B (BddxProcessArgument - Initializing default screens (BwinInitializeDefaultScreens - w 1024 h 768 (BwinInitializeDefaultScreens - Returning (BOsVendorInit - Creating bogus screen 0 (B_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (BwinValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 (BwinCheckDisplayNumber - Cygwin/X is already running on display 0 (B (BFatal server error: (BInitOutput - Duplicate invocation on display number: 0. Exiting. (B (BwinDeinitMultiWindowWM - Noting shutdown in progress (B (B (BddxBeforeReset - Hello (BwinDetectSupportedEngines - Windows NT/2000/XP (BwinDetectSupportedEngines - DirectDraw installed (BwinDetectSupportedEngines - DirectDraw4 installed (BwinDetectSupportedEngines - Returning, supported engines 0007 (BwinScreenInit - dwWidth: 1018 dwHeight: 715 (BwinSetEngine - Using Shadow DirectDraw NonLocking (BwinCreateBoundingWindowWindowed - User w: 1024 h: 768 (BwinCreateBoundingWindowWindowed - Current w: 1018 h: 715 (BwinAdjustForAutoHide - Original WorkArea: 0 0 740 1024 (BwinAdjustForAutoHide - Adjusted WorkArea: 0 0 740 1024 (BwinCreateBoundingWindowWindowed - WindowClient w 1018 h 715 r 1018 l 0 b 715 (Bt 0 (BwinCreateBoundingWindowWindowed - Returning (BwinCreatePrimarySurfaceShadowDDNL - Creating primary surface (BwinCreatePrimarySurfaceShadowDDNL - Created primary surface (BwinCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface (BwinAllocateFBShadowDDNL - lPitch: 4072 (BwinAllocateFBShadowDDNL - Created shadow pitch: 4072 (BwinAllocateFBShadowDDNL - Created shadow stride: 1018 (BwinFinishScreenInitFB - Masks: 00ff ff00 00ff (BwinInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp (B32 (BwinRandRInit () (BwinCreateDefColormap - Deferring to fbCreateDefColormap () (BwinFinishScreenInitFB - returning (BwinScreenInit - returning (BInitOutput - Returning. (BMIT-SHM extension disabled due to lack of kernel support (BXFree86-Bigfont extension local-client optimization disabled due to lack of (Bshared memory support in the kernel (B(--) Setting autorepeat to delay=500, rate=31
Re: XWin.log
winCheckDisplayNumber - Cygwin/X is already running on display 0 Fatal server error: InitOutput - Duplicate invocation on display number: 0. Exiting. winDeinitMultiWindowWM - Noting shutdown in progress You can't launch two instances on the same display number. Harold
XWin.log: WIBGI ...
Hello list ! As I know you really love WIBGI, I will contribute my ... suggestion ;-) I often have multiple XWin launched at the same time, and if XWin.log could have somewhere in his name the display number, I think that would be much easier to debug ... Thx for your attention, Gael.
Re: XWin.log: WIBGI ...
Yes, it would be great if the log file put the display and screen numbers in each message. However, this wouldn't really fix the problem because there is no synchronization to write to the log file, so you often get messages written on top of each other when you run more than one display or screen. XFree86 CVS currently has a new log file system that Alexander has enabled for Cygwin/XFree86. I don't know if that new system uses display and screen-specific log files or not (I think it should and probably does). So, your request may magically be fixed when XFree86 4.4.0 is released. By the way, 4.4.0 is going to be a very nice upgrade. It has had a lot of new features added that work for all supported platforms, including Cygwin (such as the log feature). So, wait patiently dear user, wait patiently, Harold Gaël Gueguen wrote: Hello list ! As I know you really love WIBGI, I will contribute my ... suggestion ;-) I often have multiple XWin launched at the same time, and if XWin.log could have somewhere in his name the display number, I think that would be much easier to debug ... Thx for your attention, Gael.
How do you turn off XWin.log logging?
I am using XFree86 with Cygwin and the XWin.log file grows to over 6.0 gigabytes in size. The only way to clear it is to exit Cygwin and manually delete the file. How can I prevent Cygwin/Xfree86 from writing the to log file? 6 gigabytes is insanely large for a log file. Thanks, Todd Barron Acxiom Product Development Chenal Building - Little Rock (F013-3106) Phone: (501) 342-4580 Fax: (501) 342-4903 email: [EMAIL PROTECTED] CONFIDENTIALITY NOTICE The information contained in this electronic mail transmission and any of its attachments may contain confidential or legally privileged material. These documents are intended for the sole use of the above named addressee(s). If you or your company is not the intended recipient and you have received this electronic mail message in error, you are notified that copying, reading or disclosing these documents or their contents, or in any way using the information contained in them, is prohibited. If you received this communication in error, please notify me immediately at 501-252-4580, and delete the original message. Thank you. The views or opinions expressed by the sender do not necessarily reflect those of the Acxiom Corporation. They are the views of the sender only and mean nothing more. The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please re-send this communication to the sender and delete the original message or any copy of it from your computer system. Thank You.
Re: How do you turn off XWin.log logging?
On Tue, 3 Sep 2002, Barron Todd - tbarro wrote: I am using XFree86 with Cygwin and the XWin.log file grows to over 6.0 gigabytes in size. The only way to clear it is to exit Cygwin and manually delete the file. How can I prevent Cygwin/Xfree86 from writing the to log file? 6 gigabytes is insanely large for a log file. Modify the source and recompile the Xserver. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
RE: Emailing: XWin.log
Robert, The Windows dump file won't be of any help. However, you could send in /etc/setup/installed.db. That way we know what versions of things you have. There have been several significant Cygwin/XFree86 updates since the 26 of June. I highly advise that you update. Harold Robert Taylor [EMAIL PROTECTED] said: Would the setup.log file help? How about the Windows dump file? My installation was 6/26/2002 from setup.exe via redhat -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 9:40 AM To: [EMAIL PROTECTED]; Robert Taylor; [EMAIL PROTECTED] Subject: Re: Emailing: XWin.log Robert, [For others: this is a followup to a post on ./ where Robert said that Windows XP rebooted when he ran XWin.exe] There doesn't seem to be any error recorded, at all. Try downloading the latest setup.exe (http://cygwin.com/setup.exe) and update your XFree86-xserv package. Make sure that you get version 4.2.0-10. Perhaps this was just a bug in some earlier version. Thanks for the log file, Harold Robert Taylor [EMAIL PROTECTED] said: Harold, I hope this is helpful. Robert J. Taylor
RE: Emailing: XWin.log
Robert, You are running cygwin-1.3.11-3 and XFree86-xserv-4.2.0-7. Please upgrade as I requested by getting the latest Cygwin setup.exe (http://cygwin.com/setup.exe) and running it. It will only upgrade packages that have been updated, so the download will not take long. By the way, are you able to reproduce this reboot-on-launch behavior every time? Have you tried to do this lately? How are you starting Cygwin/XFree86, are you using startxwin.bat (recommended)? Thanks, Harold Robert Taylor [EMAIL PROTECTED] said: Please find the inastalled.db file attached. Thanks for your dircect support--I look forward to being a regular user of cygwin. Robert Taylor, CTO Dispensing Solutions, Inc. [EMAIL PROTECTED] Office: (714)437-0330 ext 119 Mobile: (949)677-3864 -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 9:56 AM To: [EMAIL PROTECTED]; Robert Taylor; Harold L Hunt Cc: [EMAIL PROTECTED] Subject: RE: Emailing: XWin.log Robert, The Windows dump file won't be of any help. However, you could send in /etc/setup/installed.db. That way we know what versions of things you have. There have been several significant Cygwin/XFree86 updates since the 26 of June. I highly advise that you update. Harold Robert Taylor [EMAIL PROTECTED] said: Would the setup.log file help? How about the Windows dump file? My installation was 6/26/2002 from setup.exe via redhat -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 9:40 AM To: [EMAIL PROTECTED]; Robert Taylor; [EMAIL PROTECTED] Subject: Re: Emailing: XWin.log Robert, [For others: this is a followup to a post on ./ where Robert said that Windows XP rebooted when he ran XWin.exe] There doesn't seem to be any error recorded, at all. Try downloading the latest setup.exe (http://cygwin.com/setup.exe) and update your XFree86-xserv package. Make sure that you get version 4.2.0-10. Perhaps this was just a bug in some earlier version. Thanks for the log file, Harold Robert Taylor [EMAIL PROTECTED] said: Harold, I hope this is helpful. Robert J. Taylor
Fwd: RE: Emailing: XWin.log
Looks like we fixed another one :) Harold P.S. Robert - notice that I'm cc'ing [EMAIL PROTECTED] on all replies. Please start doing so in future replies. Forwarded From: Robert Taylor [EMAIL PROTECTED] Just installed the latest setup.exe and asked for all to be installed. It's running fine without rebooting or BSOD'ing. -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 9:56 AM To: [EMAIL PROTECTED]; Robert Taylor; Harold L Hunt Cc: [EMAIL PROTECTED] Subject: RE: Emailing: XWin.log Robert, The Windows dump file won't be of any help. However, you could send in /etc/setup/installed.db. That way we know what versions of things you have. There have been several significant Cygwin/XFree86 updates since the 26 of June. I highly advise that you update. Harold Robert Taylor [EMAIL PROTECTED] said: Would the setup.log file help? How about the Windows dump file? My installation was 6/26/2002 from setup.exe via redhat -Original Message- From: Harold L Hunt [mailto:[EMAIL PROTECTED]] Sent: Monday, July 08, 2002 9:40 AM To: [EMAIL PROTECTED]; Robert Taylor; [EMAIL PROTECTED] Subject: Re: Emailing: XWin.log Robert, [For others: this is a followup to a post on ./ where Robert said that Windows XP rebooted when he ran XWin.exe] There doesn't seem to be any error recorded, at all. Try downloading the latest setup.exe (http://cygwin.com/setup.exe) and update your XFree86-xserv package. Make sure that you get version 4.2.0-10. Perhaps this was just a bug in some earlier version. Thanks for the log file, Harold Robert Taylor [EMAIL PROTECTED] said: Harold, I hope this is helpful. Robert J. Taylor
Thought on /tmp/XWin.log
Just out of curiosity, why was XWin.exe changed to write output to /tmp/XWin.log? I liked the previous behavior of sending it to STDOUT. Seems to me this was more flexible since I could see the output in real time, redirect to a file ( /tmp/XWin.log), or both (| tee /tmp/XWin.log). I also just ran an experiment running 2 instances of XWin with -screen 0 x y and -screen 1 x y arguments. The log file from the first instance get overwritten by the log file from the second. If you don't want to go back to STDOUT, perhaps you could add the screen number somewhere in the logfile name to fix the overwriting problem (e.g. /tmp/XWin.0.log, /tmp/XWin.1.log, etc.)? _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
RE: Thought on /tmp/XWin.log
James, The discussion of why we went to /tmp/XWin.log is in the mailing list archives. The reason was primarily that we wanted to make XWin.exe a GUI application instead of a command-line application... this is necessary to quiet the thousands of questions of why does XWin.exe open a command prompt window when I run it?. There are difficulties in improving the log file system as we don't know what screen numbers will be used when we create the log file. We could send initial messages to XWin.log, then redirect each screen to XWin-screenXX.log, but can you imagine having to tell users Okay, if you have a problem that occurs early in XWin.exe initialization then you need to look at XWin.log... otherwise you need to look at XWin-screenXX.log where XX is the screen that had the problem. Yeah right, we have people that think that a sentence that reads don't use Winzip means that they should use Winzip. Hope that clears things up, Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of James Tetazoo Sent: Monday, April 01, 2002 10:30 AM To: [EMAIL PROTECTED] Subject: Thought on /tmp/XWin.log Just out of curiosity, why was XWin.exe changed to write output to /tmp/XWin.log? I liked the previous behavior of sending it to STDOUT. Seems to me this was more flexible since I could see the output in real time, redirect to a file ( /tmp/XWin.log), or both (| tee /tmp/XWin.log). I also just ran an experiment running 2 instances of XWin with -screen 0 x y and -screen 1 x y arguments. The log file from the first instance get overwritten by the log file from the second. If you don't want to go back to STDOUT, perhaps you could add the screen number somewhere in the logfile name to fix the overwriting problem (e.g. /tmp/XWin.0.log, /tmp/XWin.1.log, etc.)? _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
