Re: XWin stopped working with xorg-server 1.7.1 - no log-file created
On 19/11/2009 08:33, Gertjan van Noord wrote: after upgrading to xorg-server 1.7.1-3 starting X does no longer work. Previous version 1.6.? worked. However, I can't seem to go back to that version using the cygwin setup programme. the startxwin.bat script does not complain, but no X logo appears, and indeed no X programs can be started. moreover no log-file is created in /var/log, which seems to suggest something very basic is going wrong? starting XWin from the command line, also with -logverbose 10 does not produce any output. rebooting does not change a thing I've attached my cygcheck.out You should perhaps try 'cygcheck /usr/bin/XWin.exe' to see if it identifies a missing DLL. -- 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 error
On 18/11/2009 17:20, baseball07 wrote: Thank you for the suggestion. Could you please type out the syntax. I'm a newbie to Linux code. Thank you very much. http://x.cygwin.com/docs/ug/using-remote-apps.html -- 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 stopped working with xorg-server 1.7.1 - no log-file created
Try -noclipboard. I hit this as well. Gertjan van Noord wrote: after upgrading to xorg-server 1.7.1-3 starting X does no longer work. Previous version 1.6.? worked. However, I can't seem to go back to that version using the cygwin setup programme. the startxwin.bat script does not complain, but no X logo appears, and indeed no X programs can be started. moreover no log-file is created in /var/log, which seems to suggest something very basic is going wrong? starting XWin from the command line, also with -logverbose 10 does not produce any output. rebooting does not change a thing I've attached my cygcheck.out GJ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: XWin stopped working with xorg-server 1.7.1 - no log-file created
On Thu, Nov 19, 2009 at 10:18:22AM -0500, Michael Breuer wrote: Try -noclipboard. this solves my problem, many thanks. GJ I hit this as well. Gertjan van Noord wrote: after upgrading to xorg-server 1.7.1-3 starting X does no longer work. Previous version 1.6.? worked. However, I can't seem to go back to that version using the cygwin setup programme. the startxwin.bat script does not complain, but no X logo appears, and indeed no X programs can be started. moreover no log-file is created in /var/log, which seems to suggest something very basic is going wrong? starting XWin from the command line, also with -logverbose 10 does not produce any output. rebooting does not change a thing I've attached my cygcheck.out GJ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: XWin stopped working with xorg-server 1.7.1 - no log-file created
the DLL's are all there. Using the other poster's suggestion to use -noclipboard solves my problem, although I have no idea what/why. GJ On Thu, Nov 19, 2009 at 02:00:28PM +, Jon TURNEY wrote: On 19/11/2009 08:33, Gertjan van Noord wrote: after upgrading to xorg-server 1.7.1-3 starting X does no longer work. Previous version 1.6.? worked. However, I can't seem to go back to that version using the cygwin setup programme. the startxwin.bat script does not complain, but no X logo appears, and indeed no X programs can be started. moreover no log-file is created in /var/log, which seems to suggest something very basic is going wrong? starting XWin from the command line, also with -logverbose 10 does not produce any output. rebooting does not change a thing I've attached my cygcheck.out You should perhaps try 'cygcheck /usr/bin/XWin.exe' to see if it identifies a missing DLL. -- 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 stopped working with xorg-server 1.7.1 - no log-file created
For what it's worth, I tracked that down yesterday by looking at the error log on the server - there was a complaint about clipboard - don't recall what... seemed innocuous but figured I'd try turning off clipboard. Viola, it worked. One other point - as older versions of CygwinX have major issues (100% cpu) with the newer version of Gnome (now in F12), more people are going to be trying the beta and hitting this. Not sure what code is involved, but including this on the beta FAQ might be worthwhile. Gertjan van Noord wrote: the DLL's are all there. Using the other poster's suggestion to use -noclipboard solves my problem, although I have no idea what/why. GJ On Thu, Nov 19, 2009 at 02:00:28PM +, Jon TURNEY wrote: On 19/11/2009 08:33, Gertjan van Noord wrote: after upgrading to xorg-server 1.7.1-3 starting X does no longer work. Previous version 1.6.? worked. However, I can't seem to go back to that version using the cygwin setup programme. the startxwin.bat script does not complain, but no X logo appears, and indeed no X programs can be started. moreover no log-file is created in /var/log, which seems to suggest something very basic is going wrong? starting XWin from the command line, also with -logverbose 10 does not produce any output. rebooting does not change a thing I've attached my cygcheck.out You should perhaps try 'cygcheck /usr/bin/XWin.exe' to see if it identifies a missing DLL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin error
baseball07 wrote: Hi everyone I am getting this error when I try and locally access the Linux machines in my department and try and run a program called Cadence. Does anyone know what this means? Yes, the remote X server can't connect to your local machine, the path to which is contained in the variable DISPLAY. The latter is unset in your case, most probably because you need to login with ssh -X. Ciao Lothar -- 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/
Problem with new xinit - console window doesn't open (but bash starts)
I'm running the latest of everything Cygwin 1.7 (see below). When I start the Xwin server from the Windows shortcut: D:\Cygwin\bin\run.exe /usr/bin/startxwin.bat I see a bash.exe process running, but no X window comes up, as per: REM Make sure XWin is ready to accept connections before proceeding %RUN% checkX -wait -d %DISPLAY% -t 12 REM Startup an xterm, using bash as the shell. %RUN% xterm -e /usr/bin/bash -l Anyone else notice this? The problem is the same on my laptop at work running WinXP, as well as my home system running Windows 7 - Jim # cygcheck -c | egrep cyg|x cygrunsrv1.34-1 OK cygutils 1.4.0-1 OK cygwin 1.7.0-65OK cygwin-doc 1.5-1 OK expat2.0.1-1 OK gettext 0.17-11 OK libexpat12.0.1-1 OK libexpat1-devel 2.0.1-1 OK libpixman1_0 0.16.2-1OK libxcb1 1.4-2 OK libXext6 1.1.1-1 OK libxkbfile1 1.0.6-1 OK libxml2 2.7.4-1 OK lynx 2.8.5-4 OK texinfo 4.13-3 OK util-linux 2.14.1-1OK xauth1.0.4-1 OK xcursor-themes 1.0.2-1 OK xemacs-emacs-common 21.4.22-1 OK xinit1.2.0-1 OK xkbcomp 1.1.1-1 OK xkeyboard-config 1.7-1 OK xmodmap 1.0.4-1 OK xorg-server 1.7.1-3 OK xrdb 1.0.6-1 OK xterm250-1 OK -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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/
cygwinx 1.7 beta - crashes runing virt-manager
Connecting to F12 running Gnome, running python based applications causes Xwin to segfault. For example, running virt-manager kills Xwin immediately. Most of the F12 admin tools exhibit this behavior. I tried -swcursor based on some old discussions on this list regarding Java crashing Xwin (from 2007). Doesn't help now :( Anyone have suggestions? I'm running Xwin on Windows 7 Premium - 64 bit on an AMD X2.; F12 X86_64 on I7. The .xsession log from F12: (gnome-panel:10403): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed (gnome-panel:10403): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed (gnome-panel:10403): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed (gnome-panel:10403): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed (gnome-panel:10403): GLib-GObject-CRITICAL **: g_object_run_dispose: assertion `G_IS_OBJECT (object)' failed gnome-terminal: Fatal IO error 11 (Resource temporarily unavailable) on X server 10.0.0.11:0 The Xlog file from Xwin: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: xwin :0 -query 10.0.0.1 -logverbose 3 -noclipboard -from 10.0.0.11 -swcursor ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1680 h 1050 winInitializeDefaultScreens - Returning 2009-11-19 22:41:15 OsVendorInit - Creating bogus screen 0 2009-11-19 22:41:22 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 2009-11-19 22:41:22 winValidateArgs - Returning. 2009-11-19 22:41:22 (II) xorg.conf is not supported 2009-11-19 22:41:22 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information 2009-11-19 22:41:22 winPrefsLoadPreferences: /etc/X11/system.XWinrc 2009-11-19 22:41:22 LoadPreferences: Done parsing the configuration file... 2009-11-19 22:41:22 winGetDisplay: DISPLAY=:0.0 2009-11-19 22:41:22 winDetectSupportedEngines - Windows NT/2000/XP 2009-11-19 22:41:22 winDetectSupportedEngines - DirectDraw installed 2009-11-19 22:41:22 winDetectSupportedEngines - DirectDraw4 installed 2009-11-19 22:41:22 winDetectSupportedEngines - Returning, supported engines 0007 2009-11-19 22:41:22 winScreenInit - dwWidth: 1680 dwHeight: 1050 2009-11-19 22:41:22 winSetEngine - Using Shadow DirectDraw NonLocking 2009-11-19 22:41:22 winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per pixel 2009-11-19 22:41:22 winCreateBoundingWindowWindowed - User w: 1680 h: 1050 2009-11-19 22:41:22 winCreateBoundingWindowWindowed - Current w: 1680 h: 1050 2009-11-19 22:41:22 winAdjustForAutoHide - Original WorkArea: 0 0 1050 1680 2009-11-19 22:41:22 winAdjustForAutoHide - Taskbar is auto hide 2009-11-19 22:41:22 winAdjustForAutoHide - Found BOTTOM auto-hide taskbar 2009-11-19 22:41:22 winAdjustForAutoHide - Adjusted WorkArea: 0 0 1049 1680 2009-11-19 22:41:22 winCreateBoundingWindowWindowed - WindowClient w 1674 h 1021 r 1674 l 0 b 1021 t 0 2009-11-19 22:41:22 winWindowProc - WM_ACTIVATEAPP 2009-11-19 22:41:22 winCreateBoundingWindowWindowed - Returning 2009-11-19 22:41:22 winCreatePrimarySurfaceShadowDDNL - Creating primary surface 2009-11-19 22:41:22 winCreatePrimarySurfaceShadowDDNL - Created primary surface 2009-11-19 22:41:22 winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface 2009-11-19 22:41:22 winAllocateFBShadowDDNL - lPitch: 6696 2009-11-19 22:41:22 winAllocateFBShadowDDNL - Created shadow pitch: 6696 2009-11-19 22:41:22 winAllocateFBShadowDDNL - Created shadow stride: 1674 2009-11-19 22:41:22 winFinishScreenInitFB - Masks: 00ff ff00 00ff 2009-11-19 22:41:22 winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 2009-11-19 22:41:22 winRandRInit () 2009-11-19 22:41:22 winCreateDefColormap - Deferring to fbCreateDefColormap () 2009-11-19 22:41:22 winFinishScreenInitFB - returning 2009-11-19 22:41:22 winScreenInit - Using software cursor 2009-11-19 22:41:22 Screen 0 added at XINERAMA coordinate (0,0). 2009-11-19 22:41:22 winScreenInit - returning 2009-11-19 22:41:22 winGenerateAuthorization - GenerateAuthorization success! AuthDataLen: 16 AuthData: Ö�SOˆ~ê4€F1·£`¿ 2009-11-19 22:41:22 InitOutput - Returning. 2009-11-19 22:41:22 MIT-SHM extension disabled due to lack of kernel support 2009-11-19 22:41:22 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel 2009-11-19 22:41:22 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so 2009-11-19 22:41:22 (II) GLX: Initialized DRISWRAST GL provider for screen 0 2009-11-19 22:41:22 winPointerWarpCursor - Discarding first warp: 837 510 2009-11-19 22:41:22 (--) 8 mouse buttons found 2009-11-19 22:41:22 (--) Setting autorepeat to delay=500, rate=31 2009-11-19
Re: Problem with new xinit - console window doesn't open (but bash starts)
More info: If I run startxwin.bat from a CMD.exe command line, the bash console xterm opens just fine. I only have problems starting it from the shortcut. I do see some interesting things in the log file, however: 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 II) GLX: Initialized DRISWRAST GL provider for screen 0 [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! Warning: Missing charsets in String to FontSet conversion None of the compatibility settings are checked in the Windows shortcut. I've attached the Xwin.0.log file - Jim On 11/19/2009 8:57 PM, Jim Reisert AD1C wrote: I'm running the latest of everything Cygwin 1.7 (see below). When I start the Xwin server from the Windows shortcut: D:\Cygwin\bin\run.exe /usr/bin/startxwin.bat I see a bash.exe process running, but no X window comes up, as per: REM Make sure XWin is ready to accept connections before proceeding %RUN% checkX -wait -d %DISPLAY% -t 12 REM Startup an xterm, using bash as the shell. %RUN% xterm -e /usr/bin/bash -l Anyone else notice this? The problem is the same on my laptop at work running WinXP, as well as my home system running Windows 7 - Jim # cygcheck -c | egrep cyg|x cygrunsrv 1.34-1 OK cygutils 1.4.0-1 OK cygwin 1.7.0-65 OK cygwin-doc 1.5-1 OK expat 2.0.1-1 OK gettext 0.17-11 OK libexpat1 2.0.1-1 OK libexpat1-devel 2.0.1-1 OK libpixman1_0 0.16.2-1 OK libxcb1 1.4-2 OK libXext6 1.1.1-1 OK libxkbfile1 1.0.6-1 OK libxml2 2.7.4-1 OK lynx 2.8.5-4 OK texinfo 4.13-3 OK util-linux 2.14.1-1 OK xauth 1.0.4-1 OK xcursor-themes 1.0.2-1 OK xemacs-emacs-common 21.4.22-1 OK xinit 1.2.0-1 OK xkbcomp 1.1.1-1 OK xkeyboard-config 1.7-1 OK xmodmap 1.0.4-1 OK xorg-server 1.7.1-3 OK xrdb 1.0.6-1 OK xterm 250-1 OK -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 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 1680 h 1050 winInitializeDefaultScreens - Returning 2009-11-19 21:06:08 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 2009-11-19 21:06:08 (II) xorg.conf is not supported 2009-11-19 21:06:08 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information 2009-11-19 21:06:08 winPrefsLoadPreferences: /cygdrive/d/Home/.XWinrc 2009-11-19 21:06:08 LoadPreferences: Done parsing the configuration file... 2009-11-19 21:06:08 winGetDisplay: DISPLAY=:0.0 2009-11-19 21:06:08 winDetectSupportedEngines - Windows NT/2000/XP 2009-11-19 21:06:08 winDetectSupportedEngines - DirectDraw installed 2009-11-19 21:06:08 winDetectSupportedEngines - DirectDraw4 installed 2009-11-19 21:06:08 winDetectSupportedEngines - Returning, supported engines 0007 2009-11-19 21:06:08 winSetEngine - Multi Window or Rootless = ShadowGDI 2009-11-19 21:06:08 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel 2009-11-19 21:06:08 winAllocateFBShadowGDI - Creating DIB with width: 1680 height: 1050 depth: 32 2009-11-19 21:06:08 winFinishScreenInitFB - Masks: 00ff ff00 00ff 2009-11-19 21:06:08 winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 2009-11-19 21:06:08 null screen fn ReparentWindow 2009-11-19 21:06:08 null screen fn RestackWindow 2009-11-19 21:06:08 InitQueue - Calling pthread_mutex_init 2009-11-19 21:06:08 InitQueue - pthread_mutex_init returned 2009-11-19 21:06:08 InitQueue - Calling pthread_cond_init 2009-11-19 21:06:08 InitQueue - pthread_cond_init returned 2009-11-19 21:06:08 winInitMultiWindowWM - Hello 2009-11-19 21:06:08 Screen 0 added at XINERAMA coordinate (0,0). 2009-11-19 21:06:08 winMultiWindowXMsgProc - Hello 2009-11-19 21:06:08 winInitMultiWindowWM - Calling pthread_mutex_lock () 2009-11-19 21:06:08 winMultiWindowXMsgProc - Calling pthread_mutex_lock () 2009-11-19 21:06:08 MIT-SHM extension disabled due to lack of kernel support 2009-11-19 21:06:08 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel 2009-11-19 21:06:08 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so 2009-11-19 21:06:08 (II) GLX: Initialized DRISWRAST GL provider for screen 0 2009-11-19 21:06:08 [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! 2009-11-19 21:06:08 [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! 2009-11-19 21:06:08 [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! 2009-11-19
Re: Problem with new xinit - console window doesn't open (but bash starts)
The missing charsets message is symptomatic of not having the patches needed to a couple of X config files concerning UTF-8. If you apply the path, which I think is in the latest Xorg files, then that problem should be fixed. (Assuming you set LANG. You can also try LANG=C as a temporary workaround.) -- Eliot Moss -- 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/
