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/
Fatal error when starting Cygwin/X v1.15.0-2 built 2014-01-11
To whom it may concern, 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 XWin was started with the following command-line: X :0 -multiwindow Please find attached the XWin.0.log. Kind regards Ralf Oltmanns Systems Adminstrator financial.com AG Munich Head Office/Hauptsitz München: Georg-Muche-Straße 3 | 80807 Munich | Germany | Tel. +49 89 318528-0 | Google Maps: http://goo.gl/maps/UHwj9 Frankfurt Branch Office/Niederlassung Frankfurt: Messeturm | Friedrich-Ebert-Anlage 49 | 60327 Frankfurt am Main | Germany | Google Maps: http://goo.gl/maps/oSGjR Management Board/Vorstand: Dr. Steffen Boehnert | Dr. Alexis Eisenhofer | Dr. Yann Samson Supervisory Board/Aufsichtsrat: Rolf Richter (Chairman/Vorsitzender) Register Court/Handelsregister: Munich – HRB 128972 | Sales Tax ID Number/St.Nr.: DE205370553 XWin.0.log Description: XWin.0.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 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/
Fatal Error (Segmentation Fault) only while viewing the LVM GUI
Thank you for your prompt response. I was out yesterday, so I didn't get your email until now. I did an update and the issue no longer exists. Thanks, Carlo L. DiCocco -- 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/
xlogo crahes XWin with Fatal Error (Segmentation Fault)
Dear sirs, Some days ago I updated the cygwin system by 'setup.exe', expecting some GL problems are fixed. Since then XWin crashes with some application programs. One of the most simplest is 'xlogo'. What I have done is as follows; Start [XWin Server] (wait some time for bringing up xterm), then enter 'xlogo' in xterm, [Cygwin/X] window appears immediately. It says, A fatal error ... Caught signal 11 (Segmentation fault). ... Please open /var/log/xwin/XWin.0.log ... Vendor: .. Release: 1.12.0.0 Contact: .. Package: version 1.12.0-4 built 2012-04-17 XWin was started ... X :0 -multiwindow /var/log/xwin/XWin.0.log does not report anything important at all. OK, I tried 'X :0 -multiwindow' on one terminal, and on the other terminal $ export DISPLAY=:0.0 $ xlogo then, the message appears on one therminal; Segmentation fault at address 0x44 Fatal server error: Caught signal 11 (Segmentation fault). Server aborting Server terminated with error (1). Closing log file. winDeinitMultiWindowWM - Noting shutdown in progress winMsgWindowProc - pthread_mutex_unlock () failed: 1 while entering 'X :0' on one terminal, entring 'xlogo' on the other, there was no fatal problem. Obviously '-multiwindow' does something wrong. Keith Lindsay's post might be helpfull as workaround, but I cannot rollback to the 'version 1.12.0-1 of xorg-server (built 2012-03-12)' using 'setup.exe', April 25, 2012 21:45 Re: X segmentation fault when particular application attempts to open a window http://cygwin.com/ml/cygwin-xfree/2012-04/msg00100.html best regards, Yusuke Tamura --- -- 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: xlogo crashes XWin with Fatal Error (Segmentation Fault)
Re: xlogo crashes XWin with Fatal Error (Segmentation Fault) 2012.04.26.18:13:33 UT Hey cygwin-x folks, I have not had notable difficulties with XWin-1.12.0-4. Just about everything that I have done with it over the past few days has been fine. However, when I read Yusuke's post, I thought that I should try one of those old-timey X-programs to see whether it would crash. I've been able to reproduce an XWin crash similar to the one experienced by Yusuke. My XWin did _not_ fail when I was running octave with either the fltk or its usual gnuplot backends. I was also able to run xfig with no problem. This was a crash caused when I opened the xcalc program. I'm not certain that I understand his experiment with two terminal windows as a method of narrowing the difficulty to the -multiwindow option. However like Yusuke, I am starting XWin with the -mulitwindow option. The crash I observed was with just a single xterm, and then the xcalc program. Other programs that opened x-windows seemed fine. In this instance, I had the debugging symbols available, and collected information from a backtrace using (gdb). I've attached gdb.xwin.20120426.txt and my XWin.0.20120426.log. I did not see anything interesting in the xwin0-log, and my (gdb) backtrace is just the output from my glance at Jon Turney's recipe. I'm tossing it in this list in case it helps better-informed folks to track down the difficulty with XWin-1.12.0-4. If there is more specific or nuanced stuff that I can log with (gdb) to provide more information, please e-mail me. George gbarrick_at_walsh_dot_edu Continuing. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 2528.0xf34] 0x0040a41e in winXIconToHICON (pDisplay=0x20279a30, id=10485779, iconSize=optimized out) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c:535 535 /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c: No such file or directory. in /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c #0 0x0040a41e in winXIconToHICON (pDisplay=0x20279a30, id=10485779, iconSize=optimized out) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c:535 root = error reading variable root (Cannot access memory at address 0x7fdfcbf8) y = error reading variable y (Cannot access memory at address 0x7fdfcbf0) depth = error reading variable depth (Cannot access memory at address 0x7fdfcbe0) xImageIcon = 0x0 x = error reading variable x (Cannot access memory at address 0x7fdfcbf4) width = error reading variable width (Cannot access memory at address 0x7fdfcbec) height = error reading variable height (Cannot access memory at address 0x7fdfcbe8) border_width = error reading variable border_width (Cannot access memory at address 0x7fdfcbe4) xImageMask = 0x0 mask = optimized out image = optimized out imageMask = optimized out dst = optimized out src = optimized out planes = 1 bpp = 32 i = optimized out biggest_size = optimized out hDC = optimized out ii = error reading variable ii (Cannot access memory at address 0x7fdfcbcc) hints = 0x203ae1e8 hIcon = 0x0 biggest_icon = optimized out _XA_NET_WM_ICON = error reading variable _XA_NET_WM_ICON (Cannot access memory at address 0x5fd554) generation = error reading variable generation (Cannot access memory at address 0x5fd550) icon = optimized out icon_data = 0x0 size = 0 type = 0 format = 0 left = error reading variable left (Cannot access memory at address 0x7fdfcbfc) #1 0x0040a6ab in winUpdateIcon ( hWnd=error reading variable: Cannot access memory at address 0x7fdfcc70, hWnd@entry=error reading variable: Cannot access memory at address 0x7fdfcc6c, pDisplay=error reading variable: Cannot access memory at address 0x7fdfcc74, id=error reading variable: Cannot access memory at address 0x7fdfcc78, hIconNew=error reading variable: Cannot access memory at address 0x7fdfcc7c) at /opt/wip/cygport-git/xorg-server/xorg-server-1.12.0-4/src/xserver-cygwin-1.12.0-4/hw/xwin/winmultiwindowicons.c:560 hIcon = optimized out hIconSmall = 0x0 hIconOld = optimized out A debugging session is active. Inferior 1 [process 2528] will be detached. Quit anyway? (y or n) error return /netrel/src/gdb-7.3.50-3/gdb/windows-nat.c:1251 was 31 Quitting: Can't detach process 2528 (error 5) XWin.0.20120426.log Description: XWin.0.20120426.log -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem
Fatal Error (Segmentation Fault) only while viewing the LVM GUI
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. Please see below: airs0cld@2UA0070JZB ~ $ ssh -Y root@aorahdev root@aorahdev's password: Warning: No xauth data; using fake authentication data for X11 forwarding. Last login: Wed Apr 25 14:04:58 2012 from 2ua0070jzb.nysdoi.int The following command displays the GUI without any issue: [root@aorahdev ~]# xclock The following command displays the GUI without any issue: [root@aorahdev ~]# . oraenv ORACLE_SID = [root] ? oradshr [root@aorahdev ~]# dbca Warning: Cannot convert string -bh-lucida-medium-r-normal-sans-*-140-*-*-p-*-iso8859-1 to type FontStruct The following command displays the GUI, but reports a fatal error: [root@aorahdev ~]# system-config-lvm The contents of the XWin.0.log file are as follows: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.12.0.0 OS: Windows XP Service Pack 3 [Windows NT 5.1 build 2600] (Win32) Package: version 1.12.0-4 built 2012-04-17 XWin was started with the following command line: X :0 -multiwindow ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1680 h 1050 winInitializeScreenDefaults - native DPI x 96 y 96 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/2UA0070JZB:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 [ 64084.203] (II) xorg.conf is not supported (II) xorg.conf is not supported [ 64084.203] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [ 64084.203] LoadPreferences: /home/airs0cld/.XWinrc not found LoadPreferences: /home/airs0cld/.XWinrc not found [ 64084.203] LoadPreferences: Loading /etc/X11/system.XWinrc LoadPreferences: Loading /etc/X11/system.XWinrc [ 64084.203] LoadPreferences: Done parsing the configuration file... LoadPreferences: Done parsing the configuration file... [ 64084.203] winDetectSupportedEngines - DirectDraw installed, allowing ShadowDD winDetectSupportedEngines - DirectDraw installed, allowing ShadowDD [ 64084.203] winDetectSupportedEngines - Windows NT, allowing PrimaryDD winDetectSupportedEngines - Windows NT, allowing PrimaryDD [ 64084.203] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL [ 64084.203] winDetectSupportedEngines - Returning, supported engines 001f winDetectSupportedEngines - Returning, supported engines 001f [ 64084.203] winTaskbarInit - Could not get SHGetPropertyStoreForWindow address winTaskbarInit - Could not get SHGetPropertyStoreForWindow address [ 64084.203] winSetEngine - Multi Window or Rootless = ShadowGDI winSetEngine - Multi Window or Rootless = ShadowGDI [ 64084.203] winScreenInit - Using Windows display depth of 32 bits per pixel winScreenInit - Using Windows display depth of 32 bits per pixel [ 64084.218] winAllocateFBShadowGDI - Creating DIB with width: 1680 height: 1050 depth: 32 winAllocateFBShadowGDI - Creating DIB with width: 1680 height: 1050 depth: 32 [ 64084.218] winFinishScreenInitFB - Masks: 00ff ff00 00ff winFinishScreenInitFB - Masks: 00ff ff00 00ff [ 64084.218] winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 [ 64084.218] winInitMultiWindowWM - Calling pthread_mutex_lock () winInitMultiWindowWM - Calling pthread_mutex_lock () [ 64084.218] winMultiWindowXMsgProc - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Calling pthread_mutex_lock () [ 64084.218] MIT-SHM extension disabled due to lack of kernel support MIT-SHM extension disabled due to lack of kernel support [ 64084.218] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [ 64084.250] GL_VERSION: 1.5.0 - Build 7.14.10.4964 GL_VERSION: 1.5.0 - Build 7.14.10.4964 [ 64084.250] GL_VENDOR: Intel GL_VENDOR: Intel [ 64084.250] GL_RENDERER:Intel Eaglelake GL_RENDERER:Intel Eaglelake [ 64084.250] GL_EXTENSIONS: GL_ARB_depth_textureGL_EXTENSIONS: GL_ARB_depth_texture GL_ARB_fragment_programGL_ARB_fragment_program GL_ARB_multitextureGL_ARB_multitexture GL_ARB_occlusion_queryGL_ARB_occlusion_query [ 64084.250] GL_EXTENSIONS: GL_EXTENSIONS: GL_ARB_point_parametersGL_ARB_point_parameters GL_ARB_shadowGL_ARB_shadow
Cygwin/X server start up fatal error - failed to compile keymap
Haven't used Cygwin/X for some time. Now when I start it (either with startxwin.exe, XWin.exe, startx etc), I always get a fatal error: A fatal error has occurred and Cygwin/X will now exit. Failed to activate core devices. The /var/log/XWin.0.log contains the following EE messages: [143394.171] (EE) Error compiling keymap (server-0) [143394.171] (EE) XKB: Couldn't compile keymap [143394.171] XKB: Failed to compile keymap [143394.171] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. [143394.171] Fatal server error: [143394.171] Failed to activate core devices. Searched the web and found some similar problems other people had. But no solutions work for me. Tried: rebaseall, reinstall xkeyboard-config, reinstall bash, make sure /bin/sh exists, xkbcomp exists, /usr/share/X11/xkb/rules exists. Nothing works. versions: cygwin 1.7.7-1 xorg-server 1.8.2-1 xkeyboard-config 1.9-1 What should I do to solve this or how to further investigate it? Please help. Thanks Kyle -- 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/
fatal error
/var/log/XWin.0.log attached -- RNDr. Miroslav Iliaš, PhD. Katedra chémie Fakulta prírodných vied Univerzita Mateja Bela Tajovského 40 97400 Banská Bystrica tel: +421 48 446 7351 email : il...@fpv.umb.sk Department of Chemistry Faculty of Natural Sciences Matej Bel University Tajovského 40 97400 Banska Bystrica Slovakia tel: +421 48 446 7351 email : il...@fpv.umb.sk This message was sent using IMP, the Internet Messaging Program. Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.8.0.0 (1080) Build Date: 2010-04-02 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: X :0 -multiwindow ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - primary monitor w 1366 h 768 winInitializeDefaultScreens - native DPI x 96 y 96 winInitializeDefaultScreens - Returning [ 2935.923] winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 [ 2935.923] (II) xorg.conf is not supported [ 2935.923] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [ 2935.923] LoadPreferences: /home/dv6-2145ec/.XWinrc not found [ 2935.923] LoadPreferences: Loading /etc/X11/system.XWinrc [ 2935.923] LoadPreferences: Done parsing the configuration file... [ 2935.923] winGetDisplay: DISPLAY=:0.0 [ 2935.923] winDetectSupportedEngines - Windows NT/2000/XP [ 2935.954] winDetectSupportedEngines - DirectDraw installed [ 2935.954] winDetectSupportedEngines - DirectDraw4 installed [ 2935.954] winDetectSupportedEngines - Returning, supported engines 0007 [ 2935.954] winSetEngine - Multi Window or Rootless = ShadowGDI [ 2935.954] winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel [ 2935.970] winAllocateFBShadowGDI - Creating DIB with width: 1366 height: 768 depth: 32 [ 2935.970] winFinishScreenInitFB - Masks: 00ff ff00 00ff [ 2935.970] winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 [ 2935.970] null screen fn ReparentWindow [ 2935.970] null screen fn RestackWindow [ 2935.970] InitQueue - Calling pthread_mutex_init [ 2935.970] InitQueue - pthread_mutex_init returned [ 2935.970] InitQueue - Calling pthread_cond_init [ 2935.970] InitQueue - pthread_cond_init returned [ 2935.970] winInitMultiWindowWM - Hello [ 2935.970] winInitMultiWindowWM - Calling pthread_mutex_lock () [ 2935.970] winMultiWindowXMsgProc - Hello [ 2935.970] Screen 0 added at virtual desktop coordinate (0,0). [ 2935.970] winMultiWindowXMsgProc - Calling pthread_mutex_lock () [ 2935.985] MIT-SHM extension disabled due to lack of kernel support [ 2935.985] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [ 2936.126] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so [ 2936.126] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [ 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. -- 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/
Fatal error
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 Contact: cygwin-xfree@cygwin.com XWin has started with the following command-line: /usr/X11R6/bin/XWin -multiwindow -clipboard -silent-dup-error Regards, Marvin -- 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/
fatal error when starting X-Server
Hi, I installed Cygwin and the XWin-Server on my PC. When trying to start the XWin Server I received the following message: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.8.0.0 (1080) Build Date: 2010-04-02 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: X :0 -multiwindow ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - primary monitor w 1280 h 800 winInitializeDefaultScreens - native DPI x 96 y 96 winInitializeDefaultScreens - Returning Fatal server error: Can't read lock file /tmp/.X0-lock I would be very pleased if you can provide a solution for this problem. Thank you very much! Regards Dave -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- 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: Incorrect Cygwin/X behavior leads to .X0-lock related fatal error
On 12/03/2010 02:31, Ken Klein wrote: Here is tool behavior that seems like a bug in 1.7.1 related to the Cygwin/X FAQ item 3.4 (A2)called Fatal server error: Can't read lock file /tmp/.X0-lock. I am posting this, because the faq item states that the buggy behavior happens For reasons which are not well understood at present. This post presents what I consider to be incorrect behavior that leads to this error. If I log on as a user without admin rights (on Windows XP), and I start Cygwin/X using the XWin Server program shortcut, the referenced lock file gets created and gives me read/write access. The Everyone user just has read access. When I then close my XWin session, the lock file remains. I log out of Windows, then someone else logs on (also without admin rights), and they get the fatal error as described in the FAQ item, since they do not have write access to the lock file. If, however, I had originally started Cygwin/X by opening a Cygwin window then entering startx, when I eventually end my Cygwin session, the lock file gets deleted. So in this scenario, the next person to log on will not get the fatal error, since Cygwin didn't leave the lock file behind. My opinion is that the startx scenario behaves correctly, and the XWin Server shortcut scenario presents a bug, namely, it leaves behind the lock file after the session is ended. Thanks for the detailed bug report. In fact that FAQ is slightly out of date and we do now understand that the problem is shown when running XWin as both Administrator and non-Adminstrator users as you describe. I'm not able to reproduce the difference in behaviour you describe (of leaving the log file behind) between running startx (which then starts XWin) and directly starting XWin when running as a non-administrator user. Can you be specific about how you are exiting XWin which causes it to leave the lock file behind? This shouldn't happen, and is the cause of the problem. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Incorrect Cygwin/X behavior leads to .X0-lock related fatal error
Here is tool behavior that seems like a bug in 1.7.1 related to the Cygwin/X FAQ item 3.4 (A2)called Fatal server error: Can't read lock file /tmp/.X0-lock. I am posting this, because the faq item states that the buggy behavior happens For reasons which are not well understood at present. This post presents what I consider to be incorrect behavior that leads to this error. If I log on as a user without admin rights (on Windows XP), and I start Cygwin/X using the XWin Server program shortcut, the referenced lock file gets created and gives me read/write access. The Everyone user just has read access. When I then close my XWin session, the lock file remains. I log out of Windows, then someone else logs on (also without admin rights), and they get the fatal error as described in the FAQ item, since they do not have write access to the lock file. If, however, I had originally started Cygwin/X by opening a Cygwin window then entering startx, when I eventually end my Cygwin session, the lock file gets deleted. So in this scenario, the next person to log on will not get the fatal error, since Cygwin didn't leave the lock file behind. My opinion is that the startx scenario behaves correctly, and the XWin Server shortcut scenario presents a bug, namely, it leaves behind the lock file after the session is ended. -- 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
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/
Fatal error
Hello, 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: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.5.0 (10705000) Build Date: 2010-02-25 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: xwin -multiwindow -clipboard -silent-dup-error ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 800 winInitializeDefaultScreens - Returning 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. I hope you can help me. Thanks in advance!! -- 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/
xinit-1.2.0-2 and Xwin Fatal error (xorg-server1.7.3-1)
Hi there, I'm running cygwin 1.7.1. I entered xinit and it brought up the x server and the xterm. I then entered exit on the xterm to terminate the xterm. I got Xwin Fatal error. The last few messages in Xwin.0.log are as follows: 2009-12-30 12:45:31 DetectUnicodeSupport - Windows NT/2000/XP 2009-12-30 12:45:31 winGetDisplay: DISPLAY=:0.0 2009-12-30 12:45:31 winClipboardProc - DISPLAY=:0.0 2009-12-30 12:45:31 winClipboardProc - XOpenDisplay () returned and successfully opened the display. 2009-12-30 12:45:37 winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. 2009-12-30 12:45:37 winClipboardProc - XDestroyWindow succeeded. 2009-12-30 12:45:37 Segmentation fault at address 0x268 2009-12-30 12:45:37 Fatal server error: 2009-12-30 12:45:37 Caught signal 11 (Segmentation fault). Server aborting Does anyone gets the similar messages? Thanks. -- 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: xinit-1.2.0-2 and Xwin Fatal error (xorg-server1.7.3-1)
On 30/12/2009 13:57, ERIC HO wrote: Hi there, I'm running cygwin 1.7.1. I entered xinit and it brought up the x server and the xterm. I then entered exit on the xterm to terminate the xterm. I got Xwin Fatal error. Problem reports: http://cygwin.com/problems.html ^^^ 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/
Fwd: xinit-1.2.0-2 and Xwin Fatal error (xorg-server1.7.3-1)
terminfo05.5_20061104-11 texinfo 4.13-3 tzcode 2009k-1 util-linux 2.14.1-1 vim 7.2.264-1 w32api 3.14-1 which2.20-2 xauth1.0.4-1 xcursor-themes 1.0.2-1 xinit1.2.0-2 xkbcomp 1.1.1-1 xkeyboard-config 1.7-1 xmodmap 1.0.4-1 xorg-server 1.7.3-1 xrdb 1.0.6-1 xterm251-1 zlib 1.2.3-10 zlib-devel 1.2.3-10 zlib01.2.3-10 Use -h to see help about each section XWin.0.log Description: Binary data ---BeginMessage--- Hi there, I'm running cygwin 1.7.1. I entered xinit and it brought up the x server and the xterm. I then entered exit on the xterm to terminate the xterm. I got Xwin Fatal error. The last few messages in Xwin.0.log are as follows: 2009-12-30 12:45:31 DetectUnicodeSupport - Windows NT/2000/XP 2009-12-30 12:45:31 winGetDisplay: DISPLAY=:0.0 2009-12-30 12:45:31 winClipboardProc - DISPLAY=:0.0 2009-12-30 12:45:31 winClipboardProc - XOpenDisplay () returned and successfully opened the display. 2009-12-30 12:45:37 winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. 2009-12-30 12:45:37 winClipboardProc - XDestroyWindow succeeded. 2009-12-30 12:45:37 Segmentation fault at address 0x268 2009-12-30 12:45:37 Fatal server error: 2009-12-30 12:45:37 Caught signal 11 (Segmentation fault). Server aborting Does anyone gets the similar messages? Thanks. ---End Message--- -- 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/
Fatal Error Occurred
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. -- 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/
Fatal error
Hello, I have just downloaded Cygwin to do some modelling of some of my research results. I've also installed the X server, Version 1.5.3 (20090222). When I run the X W it gives me the following error message: Fatal error, open /var/log.xwin.0.log, Xwin was started with the following command-line: Xwin -mulitiwindow -clipboard The program still performs the modelling I need, but I just wanted to ask what I can do to fix the error that being reported. I am not very familiar with the Unix environment, but should be able to fix this with some advice. I've refrained from just trying myself because I can still use it for my main purpose and I don't want to mess that up. Thank you in advance, Tanja -- Tanja Kjällman Doctoral Student Polymer Electronics Research Center Chemistry Department, 5th floor The University of Auckland 23 Symonds Street Auckland 1004 New Zealand Email: tkja...@aucklanduni.ac.nz Ph: (mobile) +64 21 2362424 -- 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: Cygwin/X fatal error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 kra...@msu.edu wrote: Hello. This evening I updated some files for cygwin, which I run on my Windows XP machine. When I try to re-open my X-window, I now get the error message: http://x.cygwin.com/docs/faq/cygwin-x-faq.html#modular Yaakov Cygwin/X -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkliKA8ACgkQpiWmPGlmQSN7uQCgwu1lyMpgo4xN3s7F6CbWVGTo Wz8An0KyVybrqllFRHRDwCtC4V+WvyU3 =nBtz -END PGP SIGNATURE- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Cygwin/X fatal error
Hello. This evening I updated some files for cygwin, which I run on my Windows XP machine. When I try to re-open my X-window, I now get the error message: 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 Contact: cygwin-xfree@cygwin.com XWin was startedwith the following command-line: XWin -clipboard -silent-dup-error When I look in the XWin.log file, I see the message below. I have tried looking at your website, but so far haven't figured out a fix. Can you tell me what I might have done wrong? The file rgb is definitely no longer in that directory, but I don't know how to get it. Couldn't open RGB_DB '/usr/X11R6/lib/X11/rgb' _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. (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 error opening security policy file /usr/X11R6/lib/X11/xserver/SecurityPolicy XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap (--) 3 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/75dpi/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! Fatal server error: could not open default font 'fixed' -- 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 6.8.99.901-1: fatal error on vista x64
I must agree with it. Xwin can't work under vista x64. You can see my previous email as Cygwin and vista 64 bit -- 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/
Fatal Error on start up
Dear Cygwin, 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 Here is the content of XWin.log - Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.99.901-4 Contact: cygwin-xfree@cygwin.com (WW) /tmp mounted int textmode _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root XWin was started with the following command line: /usr/X11R6/bin/xwin (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winCreateBoundingWindowWindowed - Setting normal windowstyle MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 (--) 16 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! 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. Regards, Nadia - rem @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 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
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/
Fatal Error Message
First off, Thank you Thank you Thank you. Ok... So here is what I have. I open Cygwin. Type StartX And I get this error code... 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 Xwin was started with the following command-line X :0 -multiwindow -clipboard Here is what the XWin.log Contains: ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 800 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (EE) Unable to locate/open config file InitOutput - Error reading config file winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 001f InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 800 winCreateBoundingWindowWindowed - Current w: 1280 h: 800 winAdjustForAutoHide - Original WorkArea: 0 0 800 1280 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found BOTTOM auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 0 799 1280 winCreateBoundingWindowWindowed - WindowClient w 1274 h 771 r 1274 l 0 b 771 t 0 winCreateBoundingWindowWindowed - Returning winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Created primary surface winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface winAllocateFBShadowDDNL - lPitch: 5096 winAllocateFBShadowDDNL - Created shadow pitch: 5096 winAllocateFBShadowDDNL - Created shadow stride: 1274 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = xfree86 Model = pc101 Layout = us Variant = (null) Options = (null) Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! winPointerWarpCursor - Discarding first warp: 637 385 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned I have reinstalled the program, it did not help. Again, Thank you Thank you Thank you for your help in advance. Regards, Stephen Price CTO Price Telecommunications, Inc. 3237 S. Cherokee Lane Suite # 1120 Woodstock, GA 30188 USA Work: 770-977- Ext:106 Fax: 678-494-2292 Email: [EMAIL PROTECTED] Web: www.pricetel.com 3CUG: www.3CUG.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/
fatal error
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 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (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 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 2560 height: 1024 depth: 32 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 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 winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello 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: 040A (040a) (--) Using preset keyboard for Spanish (Spain, Traditional Sort) (40a), type 4 (--) 3 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' Please, could you let me know how to fix it? Thank you very much Best Regards Carlos Morán Tejeda -- 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/
Fatal error message
Dear cygwin, I have the following error message when I typed startx (My window is window server 2003). 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 contact: cygwin-xfree@cygwin.com XWin was started with the following command-line: X:0 -multiwindow -clipboard I attached the Xwin.log. with regards, A graduate student. 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: X :0 -multiwindow -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1600 h 1200 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information (==) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1600 height: 1200 depth: 32 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 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: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 (--) 3 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/100dpi/, removing from list! winInitMultiWindowWM - pthread_mutex_lock () returned. winProcEstablishConnection - Hello winInitClipboard () winClipboardProc - Hello winProcEstablishConnection - winInitClipboard returned. DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window parameter) winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window parameter) winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window parameter) winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window parameter) winClipboardProc - Call to select () failed: -1. Bailing. winClipboardProc - XDestroyWindow succeeded. winMultiWindowXMsgProcIOErrorHandler! winInitMultiWindowXMsgProc - Caught IO Error. 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: Startxwin.bat fatal error in Windows Vista
Allen Rongone wrote on Monday, May 14, 2007 8:29 PM:: I've seen this before under Windows XP and it was due to the fact that the previous user was the owner of the /tmp/.X11-unix directory and no one else had permissions to delete the X0 file nor were they able to remove this directory. I just gave Everyone Full Control to the /tmp directory and made it inheritable, that solved the problem. However, now under Vista, Everyone no longer gets propagated to the /tmp/X11-unix directory so when another user runs startxwin.bat it cannot delete the X0 file and remove the sud-directory. The usual workaround for this is to make /tmp a user mount, i.e. each user has their own /tmp. E.g.: mount -u -b $APPDATA\\tmp /tmp If that doesn't work, there's either a program already using port 6000, or your firewall/antivirus is blocking access to it. X uses port 6000 + the display number, so if another program's using port 6000, you can start X on say port 6002 with XWin :2. -- 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/
Startxwin.bat fatal error in Windows Vista
Hello, We recently received a new Dell Precision M90 laptop with Windows Vista Business version 6.0 pre-installed. I downloaded and installed the latest version of Cygwin (1.5.24) on it. Our users use it for X window access to our Unix servers, anyway, whenever a user on this machine attempts to run the startxwin.bat file they get a window that pops up and says: A fatal error has occurred and Cygwin/X will now exit. Please open /tmp/XWin.log for more information. XWin was started with the following command-line: /usr/X11R6/bin/XWin -multiwindow -clipboard -silent-dup-error I've attached a copy of the log, (along with with the output of cygcheck) but it basically says that there was fatal server error because it couldn't establish any listening sockets - Make sure an X server isn't already running. I've seen this before under Windows XP and it was due to the fact that the previous user was the owner of the /tmp/.X11-unix directory and no one else had permissions to delete the X0 file nor were they able to remove this directory. I just gave Everyone Full Control to the /tmp directory and made it inheritable, that solved the problem. However, now under Vista, Everyone no longer gets propagated to the /tmp/X11-unix directory so when another user runs startxwin.bat it cannot delete the X0 file and remove the sud-directory. Is this a Vista problem or a XWin.exe issue? And if so does anyone know a workaround? I've tried configuring the permissions every which way and no matter what I try the permissions do not get propagated to the /tmp/X11-unix directory. Thank you for your time, Allen Rongone _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 Cygwin Configuration Diagnostics Current System Time: Mon May 14 12:09:45 2007 Windows Longhorn/Vista (not yet supported!) Ver 6.0 Build 6000 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\Windows\system32 c:\Windows c:\Windows\System32\Wbem c:\Program Files\Common Files\Roxio Shared\DLLShared\ c:\Program Files\Microsoft SQL Server\90\Tools\binn\ c:\Program Files\ZipGenius 6\ c:\Program Files\wbin\ SysDir: C:\Windows\system32 WinDir: C:\Windows USER = 'root' PWD = '/home/root' HOME = '/home/root' MAKE_MODE = 'unix' HOMEPATH = '\Users\root' MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man' APPDATA = 'C:\Users\root\AppData\Roaming' HOSTNAME = 'boulder1' TERM = 'cygwin' ROXIOCENTRAL = 'C:\Program Files\Common Files\Roxio Shared\9.0\Roxio Central33\' PROCESSOR_IDENTIFIER = 'x86 Family 6 Model 15 Stepping 6, GenuineIntel' WINDIR = 'C:\Windows' VS80COMNTOOLS = 'C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\' PUBLIC = 'C:\Users\Public' OLDPWD = '/usr/bin' PROGRAMDATA = 'C:\ProgramData' USERDOMAIN = 'boulder1' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\ProgramData' !:: = '::\' TEMP = '/cygdrive/c/Users/root/AppData/Local/Temp' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' USERNAME = 'root' PROCESSOR_LEVEL = '6' FP_NO_HOST_CHECK = 'NO' SYSTEMDRIVE = 'C:' USERPROFILE = 'C:\Users\root' PS1 = '\[\e]0;[EMAIL PROTECTED] \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = '\\BOULDER1' PROCESSOR_ARCHITECTURE = 'x86' LOCALAPPDATA = 'C:\Users\root\AppData\Local' !C: = 'C:\cygwin\bin' SHLVL = '1' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' HOMEDRIVE = 'C:' PROMPT = '$P$G' COMSPEC = 'C:\Windows\system32\cmd.exe' TMP = '/cygdrive/c/Users/root/AppData/Local/Temp' SYSTEMROOT = 'C:\Windows' PRINTER = 'Adobe PDF' CVS_RSH = '/bin/ssh' PROCESSOR_REVISION = '0f06' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info:' PROGRAMFILES = 'C:\Program Files' NUMBER_OF_PROCESSORS = '2' SESSIONNAME = 'Console' COMPUTERNAME = 'BOULDER1' _ = '/usr/bin/cygcheck' POSIXLY_CORRECT = '1' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 (default) = '/cygdrive' cygdrive flags = 0x0022 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/ (default) = 'C:\cygwin' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin (default) = 'C:\cygwin/bin' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib (default) = 'C:\cygwin/lib' flags = 0x000a HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options c: hd NTFS
Fatal Error with Cygwin usage
Hi, i just downloaded the freeware software with the x11 feature. When i type 'startx' command, the program seems to run, but ends up giving me a Fatal error message saying: A fatal error has occured and Cygwin/X will now exit. Please open /tmp.XWin.log for more imformation. please guide. himanshu -- 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/
Unfixable(?) fatal error with X Server 6.8.99.901-4
After a fresh installation of Cygwin on several computers, I continue to encounter the same error upon execution of the startxwin.bat script. Unlike other users have reported, I always encounter it on execution, regardless of whether or not an X server is already running. Unfortunately, this is a serious problem for me as I can no longer get X servers running on any of my newly updated/installed machines. a fatal error has occurred and Cygwin/X will now exit XWin was started with the following command line: /usr/X11R6/bin/XWin -multiwindow -clipboard -silent-dup-error I read up on this error, the best thread I found is here: http://www.mail-archive.com/cygwin-xfree@cygwin.com/msg15983.html Perhaps the reason my version will not execute at all is a new 6.8.99.901-4 (vs. -1) problem? I attempted the author's suggestion of rolling back the xorg-x11-xwin package to 6.8.2.0-4. Unfortunately, now instead of outputing the error, Xwin quietly stackdumps (and does not run). I also tried rolling back every xorg-x11-* package to whatever version was available, which ranged from 6.8.1.0-* to 6.8.2.0-*. Again, xwin quietly stackdumps. I have copied below the output in /tmp/XWin.log using 6.8.99.901-4. Please let me know if you would like any other information. Malina Kirn output in /tmp/XWin.log using 6.8.99.901-4 Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.2.0-2 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: X :0 -multiwindow -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information (==) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1024 depth: 32 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 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 winInitMultiWindowWM - 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: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () (--) 3 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! winInitMultiWindowWM - pthread_mutex_lock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winInitMultiWindowWM - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 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. winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. winClipboardIOErrorHandler! 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: Unfixable(?) fatal error with X Server 6.8.99.901-4
Malina Kirn wrote: After a fresh installation of Cygwin on several computers, I continue to encounter the same error upon execution of the startxwin.bat script. Unlike other users have reported, I always encounter it on execution, regardless of whether or not an X server is already running. Unfortunately, this is a serious problem for me as I can no longer get X servers running on any of my newly updated/installed machines. a fatal error has occurred and Cygwin/X will now exit XWin was started with the following command line: /usr/X11R6/bin/XWin -multiwindow -clipboard -silent-dup-error I read up on this error, the best thread I found is here: http://www.mail-archive.com/cygwin-xfree@cygwin.com/msg15983.html Perhaps the reason my version will not execute at all is a new 6.8.99.901-4 (vs. -1) problem? I don't see a -4 version, I have the -1 and it works fine. [snip] Looking at the log and from what you describe there are 2 differences with respect of what I use, I start it with startx and I have cygserver running (so XWin can use shared memory), also I have the environment variable CYGWIN=server set. Can you test that with 6.8.99.901-1? -- René Berber -- 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/
fatal error occured and cygwin/x will now exit
-- 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/
fatal error with X Server 6.8.99.901-1
Since upgrading X Server from 6.8.2.0-4 to 6.8.99.901-1, I get a Windows alert box after opening a second xterm window using the startxwin.bat script, which apparently used to be able to detect whether X Server was already running or not so as not to attempt to start multiple instances. This detection mechanism seems to be broken with the new release. Despite the fact that a fatal error has occurred and Cygwin/X will now exit, all seems to work just fine after dismissing the alert box. Reverting back to 6.8.2.0-4, all seems to work as before, even with all the other new X stuff, which didn't seem to be announced. Perhaps some caveats would have been mentioned. The alert box directs me to file /tmp/XWin.log, which I copy, below. The alert box also says: XWin was started with the following command line: /usr/X11R6/bin/XWin -multiwindow -clipboard -silent-dup-error Attached is cygcheck -svr output. Wondering if X Server is broken or the startxwin.bat script or what, but for now, the older version seems to be working just fine. --Ken Nellis = /tmp/XWin.log _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Fatal server error: Cannot establish any listening sockets - Make sure an X server isn't already running === end /tmp/XWin.log === cygcheck.out Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
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: CygWin fatal error...
[EMAIL PROTECTED] wrote: Hi. I'm new to all this about Cygwin. I'couldn't find any page concerning this issue. It isn't even about a product of yours. It happens i been tring to use the Axiomatic Multi-platform C Compiler from AxiomSol, it uses the Cygwin basement on the Windows version. I don't know if you even heard about it, it is a C compiler wich produces Java ByteCode instead, quite a good idea. The thing is, once it is installed, if i try to start the Xwin server (following the sequence of commands on the ampcstart bat file), an error is generated indcating A fatal error has ocurred and Cygwin/X will now exit. Whenever i search for a file Xwin.log on the /tmp directory, it happens that this file not even exists!. Some of the directories mentioned on the same bat file wich are part of the Cygwin installation doesn't exist neither. I mentioned this issue to the guys of Axiomsol but they don't seem to understand it (they insist on the firewall stuff but i don't think this is the problem). So i'm writing you in the hope for some more useful tip. Thanks a lot, i'll be waiting your answer This is really off-topic since it's a problem with a 3rd party product. You do really need to get them to resolve it for you. However, if I had to guess, I'd say the problem is duplicate cygwin1.dlls and/or other Cygwin DLLs. You can test this by isolating (or completely uninstalling) the Axiomatic compiler and see if that resolves the issue. You may find that you need to reinstall Cygwin via setup.exe to get all the settings back to where they should be (Axiomatic may muck with these as part of their installation). But take it one step at a time. If you find just uninstalling the Axiomatic compiler resolves the issue, you can look at reinstalling Axiomatic and removing duplicated Cygwin DLLs from the installation (especially cygwin1.dll). Just make sure that the Cygwin bin directory is in your (Windows) path and that the DLLs you remove from Axiomatic's installation exist in your Cygwin instalation. That should allow you to use both Cygwin and Axiomatic together, assuming all the above yielded positive results. But keep in mind that this is a fragile installation on Axiomatic's part. Any update of their stuff will likely break things again. That's something you want to take up with them. -- 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/
CygWin fatal error...
Hi. I'm new to all this about Cygwin. I'couldn't find any page concerning this issue. It isn't even about a product of yours. It happens i been tring to use the Axiomatic Multi-platform C Compiler from AxiomSol, it uses the Cygwin basement on the Windows version. I don't know if you even heard about it, it is a C compiler wich produces Java ByteCode instead, quite a good idea. The thing is, once it is installed, if i try to start the Xwin server (following the sequence of commands on the ampcstart bat file), an error is generated indcating A fatal error has ocurred and Cygwin/X will now exit. Whenever i search for a file Xwin.log on the /tmp directory, it happens that this file not even exists!. Some of the directories mentioned on the same bat file wich are part of the Cygwin installation doesn't exist neither. I mentioned this issue to the guys of Axiomsol but they don't seem to understand it (they insist on the firewall stuff but i don't think this is the problem). So i'm writing you in the hope for some more useful tip. Thanks a lot, i'll be waiting your answer -- 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/
fatal error -- Cygwin/X Project 6.8.2.0-4
This is a bug-report. -- Yitwah Cheung Mathematics Department San Francisco State University San Francisco, CA 94132 [EMAIL PROTECTED] (email) http://math.sfsu.edu/cheung (website) 415-338-1805 (phone) 415-338-1461 (fax) 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 -multiwindow -clipboard -silent-dup-error ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winCheckDisplayNumber - Cygwin/X is already running on display 0 Fatal server erMakeAInitOutput - Duplicate invocation on display number: 0. Exiting. winDeinitMultiWindowWM - Noting shutdown in progress X server isn't already running 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: 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/
fatal error occurred. my mozilla installation failed. what to do?
Mit freundlichem Gruß Dr. Alfred Schlicht Vortragender Legationsrat Auswärtiges Amt, Ref. 606 Tel. 01888/173247 Fax 01888/1753247 e-mail: [EMAIL PROTECTED] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: 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/
How do I fix XDMCP fatal error: Manager unwilling Host unwilling?
This is essentially Part 2 of my other email (Duplication error upon startx with XWin :0; No terminal with XWin :1). I'm running a freshly downloaded cygwin/x, and am trying to connect WinXP to a (nearly) freshly installed Linux box running MEPIS. Running the default startxdmcp.bat with XWin :0 -query %REMOTE_HOST% -nodecoration -lesspointer fails at: Fatal server error: XDMCP fatal error: Manager unwilling Host unwilling. The full XWin.log follows: - Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.2.0-3 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: /usr/X11R6/bin/XWin :0 -query 192.168.0.111 -nodecoration -lesspointer ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1600 h 1200 winInitializeDefaultScreens - Returning _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information (==) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) (--) Using preset keyboard for English (USA) (409), type 4 (--) 5 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list! Fatal server error: XDMCP fatal error: Manager unwilling Host unwilling winDeinitMultiWindowWM - Noting shutdown in progress - Now, I'm new to both Linux and XDMCP, so I'm still feeling my way in this area. But I have managed to track down /etc/kde3/kdm/kdmrc and modify the approriate line to: [Xdmcp] Enable=true I have also done a few other things specified in the XDMCP HowTo available at http://en.tldp.org/HOWTO/XDMCP-HOWTO/. But due to the specifics of MEPIS combined with my inexperience with Linux, there is still a reasonable chance that I have missed something. Also, I think (but am not sure) that I have set up GuardDog (firewall) on MEPIS to allow the XDMCP requests. At least I am now getting the same results with the firewall turned off as when it is turned on. What is the likely cause of the fatal error in this case? What steps should I take to overcome it? Thanks, Angus. Cygwin Configuration Diagnostics Current System Time: Fri Jul 08 01:25:11 2005 Windows XP Professional Ver 5.1 Build 2600 Path: C:\WINDOWS\system32 C:\WINDOWS C:\WINDOWS\System32\Wbem C:\Program Files\Common Files\GTK\2.0\bin Output from C:\cygwin\bin\id.exe (nontsec) UID: 1004(angus) GID: 513(None) 0(root) 513(None)544(Administrators) 545(Users) 1003(Debugger Users) Output from C:\cygwin\bin\id.exe (ntsec) UID: 1004(angus) GID: 513(None) 0(root) 513(None)544(Administrators) 545(Users) 1003(Debugger Users) SysDir: C:\WINDOWS\System32 WinDir: C:\WINDOWS Path = `C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Common Files\GTK\2.0\bin' ALLUSERSPROFILE = `C:\Documents and Settings\All Users' APPDATA = `C:\Documents and Settings\angus\Application Data' CLASSPATH = `C:\WINDOWS\System32\QTJava.zip' CommonProgramFiles = `C:\Program Files\Common Files' COMPUTERNAME = `DURON1K' ComSpec = `C:\WINDOWS\system32\cmd.exe' GAIMHOME = `D:\Gaim\Data Settings' HOMEDRIVE = `C:' HOMEPATH = `\' LOGONSERVER = `\\DURON1K' NUMBER_OF_PROCESSORS = `1' OS = `Windows_NT' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PROCESSOR_ARCHITECTURE = `x86' PROCESSOR_IDENTIFIER = `x86 Family 6 Model 7 Stepping 0, AuthenticAMD' PROCESSOR_LEVEL = `6' PROCESSOR_REVISION = `0700' ProgramFiles = `C:\Program Files' PROMPT = `$P$G' QTJAVA = `C:\WINDOWS\System32\QTJava.zip' SESSIONNAME = `Console' SystemDrive = `C:' SystemRoot = `C:\WINDOWS' TEMP = `C:\DOCUME~1\angus\LOCALS~1\Temp' TMP = `C:\DOCUME~1\angus\LOCALS~1\Temp' USERDOMAIN = `DURON1K' USERNAME = `angus' USERPROFILE = `C:\Documents and Settings\angus' windir = `C:\WINDOWS' POSIXLY_CORRECT = `1' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 (default) = `/cygdrive' cygdrive flags = 0x0022 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/ (default
Re: How do I fix XDMCP fatal error: Manager unwilling Host unwilling?
On Fri, 8 Jul 2005, Angus Veitch wrote: Running the default startxdmcp.bat with XWin :0 -query %REMOTE_HOST% -nodecoration -lesspointer fails at: Fatal server error: XDMCP fatal error: Manager unwilling Host unwilling. The full XWin.log follows: Fatal server error: XDMCP fatal error: Manager unwilling Host unwilling Now, I'm new to both Linux and XDMCP, so I'm still feeling my way in this area. But I have managed to track down /etc/kde3/kdm/kdmrc and modify the approriate line to: [Xdmcp] Enable=true I have also done a few other things specified in the XDMCP HowTo available at http://en.tldp.org/HOWTO/XDMCP-HOWTO/. But due to the specifics of MEPIS combined with my inexperience with Linux, there is still a reasonable chance that I have missed something. http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-xdmcp-query XDMCP and firewalls XDMCP will not work correctly if you have a personal firewall installed or the built-in firewall of Windows is activated. The XDMCP protocol will send and receive data on port 177/UDP. But the actual connections will be made to the local port 6000/TCP. It is safe to allow connections since the xserver has an own security layer. An overview of used ports is given in Table 2. Table 2. Ports used with XDMCP connections PortProtocolDirection Comment 177 UDP Incoming/Outgoing Actual XDMCP connection 6000+displayTCP IncomingConnection for X11 clients. display is usally 0 except you specify it on the commandline. Special Note: XDMCP does not work with any kind of network address translation There are configuration files for xdm which control which host can connect to the xdmcp server. They are usally located in /etc/X11/xdm/Xaccess. KDM may use different locations. The default will allow any host access. But I don't know how the installed files differ from the defaults. You might want to ask the distributor of MEPIS how to get XDMCP access to the system. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
fatal error in running startx (after installing KDE)
Hi I got this message and unable to get my KDE loaded: == $startx + test -f /home/darwin/.kde_mountchecked + IPC_PID=3948 + ipc_daemon2 + client_opt= + server_opt= + xinit /opt/kde3/bin/startkde -- usr/X11R6/bin/XWin :0 -noreset -ac -nowinkill Wlcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.2.0-1 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: /usr/X11R6/bin/XWin :0 -noreset -ac -nowinkill Fatal server error: CAnnot open log file /tmp/XWin.log $ winDeinitMultiWindowWM - Noting shutdown in progress giving up xinit: Connection refused (errno 111): unable to connect to X server xinit: No such process (errno 3): Server error. + kill -15 3948 == 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 any help/clue is welcome thanx in advance (at least for reading this email) darwin -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
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
Fatal error while trying to use X11 in Cygwin... Please help me! Thank you!
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 ? Thank you very much, Philip (novice user of Linux- and any other related things...) --- The log file : $ cat XWin.log Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.8.1.0-1 Contact: [EMAIL PROTECTED] XWin was started with the following command line: x -br ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning (WW) /tmp mounted int textmode _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (II) XF86Config is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shar ed memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 040C (040c) (--) Using preset keyboard for French (Standard) (40c), type 4 (--) 5 mouse buttons found Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from li st! Fatal server error: could not open default font 'fixed' winDeinitMultiWindowWM - Noting shutdown in progress _ Trouvez l'âme soeur sur MSN Rencontres http://g.msn.fr/FR1000/9551
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
Fatal error while trying to use X11 in Cygwin...
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? Thank you very much, Philip (novice user of Linux- and any other related things...) _ Trouvez l'âme soeur sur MSN Rencontres http://g.msn.fr/FR1000/9551 XWin.log Description: Binary data
Fatal Error found in cygwin/X
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 Sundar.G System Administrator _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus
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
fatal error on cygwin/X
Hello, I installed cygwin-x, Release: 6.8.1.0. XWin was started with the following command line: /usr/X11R6/bin/XWin -ac -multiwindow -clipboard and hereafter the result: ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. 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 winDeinitMultiWindowWM - Noting shutdown in progress Can you help me? Best regards
Fatal Error while starting XWin
Hi, I have recently downloaded the cygwin/x program. When I tried to open it I got a fatal error message saying that the Cygwin/X will exit. The Xwin has started with the command /usr/X11R6/bin/Xwin -multiwindow -clipboard (this is the default). I looked at the file /tmp/Xwin.log and it said: Fatal server error: InitOutput - Duplicate invocation on display number: 0. Exiting. Then I looked at the archives and found this solution to the above problem. This means the first started X server is still running. startxwin does two things: - start the X server - start xterm as client If you want to start xterm twice, install the X-start-menu-icons and start xterm from Start-Programs-Cygwin-X-XTerm bye ago When I tried to follow these steps, I could not open Start-Programs-Cygwin-X-XTerm. When I clicked on it it just would not do anything. I would really appreciate any advise on how to fix this problem, V __ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/
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
Fatal Error while starting XWin
Hi, I have recently downloaded the cygwin/x program. The first time I run startxwin.bat the external window opened and everyhtink was fine. The second time I opened it I got a fatal error message saying that the Cygwin/X will exit. The Xwin has started with the command /usr/X11R6/bin/Xwin -multiwindow -clipboard (this is the default). I looked at the file /tmp/Xwin.log and it said: Fatal server error: InitOutput - Duplicate invocation on display number: 0. Exiting. The weird part was that the external window remained open and I could even ssh to a remote host. Everything seems to work fine and I just don't understand what is the problem. I would really appreciate any advise on how to fix this problem, Thank you, Roi
A fatal error has occurred and Cygwin/X will now exit.
H:\UNIX\cygwinPKGdir H:\UNIX\cygwin 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: 4.3.0.50 Contact: [EMAIL PROTECTED] XWin was started with the following command-line: XWin -multiwindow open /tmp/XWin.log Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 4.3.0.50 Contact: [EMAIL PROTECTED] XWin was started with the following command line: XWin -multiwindow ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1024 dwHeight: 768 winSetEngine - Multi Window = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per pixel winCreateBoundingWindowWindowed - User w: 1024 h: 768 winCreateBoundingWindowWindowed - Current w: 1024 h: 768 winAdjustForAutoHide - Original WorkArea: 0 0 768 1024 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found LEFT auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 1 768 1024 winCreateBoundingWindowWindowed - WindowClient w 1023 h 768 r 1023 l 0 b 768 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1023 height: 768 depth: 16 winAllocateFBShadowGDI - Dibsection width: 1023 height: 768 depth: 16 size image: 1572864 winAllocateFBShadowGDI - Created shadow stride: 1024 winFinishScreenInitFB - Masks: f800 07e0 001f winInitVisualsShadowGDI - Masks f800 07e0 001f BPRGB 6 d 16 bpp 16 winCreateDefColormap - Deferring to fbCreateDefColormap () null screen fn ReparentWindow null screen fn RestackWindow winFinishScreenInitFB - Calling winInitWM. InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitWM - Returning. winFinishScreenInitFB - returning winScreenInit - returning winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () InitOutput - Returning. MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) Rules = xfree86 Model = pc101 Layout = us Variant = (null) Options = (null) Fatal server error: could not open default font 'fixed' ___ H:\UNIX\cygwin\usr\X11R6\bin\startxwin.bat (REM removed) ___ @echo off SET DISPLAY=127.0.0.1:0.0 SET CYGWIN_ROOT=H:\UNIX\cygwin SET PATH=.;%CYGWIN_ROOT%\bin;%CYGWIN_ROOT%\usr\X11R6\bin;%PATH% 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 if %OS% == Windows_NT goto OS_NT echo startxwin.bat - Starting on Windows 95/98/Me goto STARTUP :OS_NT echo startxwin.bat - Starting on Windows NT/2000/XP/2003 :STARTUP start XWin -multiwindow run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash ___ thanks , rwd Searched the web for could not open default font 'fixed'. http://www.tridiavnc.com/list-mailist/1998-03/0415.html On Sun, 22 Mar 1998, Dr. Joel M. Hoffman wrote: I tried uncompressing the fonts is misc, but that didn't help. What am I doing wrong. The font path is correct! My apologies if you know this already - it's not enough to just uncompress the fonts, the fonts.dir/fonts.scale files must be updated with the new, uncompressed filenames. after font expansion of H:\UNIX\cygwin\usr\X11R6\lib\X11\fonts\misc 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: 4.3.0.50 Contact: [EMAIL PROTECTED] XWin was started with the following command-line: XWin -multiwindow __ XWin.log __ Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 4.3.0.50 Contact: [EMAIL PROTECTED] XWin was started with the following command line: XWin
A fatal error has occurred and Cygwin/X will now exit.
H:\UNIX\cygwinPKGdir H:\UNIX\cygwin 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: 4.3.0.50 Contact: [EMAIL PROTECTED] XWin was started with the following command-line: XWin -multiwindow open /tmp/XWin.log Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 4.3.0.50 Contact: [EMAIL PROTECTED] XWin was started with the following command line: XWin -multiwindow ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1024 dwHeight: 768 winSetEngine - Multi Window = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per pixel winCreateBoundingWindowWindowed - User w: 1024 h: 768 winCreateBoundingWindowWindowed - Current w: 1024 h: 768 winAdjustForAutoHide - Original WorkArea: 0 0 768 1024 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found LEFT auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 1 768 1024 winCreateBoundingWindowWindowed - WindowClient w 1023 h 768 r 1023 l 0 b 768 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1023 height: 768 depth: 16 winAllocateFBShadowGDI - Dibsection width: 1023 height: 768 depth: 16 size image: 1572864 winAllocateFBShadowGDI - Created shadow stride: 1024 winFinishScreenInitFB - Masks: f800 07e0 001f winInitVisualsShadowGDI - Masks f800 07e0 001f BPRGB 6 d 16 bpp 16 winCreateDefColormap - Deferring to fbCreateDefColormap () null screen fn ReparentWindow null screen fn RestackWindow winFinishScreenInitFB - Calling winInitWM. InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitWM - Returning. winFinishScreenInitFB - returning winScreenInit - returning winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () InitOutput - Returning. MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) Rules = xfree86 Model = pc101 Layout = us Variant = (null) Options = (null) Fatal server error: could not open default font 'fixed' ___ H:\UNIX\cygwin\usr\X11R6\bin\startxwin.bat (REM removed) ___ @echo off SET DISPLAY=127.0.0.1:0.0 SET CYGWIN_ROOT=H:\UNIX\cygwin SET PATH=.;%CYGWIN_ROOT%\bin;%CYGWIN_ROOT%\usr\X11R6\bin;%PATH% 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 if %OS% == Windows_NT goto OS_NT echo startxwin.bat - Starting on Windows 95/98/Me goto STARTUP :OS_NT echo startxwin.bat - Starting on Windows NT/2000/XP/2003 :STARTUP start XWin -multiwindow run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash ___ thanks , rwd Searched the web for could not open default font 'fixed'. http://www.tridiavnc.com/list-mailist/1998-03/0415.html On Sun, 22 Mar 1998, Dr. Joel M. Hoffman wrote: I tried uncompressing the fonts is misc, but that didn't help. What am I doing wrong. The font path is correct! My apologies if you know this already - it's not enough to just uncompress the fonts, the fonts.dir/fonts.scale files must be updated with the new, uncompressed filenames. after font expansion of H:\UNIX\cygwin\usr\X11R6\lib\X11\fonts\misc 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: 4.3.0.50 Contact: [EMAIL PROTECTED] XWin was started with the following command-line: XWin -multiwindow __ XWin.log __ Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 4.3.0.50 Contact: [EMAIL PROTECTED] XWin was started with the following command line: XWin
Re: A fatal error has occurred and Cygwin/X will now exit.
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-error-font-eof [EMAIL PROTECTED] wrote: H:\UNIX\cygwinPKGdir H:\UNIX\cygwin 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: 4.3.0.50 Contact: [EMAIL PROTECTED] XWin was started with the following command-line: XWin -multiwindow open /tmp/XWin.log Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 4.3.0.50 Contact: [EMAIL PROTECTED] XWin was started with the following command line: XWin -multiwindow ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1024 dwHeight: 768 winSetEngine - Multi Window = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per pixel winCreateBoundingWindowWindowed - User w: 1024 h: 768 winCreateBoundingWindowWindowed - Current w: 1024 h: 768 winAdjustForAutoHide - Original WorkArea: 0 0 768 1024 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found LEFT auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 1 768 1024 winCreateBoundingWindowWindowed - WindowClient w 1023 h 768 r 1023 l 0 b 768 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1023 height: 768 depth: 16 winAllocateFBShadowGDI - Dibsection width: 1023 height: 768 depth: 16 size image: 1572864 winAllocateFBShadowGDI - Created shadow stride: 1024 winFinishScreenInitFB - Masks: f800 07e0 001f winInitVisualsShadowGDI - Masks f800 07e0 001f BPRGB 6 d 16 bpp 16 winCreateDefColormap - Deferring to fbCreateDefColormap () null screen fn ReparentWindow null screen fn RestackWindow winFinishScreenInitFB - Calling winInitWM. InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitWM - Returning. winFinishScreenInitFB - returning winScreenInit - returning winInitMultiWindowWM - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Hello winMultiWindowXMsgProc - Calling pthread_mutex_lock () InitOutput - Returning. MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: 0409 (0409) Rules = xfree86 Model = pc101 Layout = us Variant = (null) Options = (null) Fatal server error: could not open default font 'fixed' ___ H:\UNIX\cygwin\usr\X11R6\bin\startxwin.bat (REM removed) ___ @echo off SET DISPLAY=127.0.0.1:0.0 SET CYGWIN_ROOT=H:\UNIX\cygwin SET PATH=.;%CYGWIN_ROOT%\bin;%CYGWIN_ROOT%\usr\X11R6\bin;%PATH% 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 if %OS% == Windows_NT goto OS_NT echo startxwin.bat - Starting on Windows 95/98/Me goto STARTUP :OS_NT echo startxwin.bat - Starting on Windows NT/2000/XP/2003 :STARTUP start XWin -multiwindow run xterm -sl 1000 -sb -rightbar -ms red -fg yellow -bg black -e /usr/bin/bash ___ thanks , rwd Searched the web for could not open default font 'fixed'. http://www.tridiavnc.com/list-mailist/1998-03/0415.html On Sun, 22 Mar 1998, Dr. Joel M. Hoffman wrote: I tried uncompressing the fonts is misc, but that didn't help. What am I doing wrong. The font path is correct! My apologies if you know this already - it's not enough to just uncompress the fonts, the fonts.dir/fonts.scale files must be updated with the new, uncompressed filenames. after font expansion of H:\UNIX\cygwin\usr\X11R6\lib\X11\fonts\misc 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: 4.3.0.50 Contact: [EMAIL PROTECTED] XWin was started with the following command-line: XWin -multiwindow __ XWin.log __ Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 4.3.0.50 Contact: [EMAIL PROTECTED
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.
fatal error
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. XWin.log Description: Binary data
Re: (additional info) Can't start gnome-terminal, fatal error
A couple of thoughts... Have you verified that the remote host is actually running a font server? Take a look at /tmp/XWin.log for error messages pertaining to the font path. Try running a local xterm and entering xset fp+ remote font path instead of using the -fp command-line option. From: Jonathan Primeau [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: (additional info) Can't start gnome-terminal, fatal error Date: Wed, 15 Oct 2003 10:10:15 -0400 I have more information related to my problem. I hope that this will make my problem more obvious... When I run gnome-terminal from a standard terminal I get: BEGIN OUTPUT ** (gnome-terminal:161): WARNING **: Cannot load font for XLFD '-bitstream-courier-medium-r-normal--14-*-*-*-*-*-iso8859-1 (gnome-terminal:161): ZVT-WARNING **: Cannot get required fonts from monospace13 (gnome-terminal:161): ZVT-WARNING **: Use -*-*-*-*-*-*-13-*-*-*-*-*-*-* XLFD fontname - some characters may not appear correctly (gnome-terminal:161): ZVT-WARNING **: Use -*-*-*-*-*-*-0-*-*-*-*-*-*-* XLFD fontname - some characters may not appear correctly (gnome-terminal:161): ZVT-CRITICAL **: file zvti18n.c: line 831: assertion `new_fontset != NULL' failed (gnome-terminal:161): ZVT-WARNING **: Failed to load any required font, so crash will occur..check X11 font pathes and etc/pangox.alias file ** (gnome-terminal:161): WARNING **: Cannot load font for XLFD '-adobe-helvetica-medium-r-normal--10-*-*-*-*-*-iso8859-1 ** (gnome-terminal:161): WARNING **: Cannot load font for XLFD '-bitstream-courier-medium-r-normal--10-*-*-*-*-*-iso8859-1 (gnome-terminal:161): ZVT-WARNING **: Cannot get required fonts from monospace10 (gnome-terminal:161): ZVT-WARNING **: Use -*-*-*-*-*-*-10-*-*-*-*-*-*-* XLFD fontname - some characters may not appear correctly (gnome-terminal:161): ZVT-WARNING **: Use -*-*-*-*-*-*-0-*-*-*-*-*-*-* XLFD fontname - some characters may not appear correctly (gnome-terminal:161): ZVT-CRITICAL **: file zvti18n.c: line 831: assertion `new_fontset != NULL' failed (gnome-terminal:161): ZVT-WARNING **: Failed to load any required font, so crash will occur..check X11 font pathes and etc/pangox.alias file ** (gnome_segv:162): WARNING **: Cannot load font for XLFD '-adobe-helvetica-medium-r-normal--10-*-*-*-*-*-iso8859-1 -- END OUTPUT I guess that the problem comes from the missing fonts, it says: Failed to load any required font, so crash will occur..check X11 font pathes and etc/pangox.alias file. Is there any way I can fix that? By the way, I use the -fp option for Xwin (Font server). Regards, Jonathan Primeau _ Surf and talk on the phone at the same time with broadband Internet access. Get high-speed for as low as $29.95/month (depending on the local service providers in your area). https://broadband.msn.com
Can't start gnome-terminal, fatal error
Hi, I am running the latest version of XWin on my Windows XP machine. I am able to connect to the remote Sun Ultra 5 (running Solaris 9 w/ GNOME 2.0) by using the following command: Xwin -screen 0 1280 1024 -from myhost -query remote_host -fp tcp/remote_host:7100 -fullscreen -depth 24 -refresh 85 The GNOME desktop displays properly. However, when I run the gnome-terminal application, the following error occurs: Application gnome-terminal (process 29819) has crashed due to a fatal error. (Arithmetic Exception) I am unable to run Netscape as well. However, I don't get any error message (the dtaction window appears but nothing happens). Any help would be appreciated, Best Regards, Jonathan Primeau
(additional info) Can't start gnome-terminal, fatal error
I have more information related to my problem. I hope that this will make my problem more obvious... When I run gnome-terminal from a standard terminal I get: BEGIN OUTPUT ** (gnome-terminal:161): WARNING **: Cannot load font for XLFD '-bitstream-courier-medium-r-normal--14-*-*-*-*-*-iso8859-1 (gnome-terminal:161): ZVT-WARNING **: Cannot get required fonts from monospace13 (gnome-terminal:161): ZVT-WARNING **: Use -*-*-*-*-*-*-13-*-*-*-*-*-*-* XLFD fontname - some characters may not appear correctly (gnome-terminal:161): ZVT-WARNING **: Use -*-*-*-*-*-*-0-*-*-*-*-*-*-* XLFD fontname - some characters may not appear correctly (gnome-terminal:161): ZVT-CRITICAL **: file zvti18n.c: line 831: assertion `new_fontset != NULL' failed (gnome-terminal:161): ZVT-WARNING **: Failed to load any required font, so crash will occur..check X11 font pathes and etc/pangox.alias file ** (gnome-terminal:161): WARNING **: Cannot load font for XLFD '-adobe-helvetica-medium-r-normal--10-*-*-*-*-*-iso8859-1 ** (gnome-terminal:161): WARNING **: Cannot load font for XLFD '-bitstream-courier-medium-r-normal--10-*-*-*-*-*-iso8859-1 (gnome-terminal:161): ZVT-WARNING **: Cannot get required fonts from monospace10 (gnome-terminal:161): ZVT-WARNING **: Use -*-*-*-*-*-*-10-*-*-*-*-*-*-* XLFD fontname - some characters may not appear correctly (gnome-terminal:161): ZVT-WARNING **: Use -*-*-*-*-*-*-0-*-*-*-*-*-*-* XLFD fontname - some characters may not appear correctly (gnome-terminal:161): ZVT-CRITICAL **: file zvti18n.c: line 831: assertion `new_fontset != NULL' failed (gnome-terminal:161): ZVT-WARNING **: Failed to load any required font, so crash will occur..check X11 font pathes and etc/pangox.alias file ** (gnome_segv:162): WARNING **: Cannot load font for XLFD '-adobe-helvetica-medium-r-normal--10-*-*-*-*-*-iso8859-1 -- END OUTPUT I guess that the problem comes from the missing fonts, it says: Failed to load any required font, so crash will occur..check X11 font pathes and etc/pangox.alias file. Is there any way I can fix that? By the way, I use the -fp option for Xwin (Font server). Regards, Jonathan Primeau
wmaker fatal error: could not open display :0
Having trouble getting X to run... The worst part about this is that I had it working a few hours ago, but I uninstalled and reinstalled becaused I foobared my package choices and vim couldn't find some resource. So atleast I know it's a configuration problem. Now to pin it down... I am using WindowsXP Home Ed. SP1 When I attempt to startx I get the following: - $ startx waiting for X server to shut down $ wmaker fatal error: could not open display :0 - I've also tried: - $ startx -display :1 // I've tried it as 1, :1 and :1 with the same response /usr/X11R6/bin/xterm Xt error: Can't open display: :1 waiting for X server to shut down - My XWin.log from just the command startx reads as... - $ cat XWin.log - ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (EE) Unable to locate/open config file InitOutput - Error reading config file winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - Allowing PrimaryDD winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 001f InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winSetEngine - Using Shadow DirectDraw NonLocking winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1024 h: 768 winCreateBoundingWindowWindowed - Current w: 1024 h: 768 winAdjustForAutoHide - Original WorkArea: 0 0 768 1024 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found BOTTOM auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 0 767 1024 winCreateBoundingWindowWindowed - WindowClient w 1018 h 735 r 1018 l 0 b 735 t 0 winCreateBoundingWindowWindowed - Returning winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Created primary surface winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface winAllocateFBShadowDDNL - lPitch: 4072 winAllocateFBShadowDDNL - Created shadow pitch: 4072 winAllocateFBShadowDDNL - Created shadow stride: 1018 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = xfree86 Model = pc101 Layout = us Variant = (null) Options = (null) winPointerWarpCursor - Discarding first warp: 509 367 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned - END XWin.log - And my cygwin.bat file reads - cygwin.bat - @echo off set DISPLAY=127.0.0.1:0.0 set CYGWIN=tty notitle glob set HOME=C:\cygwin\home PATH=C:\cygwin\bin;C:\cygwin\sbin;C:\cygwin\usr\bin;C:\cygwin\usr\sbin;C:\cy gwin\usr\local\bin;C:\cygwin\usr\X11R6\bin;.. C: chdir C:\cygwin\bin bash --login -i - END cygwin.bat - Last but not least... my .xinitrc file looks like this... - $ cat .xinitrc - #!/bin/sh # $Xorg: xinitrc.cpp,v 1.3 2000/08/17 19:54:30 cpqbld Exp $ userresources=$HOME/.Xresources usermodmap=$HOME/.Xmodmap sysresources=/usr/X11R6/lib/X11/xinit/.Xresources sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap # merge in defaults and keymaps if [ -f $sysresources ]; then xrdb -merge $sysresources fi if [ -f $sysmodmap ]; then xmodmap $sysmodmap fi if [ -f $userresources ]; then xrdb -merge $userresources fi if [ -f $usermodmap ]; then xmodmap $usermodmap fi # start some nice programs # twm # xclock -geometry 50x50-1+1 # xterm -geometry 80x50+494+51 # xterm -geometry 80x20+494-0 # exec xterm -geometry 80x66+0+0 -name login wmaker - END $ cat .xinitrc - Heeelllp! :P _ Free email with personality! Over 200 domains! http://www.MyOwnEmail.com Looking for friendships,romance and more? http://www.MyOwnFriends.com
Re: wmaker fatal error: could not open display :0
What happens if you try startxwin.sh? Thats how I pull up my xwindows. /Andy / digitalsmear [EMAIL PROTECTED] wrote: | Having trouble getting X to run... The worst part about this is that I | had it working a few hours ago, but I uninstalled and reinstalled becaused | I foobared my package choices and vim couldn't find some resource. So | atleast I know it's a configuration problem. Now to pin it down... | | I am using WindowsXP Home Ed. SP1 | When I attempt to startx I get the following: | - | $ startx | waiting for X server to shut down | $ wmaker fatal error: could not open display :0 -- The parser of the compiler rests on the code! Please note, new email, @telia.com - @comhem.se
