SHM extension fails to start
Hi, When XWin starts, I see the following error message in the XWin log file: MIT-SHM extension disabled due to lack of kernel support However, the ipc-deamon2 deamon has been installed: 3504 cw 8 0 13668 192412 S29.6 0.0 39:56 XWin 560 SYSTEM 8 0 2776 314848 S 0.0 0.1 0:01 sshd 3756 SYSTEM 8 0 2188 206844 S 0.0 0.0 0:00 inetd 3744 SYSTEM 8 0 2628 268868 S 0.0 0.1 0:00 inetd 2980 cw 8 0 3060 265292 S 0.0 0.1 1:01 blackbox 1756 SYSTEM 8 0 2308 6312 4084 S 0.0 0.3 0:00 ipc-daemon2 3544 cw 8 0 2492 57624 S 0.0 0.0 0:02 bash 464 SYSTEM 8 0 2248 232448 S 0.0 0.1 0:00 cygrunsrv According to the Cygwin/X users guide: this should be supported if ipc-daemon2 is running. Attached are also the results of xdpyinfo Am I missing something? Will the SHM extension improve performance of the X server? Best Regards and thanks, Charles Dr. Charles L. Werner Gamma Remote Sensing AG Thunstrasse 130 CH-3074 Muri b. Bern, Switzerland Tel: +41 31 951 70 05 FAX: +41 31 951 70 08 http://www.gamma-rs.ch Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-1 Contact: [EMAIL PROTECTED] XWin was started with the following command line: XWin -scrollbars ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1600 h 1200 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winValidateArgs - Returning. (II) XF86Config is not supported. See http://x.cygwin.com/docs/faq/cygwin-xfree-faq.html for more information winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1600 dwHeight: 1200 winSetEngine - Multi Window or Rootless = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per pixel winCreateBoundingWindowWindowed - User w: 1600 h: 1200 winCreateBoundingWindowWindowed - Current w: 1600 h: 1200 winAdjustForAutoHide - Original WorkArea: 0 0 1170 1600 winAdjustForAutoHide - Adjusted WorkArea: 0 0 1170 1600 winCreateBoundingWindowWindowed - WindowClient w 1592 h 1143 r 1592 l 0 b 1143 t 0 winWindowProc - WM_SIZE - window w: 1600 h: 1170, new client area w: 1592 h: 1143 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1592 height: 1143 depth: 16 winAllocateFBShadowGDI - Dibsection width: 1592 height: 1143 depth: 16 size image: 3639312 winAllocateFBShadowGDI - Created shadow stride: 1592 winFinishScreenInitFB - Masks: f800 07e0 001f winInitVisualsShadowGDI - Masks f800 07e0 001f BPRGB 6 d 16 bpp 16 winRandRInit () winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning 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) (EE) Keyboardlayout US (0409) is unknown Rules = xorg Model = pc101 Layout = us Variant = (null) Options = (null) 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/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 796 571 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned winProcEstablishConnection - Hello winProcEstablishConnection - Clipboard is not enabled, returning. winWindowProc - WM_SIZE - window w: 1600 h: 1170, new client area w: 1592 h: 1143 winWindowProc - WM_SIZE - window w: 1600 h: 1170, new client area w: 1592 h: 1143 winWindowProc - WM_SIZE - window w: 1600 h: 1170, new client area w: 1592 h: 1143 winWindowProc - WM_SIZE - window w: 1600 h: 1170, new client area w: 1592 h: 1143 name of display::0.0 version number:11.0 vendor string:The Cygwin/X Project vendor release number:6070 maximum request size: 16777212 bytes motion buffer size: 256 bitmap unit, bit order, padding:32, LSBFirst, 32 image byte order:LSBFirst number of supported pixmap formats:7 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 4, bits_per_pixel 8, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 15, bits_per_pixel 16, scanline_pad 32 depth 16, bits_per_pixel 16, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 depth 32, bits_per_pixel 32, scanline_pad 32 keycode range:minimum 8, maximum 255 focus: window 0x62, revert to PointerRoot number of extensions:23 BIG-REQUESTS
Clipboard problems
Hello. I've got some problems with clipboard integration since XWin version 4.3.0-62 or 4.3.0-64 i think (not 100% sure, but it dates of late march of beginning of april, and i usually update really regularly my installations). I run kde-cygwin.3.1.4 but I don't know if this is relevant; Simply, the trouble I have occures always in this environement, as I've not observed it outside kde (but I've not much tested it). So, my problem it that I can't use Windows clipboard anymore when I've got XWin running!!! I can copy/paste inside X11 applications as normal behavior I can copy from X11 and paste to Windows applications bash-2.05b But I can copy from Windows applications neither to Windows application, nor to X11 ones. And my /tmp/XWin.log looks like : Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-1 Contact: [EMAIL PROTECTED] XWin was started with the following command line: /usr/X11R6/bin/XWin :0 -noreset -ac -nowinkill -nodecoration -lesspointer -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winValidateArgs - Returning. (II) XF86Config is not supported. See http://x.cygwin.com/docs/faq/cygwin-xfree-faq.html for more information winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1280 dwHeight: 1024 winSetEngine - Multi Window or Rootless = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 996 1280 winAdjustForAutoHide - Adjusted WorkArea: 0 0 996 1280 winCreateBoundingWindowWindowed - WindowClient w 1280 h 996 r 1280 l 0 b 996 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 996 depth: 32 winAllocateFBShadowGDI - Dibsection width: 1280 height: 996 depth: 32 size image: 5099520 winAllocateFBShadowGDI - Created shadow stride: 1280 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 winRandRInit () winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - returning winScreenInit - returning 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: 040C (040c) (--) Using preset keyboard for French (Standard) (40c), type 81 Rules = xorg Model = pc105 Layout = fr Variant = (null) Options = (null) 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/CID/, removing from list! winPointerWarpCursor - Discarding first warp: 640 498 winBlockHandler - Releasing pmServerStarted winBlockHandler - pthread_mutex_unlock () returned winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - DISPLAY=127.0.0.1:0.0 winClipboardProc - XOpenDisplay () returned and successfully opened the display. winClipboardWindowProc - WM_DRAWCLIPBOARD - Initializing - Returning. winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) winClipboardErrorHandler - ERROR: BadValue (integer parameter out of range for operation) [12000 more idetical lines
Re: SHM extension fails to start
On Thu, 8 Apr 2004, Charles L. Werner wrote: Hi, When XWin starts, I see the following error message in the XWin log file: MIT-SHM extension disabled due to lack of kernel support However, the ipc-deamon2 deamon has been installed: 3504 cw 8 0 13668 192412 S29.6 0.0 39:56 XWin 560 SYSTEM 8 0 2776 314848 S 0.0 0.1 0:01 sshd 3756 SYSTEM 8 0 2188 206844 S 0.0 0.0 0:00 inetd 3744 SYSTEM 8 0 2628 268868 S 0.0 0.1 0:00 inetd 2980 cw 8 0 3060 265292 S 0.0 0.1 1:01 blackbox 1756 SYSTEM 8 0 2308 6312 4084 S 0.0 0.3 0:00 ipc-daemon2 3544 cw 8 0 2492 57624 S 0.0 0.0 0:02 bash 464 SYSTEM 8 0 2248 232448 S 0.0 0.1 0:00 cygrunsrv According to the Cygwin/X users guide: this should be supported if ipc-daemon2 is running. We have to update this. Attached are also the results of xdpyinfo Am I missing something? Will the SHM extension improve performance of the X server? XWin now uses the cygserver support included in cygwin1.dll. try if starting XWin works with CYGWIN=server XWin.exe bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Double-clicking on tray icon
Double-clicking on the 'X' icon in the Windows system tray brings up a dialogue box asking if you want to kill the X server, but I think it should bring the X window to the foreground (if single-window mode). -- Ed Avis [EMAIL PROTECTED]
Re: SHM extension fails to start
Charles L. Werner wrote: I tried the suggested command from the Cygwin bash command line and the SHM extension still fails: I tried to find documentation on cygserver, but all there is dead links in the cygwin users guide. I assume the CYGWIN environment variable is being set by suggested command. There is no info for this option in the users guide for the CYGWIN environment variable... Since it had no effect is the environment variable setting incorrect? You have to launch cygserver just like you launch ipc-daemon2, except cygserver is in /usr/sbin instead of /usr/bin so you have to explicitly reference it unless /usr/sbin has been manually added to your path: /usr/sbin/cygserver Then launch CYGWIN=server XWin. Harold
Re: Problem with truetype fonts caused by not building FreeType module?
Lev S Bishop wrote: (Replying to my own message) I messed about with the host.def.in and got it to sort of work. My host.def.in is: #define BuildFreeType YES #define BuildServersOnlyYES #define XnestServer NO #define XVirtualFramebufferServer NO #define BuildXWinMultiWindowExtWM NO #define EtcX11Directory @sysconfdir@ #define ProjectRoot @prefix@ I also had to grab xc/lib/font/FreeType from the freedesktop cvs (tag CYGWIN if that's relevant). (Using the latest src packages from setup for the other sources). Now you are getting somewhere... the implication of BuildFreeType NO is that you are going to use the installed version since we set HasFreeType YES, but this does not appear to be the case. We'll either have to fix the build rules or just set BuildFreeType to YES but not actually include it in our distribution, just as we do for Xft. Harold
Re: Problem with truetype fonts caused by not building FreeType module?
Harold wrote: Now you are getting somewhere... the implication of BuildFreeType NO is that you are going to use the installed version since we set HasFreeType YES, but this does not appear to be the case. We'll either have to fix the build rules or just set BuildFreeType to YES but not actually include it in our distribution, just as we do for Xft. I think you have the wrong idea about FreeType backend. My understanding is that this is one of the modules which implement server-side truetype (the other being X-TrueType, the xtt module - only one of the two is allowed, and X-TrueType is scheduled for demolition in the next release). It's built *around* the FreeType library (which is what we say we have by asserting HasFreeType YES...) but it's not the same thing as having the library. I think all we need to do is set BuildFreeType to yes - the resulting module gets statically linked into libXfont.a (rather than being a loadable module, as it would be in many other X servers, since we don't do loadable modules on cygwin/x), and from there gets linked into XWin.exe and xfs.exe (I understand xfs.exe is currently non-functional, though), and perhaps some other places? I could be wrong about all this but the release notes seem to back me up: http://freedesktop.org/~xorg/X11R6.7.0/doc/RELNOTES6.html#41 Lev
Re: SHM extension fails to start
Charles L. Werner wrote: I tried to find documentation on cygserver, but all there is dead links in the cygwin users guide. I assume the CYGWIN environment variable is being set by suggested command. There is no info for this option in the users guide for the CYGWIN environment variable... Since it had no effect is the environment variable setting incorrect? See /usr/share/doc//Cygwin/cygserver.README. If you're using NT/2000/XP/2003, you can install cygserver as a service by running /usr/bin/cygserver-config. Dave
Re: SHM extension fails to start
On Apr 8 17:30, Charles L. Werner wrote: I tried the suggested command from the Cygwin bash command line and the SHM extension still fails: I tried to find documentation on cygserver, but all there is dead links in the cygwin users guide. I assume the CYGWIN environment variable is being set by suggested command. There is no info for this option in the users guide for the CYGWIN I'll upload the missing html file in a minute. In the meantime you can find the same documentation in /usr/share/doc/Cygwin/cygserver.README on your local hard disk. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
Do I need XFree86 now that XOrg-x11 is the default X-windowing system?
Do I need XFree86 now that XOrg-x11 is the default X-windowing system? When I do a fresh install, I see that a couple of packages in the removed packages section are still selected. These are XFree86-base and XFree86-bin. Are these really necessary is I install xorg-x11-base and xorg-xll-bin?
Re: Problem with truetype fonts caused by not building FreeType module?
Lev, Lev S Bishop wrote: Harold wrote: Now you are getting somewhere... the implication of BuildFreeType NO is that you are going to use the installed version since we set HasFreeType YES, but this does not appear to be the case. We'll either have to fix the build rules or just set BuildFreeType to YES but not actually include it in our distribution, just as we do for Xft. I think you have the wrong idea about FreeType backend. My understanding is that this is one of the modules which implement server-side truetype (the other being X-TrueType, the xtt module - only one of the two is allowed, and X-TrueType is scheduled for demolition in the next release). It's built *around* the FreeType library (which is what we say we have by asserting HasFreeType YES...) but it's not the same thing as having the library. I think all we need to do is set BuildFreeType to yes Hmm... I was thinking we were setting BuildFreetype to NO and BuildFontconfig to NO in cygwin.cf to prevent these already installed libraries from being compiled, when in fact we were not doing so. You are correct that no longer including xorg.cf (or xfree86.cf) caused the default for BuildFreetype and BuildFontconfig to flip from YES to NO and you are correct that these signal if programs should link against these libraries. There are separate flags call BuildFreetype2Library and BuildFontconfigLibrary that we need to set to NO to prevent just the library from being built, but those should actually pickup the correct defaults from X11.tmpl since we set HasFreetype2 and HasFontconfig to YES. - the resulting module gets statically linked into libXfont.a (rather than being a loadable module, as it would be in many other X servers, since we don't do loadable modules on cygwin/x), and from there gets linked into XWin.exe and xfs.exe (I understand xfs.exe is currently non-functional, though), and perhaps some other places? Regarding the static linking, that is not correct. I had noticed recently that XWin.exe was no longer linked to cygfreetype-6.dll (do a 'cygcheck XWin.exe' to find out what DLLs are being linked to) and was wondering what happened. I could be wrong about all this but the release notes seem to back me up: http://freedesktop.org/~xorg/X11R6.7.0/doc/RELNOTES6.html#41 No, you're not wrong, you helped me find the correct flags we need to set and you helped find the reason why the defaults for some of these flags has changed. Yay, now I can do a complete rebuild. :) Harold
Re: Do I need XFree86 now that XOrg-x11 is the default X-windowing system?
Anybody wrote: Do I need XFree86 now that XOrg-x11 is the default X-windowing system? When I do a fresh install, I see that a couple of packages in the removed packages section are still selected. These are XFree86-base and XFree86-bin. Are these really necessary is I install xorg-x11-base and xorg-xll-bin? Those packages are all empty, they are just used to force removal of the files from those packages before the files from the xorg-x11-* packages are installed. If we didn't do this and you later removed the XFree86-* packages you'd end up deleting files from the xorg-x11-* packages, which you don't want to do. In other words, just ignore the XFree86-* packages in the ZZZRemovedPackages category, they contain no files and don't matter to you anymore. Harold
6.7.0.0 XWin w/out -nodecoration running in background doesn't display anything
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, i just upgraded to the new X11 (X.org) version of cygwin/X (Release 6.7.0.0-1. I use XWin to connect via XDMCP to several linux server. My previous used startup script is a MS-DOS batch file in which i fire-up XWin.exe with start XWin.exe -fp and so on. This is all ok. I get an connection and can work. But with this new X11 release i get a additional window with all the status and error messages from XWin. Until now XWin run in background when startet by the DOS start-command. When i try the new cygwin command run, as used in the sample startxdmcp.bat, i'm only can do this by supplying the -nodecoration parm. Without this param, i do not see any X-client nor the login screen from kde (in my case). Even XWin runs an has a connection to the server. I see the X in the systray, right clicking an choosing Exit reminds me that three clients connected. Shortly said: when you want to run X in a M$-Windows Window (let - -nodecorations away) then you can't run XWin in background. As i use up to 6 XDMCP connections to different linux servers with different screen sizes and resolutions, i now have 12 Windows on the desk (or taskbar, when minimized). Is there a way to get the old behavor back? Testcase: - - run XWin.exe -query HOST = you see the X in the systray but nothing else. - - run XWin.exe -query HOST -nodecorations = you get a fullscreen login screen to the server - - start XWin.exe -query HOST = you get the servers login screen in a Windooze window and an _additional_ console window with the text messages from XWin.exe - - start /b XWin.exe -query HOST = same as run XWin Regards - -- Rudolf Kollien email: [EMAIL PROTECTED] * Never trust a operating system you have no sources for * Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions. * -BEGIN PGP SIGNATURE- iD8DBQFAdaMqzOHTWsKaqE0RAjBzAJ4nmwvsiRCfJsPwd78r2V/F9B3MKgCfa/R9 1WgN4gBq5vhfKrE6ALKSbQ8= =OCSD -END PGP SIGNATURE-
Re: 6.7.0.0 XWin w/out -nodecoration running in background doesn't display anything
Yeah, you can't use run in the batch file... you have to use start instead. I noticed this right before the release, but I don't have a permanent solution yet. We had to switch from start to run because start doesn't prevent a DOS box from being displayed and because we switched XWin.exe from not displaying a DOS box by default to displaying a DOS box by default. The reason for this is that the new logging facility allows sending messages both to standard output and to a log file if one is opened sometime after the server starts (message have to be cached until that point since they would otherwise be lost since the log file isn't open yet). The nicest thing about this is that people running XWin -help will now see the help output instead of having to open /tmp/XWin.log to see the output. What is the permanent solution to the problem? I don't know. I think it may be time to finish writing the batch file that just launches a bash shell script, but I haven't got time to work on that today. Harold Rudolf Kollien wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, i just upgraded to the new X11 (X.org) version of cygwin/X (Release 6.7.0.0-1. I use XWin to connect via XDMCP to several linux server. My previous used startup script is a MS-DOS batch file in which i fire-up XWin.exe with start XWin.exe -fp and so on. This is all ok. I get an connection and can work. But with this new X11 release i get a additional window with all the status and error messages from XWin. Until now XWin run in background when startet by the DOS start-command. When i try the new cygwin command run, as used in the sample startxdmcp.bat, i'm only can do this by supplying the -nodecoration parm. Without this param, i do not see any X-client nor the login screen from kde (in my case). Even XWin runs an has a connection to the server. I see the X in the systray, right clicking an choosing Exit reminds me that three clients connected. Shortly said: when you want to run X in a M$-Windows Window (let - -nodecorations away) then you can't run XWin in background. As i use up to 6 XDMCP connections to different linux servers with different screen sizes and resolutions, i now have 12 Windows on the desk (or taskbar, when minimized). Is there a way to get the old behavor back? Testcase: - - run XWin.exe -query HOST = you see the X in the systray but nothing else. - - run XWin.exe -query HOST -nodecorations = you get a fullscreen login screen to the server - - start XWin.exe -query HOST = you get the servers login screen in a Windooze window and an _additional_ console window with the text messages from XWin.exe - - start /b XWin.exe -query HOST = same as run XWin Regards - -- Rudolf Kollien email: [EMAIL PROTECTED] * Never trust a operating system you have no sources for * Buying an operating system without source is like buying a self-assembly Space Shuttle with no instructions. * -BEGIN PGP SIGNATURE- iD8DBQFAdaMqzOHTWsKaqE0RAjBzAJ4nmwvsiRCfJsPwd78r2V/F9B3MKgCfa/R9 1WgN4gBq5vhfKrE6ALKSbQ8= =OCSD -END PGP SIGNATURE-
Re: Problem with truetype fonts caused by not building FreeType module?
Harold wrote: Lev S Bishop wrote: - the resulting module gets statically linked into libXfont.a (rather than being a loadable module, as it would be in many other X servers, since we don't do loadable modules on cygwin/x), and from there gets linked into XWin.exe and xfs.exe (I understand xfs.exe is currently non-functional, though), and perhaps some other places? Regarding the static linking, that is not correct. I had noticed recently that XWin.exe was no longer linked to cygfreetype-6.dll (do a 'cygcheck XWin.exe' to find out what DLLs are being linked to) and was wondering what happened. No, I am sure that I am correct about the static linking, but I was not very clear what I was saying. There are *two* things called freetype under discussion. There is the freetype library (the thing that is available from www.freetype.org, is independent of X, and is contained in cygfreetype-6.dll from the package libfreetype26-2.1.5-1) and there is the freetype module (aka FreeType backend, formerly known as xfsft, this is the thing that's part of the x server). From now on I'll call the former freetype the freetype2 library and the latter the freetype backend. The freetype backend deals with making truetype fonts look and feel to the rest of the x server like all other x core fonts, XLFDs, fonts.dir, fonts.alias, etc) but to do the actual rendering it calls upon the freetype2 library. You can think of it as a wrapper for the freetype2 library. There is a version of the freetype2 library in the xc source tree, but we don't want to use it because we prefer to use a seperately installed (more up to date) version, so we set HasFreeType2 YES (typo in my earlier email, missed off the 2 on HasFreeType2). The freetype2 library can be dynamically linked (its cygfreetype6.dll). Following me so far? Now, here's what I was really getting at: the server architecture is such that certain parts of the X server are loadable modules -- whether or not they get loaded into the server is configured *at runtime* by looking in the Module section of the config file (xorg.conf), for lines like 'Load type1' to load the type 1 font rasterizer, etc (this is as opposed to load time dynamic linking, which is what cygcheck tells you about). See: http://freedesktop.org/~xorg/X11R6.7.0/doc/xorg.conf.5.html#sect5 However, cygwin/x doesn't support loadable modules like that (we don't set DoLoadableServer YES, and we don't have a config file to read even if we did) so the freetype backend gets built statically into libXfont.a, and libXfont.a is linked into XWin.exe. So the path is like this for cygwin/x: XWin.exe is linked to libXfont.a, which includes the freetype backend, which depends on the freetype2 library. So the ultimate situation is that XWin.exe is statically linked to the freetype backend but dynamically linked to the freetype2 library. (With recent builds, the situation was: XWin.exe is linked to libXfont.a, which doesn't include the freetype backend, so nothing in XWin.exe depends on the freetype2 library, so cygcheck on XWin.exe doesn't report cygfreetype6.dll). Whether or not we use the freetype backend is controlled by the build switch: BuildFreeType (note capitalization). The freetype2 library is controlled by the switch HasFreetype2. We already have HasFreetype2 YES, but we need to add BuildFreeType YES. The switches control the building of completely orthogonal branches of the source tree. I hope that was clear? Harold: you mentioned something about BuildFontconfig. There is no such switch. There is only a switch BuildFontconfigLibrary. This gets its default (correctly) due to our setting HasFontconfig YES. You don't need to change anything here. Anyway, we're talking about server-side fonts here, which don't use fontconfig. The client-side font mechanism does use fontconfig, and that side of things is working perfectly right now -- no need to mess about with that. Lev
Re: Problem with truetype fonts caused by not building FreeType module?
Lev S Bishop wrote: Harold wrote: Lev S Bishop wrote: - the resulting module gets statically linked into libXfont.a (rather than being a loadable module, as it would be in many other X servers, since we don't do loadable modules on cygwin/x), and from there gets linked into XWin.exe and xfs.exe (I understand xfs.exe is currently non-functional, though), and perhaps some other places? Regarding the static linking, that is not correct. I had noticed recently that XWin.exe was no longer linked to cygfreetype-6.dll (do a 'cygcheck XWin.exe' to find out what DLLs are being linked to) and was wondering what happened. No, I am sure that I am correct about the static linking, but I was not very clear what I was saying. There are *two* things called freetype under discussion. There is the freetype library (the thing that is available from www.freetype.org, is independent of X, and is contained in cygfreetype-6.dll from the package libfreetype26-2.1.5-1) and there is the freetype module (aka FreeType backend, formerly known as xfsft, this is the thing that's part of the x server). From now on I'll call the former freetype the freetype2 library and the latter the freetype backend. Uhh... you could have just called it the freetype backend in the font library. Yes, the font library is always statically linked into the server due to a limitation in the way it was implemented. I don't disagree that there is a freetype portion of the font library and that it was not being built. The freetype backend deals with making truetype fonts look and feel to the rest of the x server like all other x core fonts, XLFDs, fonts.dir, fonts.alias, etc) but to do the actual rendering it calls upon the freetype2 library. You can think of it as a wrapper for the freetype2 library. There is a version of the freetype2 library in the xc source tree, but we don't want to use it because we prefer to use a seperately installed (more up to date) version, so we set HasFreeType2 YES (typo in my earlier email, missed off the 2 on HasFreeType2). The freetype2 library can be dynamically linked (its cygfreetype6.dll). Yup. Now, here's what I was really getting at: the server architecture is such that certain parts of the X server are loadable modules -- whether or not they get loaded into the server is configured *at runtime* by looking in the Module section of the config file (xorg.conf), for lines like 'Load type1' to load the type 1 font rasterizer, etc (this is as opposed to load time dynamic linking, which is what cygcheck tells you about). See: http://freedesktop.org/~xorg/X11R6.7.0/doc/xorg.conf.5.html#sect5 However, cygwin/x doesn't support loadable modules like that (we don't set DoLoadableServer YES, and we don't have a config file to read even if we did) so the freetype backend gets built statically into libXfont.a, and libXfont.a is linked into XWin.exe. Right, I don't dispute that, but your earlier message was really confusing the names of things and we were not talking about the same thing. Whether or not we use the freetype backend is controlled by the build switch: BuildFreeType (note capitalization). The freetype2 library is controlled by the switch HasFreetype2. We already have HasFreetype2 YES, but we need to add BuildFreeType YES. The switches control the building of completely orthogonal branches of the source tree. Right, that is what I said. I said that no longer including xorg.cf some time ago caused the BuildFreeType flag to start defaulting to NO instead of its previous YES. And I also credited you with discovering that the flag doesn't control building the library but instead controls whether the other clients and libraries in the tree use freetype and whether or not any code dependent upon freetype is built. What more do you want? You must not have read the end of my last message very clearly. Harold: you mentioned something about BuildFontconfig. There is no such switch. I don't care, you know what I meant. I don't have time to read ten files for each sentence I write in these really long and trying emails. That is why I would prefer that we just converse in IRC about this... it is a lot easier on me. Harold
Problems when try to start cygwin
Hi, i tried to start cygwin but I am find some fatal problems. When I try to start with startx command a message is appearing: 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.7.0.0-1 Contact:[EMAIL PROTECTED] Xwin was started with the following command-line X :0 Could you help me on this ensue Thanks a lot Paulo Coelho Support Engineer Mobile: +55 21 8153 9227 Fax: +551 21 2532 9219 e-mail:[EMAIL PROTECTED]
Re: Problems when try to start cygwin
Did you read the message? You should be looking at /tmp/XWin.log and if you expect us to help you should be sending in /tmp/XWin.log. Harold Paulo Coelho wrote: Hi, i tried to start cygwin but I am find some fatal problems. When I try to start with startx command a message is appearing: 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.7.0.0-1 Contact:[EMAIL PROTECTED] Xwin was started with the following command-line X :0 Could you help me on this ensue Thanks a lot Paulo Coelho Support Engineer Mobile: +55 21 8153 9227 Fax: +551 21 2532 9219 e-mail:[EMAIL PROTECTED]
hangs and other pblms with 6.7.0.0-1 release
Hi, Updated today to 6.7.0.0-1 using setup, resulting in a nearly useless XWin: 1. XTerms do not respect sizing/minimize buttons (nothing happens), nor toolbar tab (cannot minimize). 2. XTerm freezes easily (a right-mouse click seems to trigger hang 100% of time). In this state cannot bring to foreground - window is totally non-responsive, X icon in tray is non- responsive. 3. Alt-F4 does not close XWin in this hung state (have to kill based on PID). 4. Alt-F4 does not work when not in hung-state either. Right- click on X icon to kill XWin server (when not in hung state and no open XTerms) results in an illegal operation: XWIN caused an invalid page fault in module CYGWIN1.DLL at 025f:610885ba. Registers: EAX=0267 CS=025f EIP=610885ba EFLGS=00010202 EBX=0202 SS=0267 ESP=031fedb0 EBP=031ff048 ECX=100e05a0 DS=0267 ESI=0020 FS=6717 EDX= ES=0267 EDI=007606c8 GS=70fe Bytes at CS:EIP: ff 77 20 53 66 8b 47 24 8e c0 66 8b 47 28 8e e8 Stack dump: Tail of XWin.log after this fault is: winAboutDlgProc - WM_COMMAND - IDOK or IDCANCEL winDeinitMultiWindowWM - Noting shutdown in progress ddxBeforeReset - Hello winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. ddxBeforeReset - Clipboard thread has exited. winClipboardIOErrorHandler! winDeinitMultiWindowWM - Noting shutdown in progress. Am using on Win98SE system with STB Velocity 128 (NVidia Riva 128) card. Previous XWin worked fine, and am starting up using latest startxwin.sh with no modifications. Shutting down anti- virus and ZoneAlarm makes no difference. No custom startups, and verified mounts are binmode. cygcheck -cv shows no problems (all installed Cygwin SW is current). XWin.log follows when in hung state and had to terminate with a kill -9 (very little activity - xterm came up on startup, a right-click froze the system): Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-1 Contact: [EMAIL PROTECTED] XWin was started with the following command line: XWin -multiwindow -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winValidateArgs - Returning. (II) XF86Config is not supported. See http://x.cygwin.com/docs/faq/cygwin-xfree-faq.html for more information winDetectSupportedEngines - Windows 95/98/Me winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1280 dwHeight: 1024 winSetEngine - Multi Window or Rootless = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 1024 1280 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found BOTTOM auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 0 1023 1280 winCreateBoundingWindowWindowed - WindowClient w 1280 h 1023 r 1280 l 0 b 1023 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1023 depth: 16 winAllocateFBShadowGDI - Dibsection width: 1280 height: -1023 depth: 16 size image: 2618880 winAllocateFBShadowGDI - WEIRDNESS - biHeight still negative: - 1023 winAllocateFBShadowGDI - WEIRDNESS - Flipping biHeight sign winAllocateFBShadowGDI - Created shadow stride: 1280 winFinishScreenInitFB - Masks: 7c00 03e0 001f winInitVisualsShadowGDI - Masks 7c00 03e0 001f BPRGB 5 d 15 bpp 16 winRandRInit () 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. winMultiWindowXMsgProc - Hello winInitMultiWindowWM - Hello winFinishScreenInitFB - returning winMultiWindowXMsgProc - Calling pthread_mutex_lock () winInitMultiWindowWM - Calling pthread_mutex_lock () winScreenInit - returning 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=250, rate=15 (--) winConfigKeyboard - Layout: 0409 (0409) (EE) Keyboardlayout United States 101 (0409) is unknown Rules = xorg Model = pc101 Layout = us Variant = (null) Options = (null) Could not init font path element /usr/X11R6/lib/X11/fonts/TTF/, removing from list! Could not init font path element
Re: hangs and other pblms with 6.7.0.0-1 release
Why don't you try some troubleshooting... try without -clipboard and without -multiwindow and see what happens. Harold Carl Holmberg wrote: Hi, Updated today to 6.7.0.0-1 using setup, resulting in a nearly useless XWin: 1. XTerms do not respect sizing/minimize buttons (nothing happens), nor toolbar tab (cannot minimize). 2. XTerm freezes easily (a right-mouse click seems to trigger hang 100% of time). In this state cannot bring to foreground - window is totally non-responsive, X icon in tray is non- responsive. 3. Alt-F4 does not close XWin in this hung state (have to kill based on PID). 4. Alt-F4 does not work when not in hung-state either. Right- click on X icon to kill XWin server (when not in hung state and no open XTerms) results in an illegal operation: XWIN caused an invalid page fault in module CYGWIN1.DLL at 025f:610885ba. Registers: EAX=0267 CS=025f EIP=610885ba EFLGS=00010202 EBX=0202 SS=0267 ESP=031fedb0 EBP=031ff048 ECX=100e05a0 DS=0267 ESI=0020 FS=6717 EDX= ES=0267 EDI=007606c8 GS=70fe Bytes at CS:EIP: ff 77 20 53 66 8b 47 24 8e c0 66 8b 47 28 8e e8 Stack dump: Tail of XWin.log after this fault is: winAboutDlgProc - WM_COMMAND - IDOK or IDCANCEL winDeinitMultiWindowWM - Noting shutdown in progress ddxBeforeReset - Hello winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. ddxBeforeReset - Clipboard thread has exited. winClipboardIOErrorHandler! winDeinitMultiWindowWM - Noting shutdown in progress. Am using on Win98SE system with STB Velocity 128 (NVidia Riva 128) card. Previous XWin worked fine, and am starting up using latest startxwin.sh with no modifications. Shutting down anti- virus and ZoneAlarm makes no difference. No custom startups, and verified mounts are binmode. cygcheck -cv shows no problems (all installed Cygwin SW is current). XWin.log follows when in hung state and had to terminate with a kill -9 (very little activity - xterm came up on startup, a right-click froze the system): Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-1 Contact: [EMAIL PROTECTED] XWin was started with the following command line: XWin -multiwindow -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winValidateArgs - Returning. (II) XF86Config is not supported. See http://x.cygwin.com/docs/faq/cygwin-xfree-faq.html for more information winDetectSupportedEngines - Windows 95/98/Me winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 0007 winScreenInit - dwWidth: 1280 dwHeight: 1024 winSetEngine - Multi Window or Rootless = ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 16 bits per pixel winCreateBoundingWindowWindowed - User w: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 1024 1280 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found BOTTOM auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 0 1023 1280 winCreateBoundingWindowWindowed - WindowClient w 1280 h 1023 r 1280 l 0 b 1023 t 0 winCreateBoundingWindowWindowed - Returning winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1023 depth: 16 winAllocateFBShadowGDI - Dibsection width: 1280 height: -1023 depth: 16 size image: 2618880 winAllocateFBShadowGDI - WEIRDNESS - biHeight still negative: - 1023 winAllocateFBShadowGDI - WEIRDNESS - Flipping biHeight sign winAllocateFBShadowGDI - Created shadow stride: 1280 winFinishScreenInitFB - Masks: 7c00 03e0 001f winInitVisualsShadowGDI - Masks 7c00 03e0 001f BPRGB 5 d 15 bpp 16 winRandRInit () 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. winMultiWindowXMsgProc - Hello winInitMultiWindowWM - Hello winFinishScreenInitFB - returning winMultiWindowXMsgProc - Calling pthread_mutex_lock () winInitMultiWindowWM - Calling pthread_mutex_lock () winScreenInit - returning 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=250, rate=15 (--) winConfigKeyboard - Layout: 0409 (0409) (EE) Keyboardlayout United States 101 (0409) is unknown Rules = xorg Model = pc101 Layout = us Variant = (null)
Re: Problem with truetype fonts caused by not building FreeType module?
Harold wrote: What more do you want? You must not have read the end of my last message very clearly. I just didn't want you to do a complete rebuild with the wrong flags and break something that worked before or waste your time any more than needed. Just trying to spell everything out as precisely and clearly as I can, because I find it very confusing and I have to be really careful what I say or I end up tripping over myself with multiple meanings for freetype. I find build systems confusing at the best of times, and whoever decided to change the name from xfsft to freetype has a twisted sense of humour :-) Sorry if it came accross as pedantic or patronizing. I can tell you if I tried to discuss this in real time on IRC I'd be utterly incomprehensible. Lev
Re: 6.7.0.0 XWin w/out -nodecoration running in background doesn't display anything
Harold L Hunt II wrote: What is the permanent solution to the problem? I don't know. I think it may be time to finish writing the batch file that just launches a bash shell script, but I haven't got time to work on that today. FWIW, I use setsid to launch without the DOS window. Works fine for me under 2k and XP. - @echo off SET CYGWIN_ROOT=\cygwin SET PATH=.;%CYGWIN_ROOT%\bin;%CYGWIN_ROOT%\usr\X11R6\bin;%PATH% 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 start /min sh -c setsid startxwin.sh - Dave
Re: 6.7.0.0 XWin w/out -nodecoration running in background doesn't display anything
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Harold, sorry, if my question sounds stupid, but... when i can't use run in a batch why there is run used in the startxdmcp.bat? It does the job as requested. But only with -nodecorations. Why can a window without border and titlebar can be used, but a normal window not? I don't want to compare to the old XFree86 (i'm glad about the new project) but once upon a time there where the same problem but was gone long ago. I will try the hint from David Rothenberger with setsid (never heared about). Sound's good. The problem is, that when the controlling window ist closed, the whole X-session gets killed. I i know my users: the will close this unneccessary window. Am Donnerstag, 8. April 2004 21:51 schrieb Harold L Hunt II: Yeah, you can't use run in the batch file... you have to use start instead. I noticed this right before the release, but I don't have a permanent solution yet. We had to switch from start to run because start doesn't prevent a DOS box from being displayed and because we switched XWin.exe from not displaying a DOS box by default to displaying a DOS box by default. The reason for this is that the new logging facility allows sending messages both to standard output and to a log file if one is opened sometime after the server starts (message have to be cached until that point since they would otherwise be lost since the log file isn't open yet). The nicest thing about this is that people running XWin -help will now see the help output instead of having to open /tmp/XWin.log to see the output. What is the permanent solution to the problem? I don't know. I think it may be time to finish writing the batch file that just launches a bash shell script, but I haven't got time to work on that today. Harold -BEGIN PGP SIGNATURE- iD8DBQFAdd0ozOHTWsKaqE0RAhnsAJ9PM2jUh0CdZIvt1sWXXgQ/MAfgkQCgoid1 K7ioTXTqK3f5Pl4V6NIg+MI= =gqaK -END PGP SIGNATURE-
Re: 6.7.0.0 XWin w/out -nodecoration running in background doesn't display anything
Rudolf Kollien wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Harold, sorry, if my question sounds stupid, but... when i can't use run in a batch why there is run used in the startxdmcp.bat? It does the job as requested. But only with -nodecorations. Why can a window without border and titlebar can be used, but a normal window not? I don't want to compare to the old XFree86 (i'm glad about the new project) but once upon a time there where the same problem but was gone long ago. I didn't want to get into the details of what works and what doesn't work. You are right that it seems to work fine with -query, but it doesn't work with other options. I don't know what is going on, but I suspect we can probably fix it by modifying either run.exe or XWin.exe... but the other solution is to just use bash so we can do XWin instead of using start or run. Find whatever solution you need for the time being until it can be fixed properly. Harold
Re: 6.7.0.0 XWin w/out -nodecoration running in background doesn't display anything
Rudolf Kollien wrote: Thanks a lot. Will give it a try. Unfortunately there are some Win98 boxes around. I don't know what setsid doesn't work with Win98, just that I don't have a Win98 box to try it on. The setsid docs don't say anything about it not working for Win98, though. Dave
Re: 6.7.0.0 XWin w/out -nodecoration running in background doesn't display anything
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 As cygwin provides a *nix-like environment, there IS a (shell) solution. Would be the first problem which couldn't worked around :-) Am Freitag, 9. April 2004 01:20 schrieb Harold L Hunt II: Rudolf Kollien wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Harold, sorry, if my question sounds stupid, but... when i can't use run in a batch why there is run used in the startxdmcp.bat? It does the job as requested. But only with -nodecorations. Why can a window without border and titlebar can be used, but a normal window not? I don't want to compare to the old XFree86 (i'm glad about the new project) but once upon a time there where the same problem but was gone long ago. I didn't want to get into the details of what works and what doesn't work. You are right that it seems to work fine with -query, but it doesn't work with other options. I don't know what is going on, but I suspect we can probably fix it by modifying either run.exe or XWin.exe... but the other solution is to just use bash so we can do XWin instead of using start or run. Find whatever solution you need for the time being until it can be fixed properly. Harold -BEGIN PGP SIGNATURE- iD8DBQFAdem4zOHTWsKaqE0RAtEWAJ9SZPZg4ES90Bj/A/nemtWHmhZtUQCeND+G hjHezE9P/5je1My7JfyNNI0= =klTm -END PGP SIGNATURE-
Re: I miss files and openssl doesnt want to install
This is not related to Cygwin/X. As such, I have redirected futher discussion to the main Cygwin mailing list. Please consult http://cygwin.com/lists.html before posting again. Also, please consult http://cygwin.com/problems.html for the required way to submit a useful problem report. Finally, please search the mailing list archives before posting. Often, you question has already been asked and answered. Note: Using google as your search engine with a site:cygwin.com keyword will often produce better results than the search engine provided at cygwin.com. On Thu, 8 Apr 2004, Inqu wrote: Where can I find the rxvt-thingie? To answer question like this in general, please consult the package search facility available at http://cygwin.com/packages. I also suggest you read http://cygwin.com/faq/faq_toc.html#TOC13 and the following entry since it seems you did not understand what they have to say. Today I dloaded openssl 0.9.7d, located the compiler and perl from internet and installed it. The install went ok but the openssl doesnt work (or I cant find it). [snip] Is the ssl installed now or not and how can I find it? No, it is not. Again, consulting the package search facility mentioned above will solve your problem. I'm using mingw compiler, and winxp. If you're using the mingw compiler, then this question is off topic even for the main Cygwin list. Please consult mingw-users at lists.sourceforge.net. HTH -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444
.xinitrc ?
twm: another window manager is already running on screen 0? twm: unable to find any unmanaged screens If I use .xinitrc with exec twm, startx reports the above. The same using another window manager. It works fine if I add it to startxwin.sh. It used to work with XFree86. -- How to contact me - http://www.pervalidus.net/contact.html
X server with GLX acceleration
Hi, This works for me, glxgears results:- $ glxgears 3177 frames in 5.0 seconds = 635.400 FPS 3273 frames in 5.0 seconds = 654.600 FPS was: $ glxgears 520 frames in 5.0 seconds = 104.000 FPS 416 frames in 5.0 seconds = 83.200 FPS Pentium 800 with ATI Rage Pro (Windows XP) Nice work, thanks. Colin Harrison
X Server GLX Acceleration Results
Hi, GLX acceleration works fine for me. Tried on Matrox G550 and ATI Rage Pro on Windows XP. glxgears shows a massive speed-up (gears graphic doesn't show on ATI?). More testing underway. Thanks Colin Harrison
XWin initialization error
After installing the Cygwin/X and following the steps at the website http://x.cygwin.com/docs/ug/using.html, I am getting the following error message: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-1 Contact: [EMAIL PROTECTED] XWin was started with the following command line: X :0 -multiwindow -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winValidateArgs - Returning. 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 I have installed the whole Cygwin package, so there should not be anything missing. I also checked my fonts and they look like they are mounted correctly. What shall I do to start the XWin? Thanks in advance, Gokhan Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 6.7.0.0-1 Contact: [EMAIL PROTECTED] XWin was started with the following command line: X :0 -multiwindow -clipboard ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning OsVendorInit - Creating bogus screen 0 _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 winValidateArgs - Returning. 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
