Re: Fatal error when starting Cygwin/X v1.15.0-2 built 2014-01-11
On 26/05/2014 16:55, Ralf Oltmanns wrote: I updated to 1.15.1-2 and placed the crash-reporter into cygwin64/bin. A crash report has been submitted to your server. The same problem still persists. Thanks very much. Could you please also install the xorg-server-debuginfo package, remove xorg_cygwin_crash_reporter_gui and show the log you get then? On 05/26/2014 03:32 PM, Jon TURNEY wrote: On 26/05/2014 14:18, Ralf Oltmanns wrote: I just installed cygwin/X on a freshly installed Windows 7 Professional (64bit). When trying to start XWin Server, it crashes with signal 11 (Segmentation fault) My installation is as follows: Release: 1.15.0.0 Package: version 1.15.0-2 built 2014-01-11 Thanks for the bug report. The current XWin version is 1.15.1-2. Perhaps you could try again with that? If that doesn't resolve your problem, I'm afraid that the log doesn't contain enough information for me to identify the cause of the crash. Could you then install the xorg-server-debuginfo package, which enables a more useful backtrace to be generated in the log, and try again? With 1.15.1, I also enabled a tool I have been working to automate sending better crash information using minidumps. If you would like to try that, download it from [1] (anonymous ftp) and put it into /usr/bin and reproduce your crash again. [1] ftp://cygwin.com/pub/cygwinx/x86_64/xorg_cygwin_crash_reporter_gui.exe -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Fatal error when starting Cygwin/X v1.15.0-2 built 2014-01-11
On 26/05/2014 14:18, Ralf Oltmanns wrote: I just installed cygwin/X on a freshly installed Windows 7 Professional (64bit). When trying to start XWin Server, it crashes with signal 11 (Segmentation fault) My installation is as follows: Release: 1.15.0.0 Package: version 1.15.0-2 built 2014-01-11 Thanks for the bug report. The current XWin version is 1.15.1-2. Perhaps you could try again with that? If that doesn't resolve your problem, I'm afraid that the log doesn't contain enough information for me to identify the cause of the crash. Could you then install the xorg-server-debuginfo package, which enables a more useful backtrace to be generated in the log, and try again? With 1.15.1, I also enabled a tool I have been working to automate sending better crash information using minidumps. If you would like to try that, download it from [1] (anonymous ftp) and put it into /usr/bin and reproduce your crash again. [1] ftp://cygwin.com/pub/cygwinx/x86_64/xorg_cygwin_crash_reporter_gui.exe -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Fatal Error (Segmentation Fault) only while viewing the LVM GUI
On 25/04/2012 19:25, Carlo.DiCocco wrote: I think I may have found a bug. I am connecting to a remote Linux server from my Windows desktop and attempting to use some of the GUI tools on the remote server. The xclock GUI displays fine. The Oracle dbca GUI displays fine. The LVM system-config-lvm GUI displays and works fine, but cygwin generates a fatal error window due to a segmentation fault. The following command displays the GUI, but reports a fatal error: [root@aorahdev ~]# system-config-lvm [ 64144.546] Segmentation fault at address 0x44 [ 64144.546] Fatal server error: [ 64144.546] Caught signal 11 (Segmentation fault). Server aborting [ 64144.546] Server terminated with error (1). Closing log file. Thanks for reporting this problem. I was not able to reproduce this crash using system-config-lvm 1.1.16, on Fedora 15. Perhaps you can provide details on the remote server and system-config-lvm version you are using? It would be very helpful if you could follow the instructions at [1] to use gdb to get a backtrace for the X server when it crashes. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Fatal Error (Segmentation Fault) only while viewing the LVM GUI
On 26/04/2012 14:18, Jon TURNEY wrote: On 25/04/2012 19:25, Carlo.DiCocco wrote: I think I may have found a bug. I am connecting to a remote Linux server from my Windows desktop and attempting to use some of the GUI tools on the remote server. The xclock GUI displays fine. The Oracle dbca GUI displays fine. The LVM system-config-lvm GUI displays and works fine, but cygwin generates a fatal error window due to a segmentation fault. The following command displays the GUI, but reports a fatal error: [root@aorahdev ~]# system-config-lvm [ 64144.546] Segmentation fault at address 0x44 [ 64144.546] Fatal server error: [ 64144.546] Caught signal 11 (Segmentation fault). Server aborting [ 64144.546] Server terminated with error (1). Closing log file. Thanks for reporting this problem. I was not able to reproduce this crash using system-config-lvm 1.1.16, on Fedora 15. Perhaps you can provide details on the remote server and system-config-lvm version you are using? It would be very helpful if you could follow the instructions at [1] to use gdb to get a backtrace for the X server when it crashes. Oops [1] http://x.cygwin.com/devel/backtrace.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Fatal Error (Segmentation Fault) only while viewing the LVM GUI
On 26/04/2012 14:23, Jon TURNEY wrote: On 26/04/2012 14:18, Jon TURNEY wrote: On 25/04/2012 19:25, Carlo.DiCocco wrote: I think I may have found a bug. I am connecting to a remote Linux server from my Windows desktop and attempting to use some of the GUI tools on the remote server. The xclock GUI displays fine. The Oracle dbca GUI displays fine. The LVM system-config-lvm GUI displays and works fine, but cygwin generates a fatal error window due to a segmentation fault. The following command displays the GUI, but reports a fatal error: [root@aorahdev ~]# system-config-lvm [ 64144.546] Segmentation fault at address 0x44 [ 64144.546] Fatal server error: [ 64144.546] Caught signal 11 (Segmentation fault). Server aborting [ 64144.546] Server terminated with error (1). Closing log file. Thanks for reporting this problem. I was not able to reproduce this crash using system-config-lvm 1.1.16, on Fedora 15. Perhaps you can provide details on the remote server and system-config-lvm version you are using? It would be very helpful if you could follow the instructions at [1] to use gdb to get a backtrace for the X server when it crashes. Oops [1] http://x.cygwin.com/devel/backtrace.html It seems quite likely this is the same crash as reported at [1], so it's probably worth testing X server 1.12.0-5 to see if it's fixed there, first. [1] http://cygwin.com/ml/cygwin-xfree/2012-04/msg00097.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: fatal error
On 25/06/2010 10:12, Miroslav Iliaš wrote: /var/log/XWin.0.log attached [ 2936.391] (EE) XKB: Could not invoke xkbcomp [ 2936.391] (EE) XKB: Couldn't compile keymap [ 2936.391] XKB: Failed to compile keymap [ 2936.391] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. [ 2936.391] Fatal server error: [ 2936.391] Failed to activate core devices. Can you run /usr/bin/xkbcomp from bash? If no, your installation of xkbcomp is broken somehow. Try 'cycheck /usr/bin/xkbcomp'. If yes, you probably have some kind of BLODA [1] problem. [1] http://cygwin.com/faq/faq.using.html#faq.using.bloda -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Fatal error
On 6/9/2010 1:14 PM, marvin.man...@oracle.com wrote: I get the following fatal error with my windows xp machine. A fatal error has occurred and Cygwin/X will now exit. Please open /tmp/XWin.log for more information. Vendor: The Cygwin/X Project Release: 6.8.99.901-4 Time to upgrade. Go to cygwin.com and click on Install or update Cygwin now! -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: fatal error when starting X-Server
On Sat, May 29, 2010 at 11:42:07AM +0200, David Rockel wrote: Fatal server error: Can't read lock file /tmp/.X0-lock Hello, I would start checking if /tmp has 1777 perms. Regards. -- Huella de clave primaria: 0FDA C36F F110 54F4 D42B D0EB 617D 396C 448B 31EB pgpjn0SsQ9jcb.pgp Description: PGP signature
Re: Fatal error
Fortunately, it works now. Thank you very much anyway. Eva Jon TURNEY jon.tur...@dronecode.org.uk ha escrito: On 08/03/2010 18:31, evgar...@ull.es wrote: my name is Eva García Llorente, I have installed a new version of cygwin (that one which is necessary for installing the latest Singular version (3-1-1)). It is supposed to be installed,but when I try to execute Singular (Emacs and X-server) a fatal error occurs, and in /var/log/Xwinlog is reported the following error: Fatal server error: Can't read lock file /tmp/.X0-lock I have tried these possible solutions (FAQ): 1. startxwin -- -nolock 2. rm -rf /tmp; mkdir /tmp ; chmod 1777 /tmp and they have not worked. Can you attach the log file from running the X server with the additional -nolock option? What about the facts which FAQ 3.4 mentions as relevant? Are you using a FAT filesystem? Does your account have local Administrator privileges? -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Fatal error
On 08/03/2010 18:31, evgar...@ull.es wrote: my name is Eva García Llorente, I have installed a new version of cygwin (that one which is necessary for installing the latest Singular version (3-1-1)). It is supposed to be installed,but when I try to execute Singular (Emacs and X-server) a fatal error occurs, and in /var/log/Xwinlog is reported the following error: Fatal server error: Can't read lock file /tmp/.X0-lock I have tried these possible solutions (FAQ): 1. startxwin -- -nolock 2. rm -rf /tmp; mkdir /tmp ; chmod 1777 /tmp and they have not worked. Can you attach the log file from running the X server with the additional -nolock option? What about the facts which FAQ 3.4 mentions as relevant? Are you using a FAT filesystem? Does your account have local Administrator privileges? -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Fatal Error Occurred
On Sat, 12 Sep 2009, Alicia Muirhead wrote: A fatal error has occurred and Cygwin/X will now exit. Please open /tmp/XWin.log for more information. Release: 6.8.99.901-4 XWin was started with the following command-line: /usr/X11R6/bin/XWin-multiwindow -clipboard -silent-dup-error' I cannot open /tmp/XWin.log. Try looking in /var/log -- 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: Fatal error
On 09/09/2009 23:21, Tanja Kjallman wrote: Fatal error, open /var/log.xwin.0.log, Xwin was started with the following command-line: Xwin -mulitiwindow -clipboard ^ XWin isn't very forgiving about misspellings. Yaakov Cygwin/X -- 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: Fatal Error -Cannot establish listening sockets - when starting X server using startx
On 14/08/2009 08:38, rk ka wrote: I installed Cygwin/X with the latest setup.exe. When i run startx I get a fatal error. Please check the attached Xwin log for details. There is no other instance of X server running. I've also included the output of cygcheck -s -v -r in cygcheck.out. Try something like 'netstat -a -b -n | grep -A2 :6000' which should identify any process which is already bound to the socket which the X server wants to use. You should also read your cygcheck output, which includes: Potential app conflicts: ZoneAlarm Personal Firewall Detected: HKLM Registry Key, Named file. So you should also consider the possibilities that this is either configured to cause the X server to fail this way, or it causing random failures [2] Please can someone tell me how I can fix this? I could not find analogous issues in the mailing list for this. I wonder why you did not find [1] [1] http://cygwin.com/ml/cygwin-xfree/2009-05/msg8.html [2] http://cygwin.com/faq/faq.using.html#faq.using.bloda -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Fatal Error -Cannot establish listening sockets - when starting X server using startx
Thanks Jon for the reply. I noticed [1] but did not go beyond reading the subject cuz it read Vista. Sorry. Cheers. 2009/8/14 Jon TURNEY jon.tur...@dronecode.org.uk: On 14/08/2009 08:38, rk ka wrote: I installed Cygwin/X with the latest setup.exe. When i run startx I get a fatal error. Please check the attached Xwin log for details. There is no other instance of X server running. I've also included the output of cygcheck -s -v -r in cygcheck.out. Try something like 'netstat -a -b -n | grep -A2 :6000' which should identify any process which is already bound to the socket which the X server wants to use. You should also read your cygcheck output, which includes: Potential app conflicts: ZoneAlarm Personal Firewall Detected: HKLM Registry Key, Named file. So you should also consider the possibilities that this is either configured to cause the X server to fail this way, or it causing random failures [2] Please can someone tell me how I can fix this? I could not find analogous issues in the mailing list for this. I wonder why you did not find [1] [1] http://cygwin.com/ml/cygwin-xfree/2009-05/msg8.html [2] http://cygwin.com/faq/faq.using.html#faq.using.bloda -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Fatal Error on start up
Nadia Dimitrova wrote: Dear Cygwin, One copy of a request is more than enough BTW. I am trying to install FontForge on my Windows Vista laptop and I need Cygwin shell to run it. To set environmental variables they suggest I run a BAT file. It looks like it succeeds with the variables but it cannot execute XWin at the end. Could you please help me figure out what is wrong with my Cygwin installation. I get a message snip Fatal server error: could not open default font 'fixed' winDeinitMultiWindowWM - Noting shutdown in progress -- See starxwin.BAT file at the end of this message. I appreciate your help. See the FAQ entry: http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-error-font-eof -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 429-6305 - 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: fatal error
Carlos Moran Tejeda wrote: Dear Cygwin staff: Im a new user of Cygwin. I was trying to run Grass under Cygwin but when I type startx in the comand console a fatal error occurs. The description is snip Fatal server error: could not open default font 'fixed' Please, could you let me know how to fix it? Have you looked in the Cygwin-X FAQ? Here's one hit that seems relevant: http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-error-font-eof Other troubleshooting entries may prove helpful to you as well. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 429-6305 - 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: fatal error
Carlos Moran Tejeda wrote on Tuesday, February 05, 2008 2:55 PM:: Fatal server error: could not open default font 'fixed' Please, could you let me know how to fix it? Try looking in the FAQ - there's a link to it at the bottom of every message on the list. This is almost always caused by choosing to install for DOS style text files. If this is what you did, be advised that this causes all sorts of other problems, so if you've only just installed cygwin, I'd recommend deleting your cygwin installation directory and reinstalling from scratch. -- 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: Fatal Error with Cygwin usage
On 11/7/06, Himanshu wrote: A fatal error has occured and Cygwin/X will now exit. Please open /tmp.XWin.log for more imformation. Without posting the entire contents of /tmp.XWin.log, can you tell the group if you found anything useful there, such as what is the actual error is being caused by? Thank you, -Jason -- 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: Fatal Error with Cygwin usage
Did you read any of the on-line documentation? -- 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: fatal error with X Server 6.8.99.901-1
Apologies for the long lines in my previous message. Haven't figured out yet how to control Outlook. (Suggestions welcome.) --Ken Nellis -- 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: fatal error with X Server 6.8.99.901-1
On Mon, Jul 17, 2006 at 10:20:09AM -0400, Kenneth Nellis wrote: Apologies for the long lines in my previous message. Haven't figured out yet how to control Outlook. (Suggestions welcome.) But suggestions do not go here. 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/
Re: fatal error -- Cygwin/X Project 6.8.2.0-4
On Tue, 7 Feb 2006, Yitwah Cheung wrote: This is a bug-report. [snip] Fatal server error - Duplicate invocation on display number: 0. Exiting. Not a bug: http://x.cygwin.com/docs/faq/cygwin-x-faq.html#duplicate-invocation. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ [EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-'old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte. But no -- you are no fool; you call yourself a fool, there's proof enough in that! -- Rostand, Cyrano de Bergerac -- 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: fatal error occurred. my mozilla installation failed. what to do?
First, I just have to cite Heinlein: When in danger, or in doubt -- Run in circles, scream, and shout. Then I'd like to cite the Cygwin problem reporting page at http://cygwin.com/problems.html, which has some useful hints on how to report problems properly. For Cygwin/X crashes, it's usually also useful to provide XWin.log. Besides the above, lacking the details of the error, it's quite impossible to help you. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. /DA -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: fatal error in running startx (after installing KDE)
On Fri, 15 Apr 2005, Darwin P Sigumonrong wrote: Fatal server error: CAnnot open log file /tmp/XWin.log I have to add that i installed my Cygwin and KDE3 on Windows XP under admin login The strange thing (at least for me) is that the KDE can run when I log in as admin but when I login using another login user name, the KDE won't work make sure any use can write to c:\cygwin\tmp bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: Fatal error while trying to use X11 in Cygwin...
On Thu, 14 Oct 2004, Philippe Wang wrote: Hello, I have just installed Cygwin and it works for what I really need to do. However, when I want to try X11 with the command x, a fatal error occurs. Could you help me please? Check the archives. I've already sent an answer which got blocked by your spam filter. Seems the multiple exclamation marks in your old subject made it upset. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: Fatal error while trying to use X11 in Cygwin... Please help me! Thank you!
Philippe Wang wrote: Fatal server error: could not open default font 'fixed' Can you please try running font-update. What does it output? bye ago NP: NamNamBulu - Forgiving (Transformation Mix) -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: Fatal Error found in cygwin/X
On Tue, 5 Oct 2004, Sundar G wrote: Dear, When I executed the command /usr/X11R6/bin/XWin.exe it gave me A fatal error is occured and Cygwin /X will now exit I want to excute the command XWin.exe -query IP Address of Linux Server . Please help me What does /tmp/XWin.log tell? bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: Fatal Error while starting XWin
vamsi vadhri wrote: Fatal server error: InitOutput - Duplicate invocation on display number: 0. Exiting. Are you running Cygwin/X on a terminal server or any other system where more than one user can be logged on? Then most likely another user has already started XWin. To be able to start XWin when another user is already running it, change the startup in startxwin.bat from XWin some options to XWin :1 same options and adjust the string for display accordingly (from :0.0 to :1.0). HTH ago NP: Atrocity - Cold Black Days (Das Ich Remix) -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: Fatal Error while starting XWin
On Wed, 9 Jun 2004, Alexander Gottwald wrote: vamsi vadhri wrote: Fatal server error: InitOutput - Duplicate invocation on display number: 0. Exiting. Are you running Cygwin/X on a terminal server or any other system where more than one user can be logged on? Then most likely another user has already started XWin. To be able to start XWin when another user is already running it, change the startup in startxwin.bat from XWin some options to XWin :1 same options and adjust the string for display accordingly (from :0.0 to :1.0). Or, if you won't ever need to share the Cygwin /tmp directory with the other users, simply create a user-level /tmp mount that points to a user-specific directory, e.g. 'mount -u $USERPROFILE/Local Settings/Temp /tmp'... HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
Re: fatal error
Oleg, Something is weird with your Xdmcp server on the Linux machine. Which *dm are you using (e.g. gdm, kdm, xdm, etc.)? Check /var/log/messages for some output from whichever *dm you are using, it should give us some useful information. Harold Oleg wrote: Dear support team, Cygwin is installed on the new machine (Pentium III 533, 384Mb). It works perfect on the previous computer (Pentium 4 2400, 256Mb) but on this machine shows fatal error, when I start startxwin.bat with the line: XWin -query morpheus.tran.wau.nl (Linux Debian server) XWin.log file is attached. Please help to get it working right, thank you very much Oleg, Wageningen University, The Netherlands.
