X server version 6.8.99.901
I've updated the X software to 6.8.99.901 and noticed two problems with the new X server: 1. CNTL-ALT-BKSP doesn't terminate the server cleanly. There's no confirmation dialogue and /tmp/.X11-unix/X0 is not deleted. However, the new server does terminate properly if I right-click the X icon in the taskbar and select exit. 2. It is not possible to start the X server if another user created the /tmp/.X11-unix file but failed to delete it. To reproduce the bug: Log into a user in the Administrators group, start the X server, then log out. The /tmp/.X11-unix/X0 socket will be left in place. Log into a non-Administrator user and attempt to start the X server using startxwin.bat. The startxwin session will report that /tmp/.X11-unix/X0 could not be deleted (because /tmp/.X11-unix is a 'sticky' directory). The X server will not start and its log file will show that it thought that another server was running. The previous X server was quite happy to re-use an X0 socket created by another user. I worked round the problem by hacking startxwin.bat to do the following after the X server had been started: %CYGWIN_ROOT%\bin\sleep 5 %CYGWIN_ROOT%\bin\chmod -t /tmp/.X11-unix This ensures that /tmp/.X11-unix will be non-sticky, so any user will be able to clean up the X0 socket. -- 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/
ImageMagick 6.0.4 no longer executes with package xorg-x11-bin-dlls 6.8.99.901-1
Hi all, I have found a problem with ImageMagick 6.0.4 running with xorg-x11-bin-dlls 6.8.99.901-1 - and I've found a temporary fix. Problem: After a recent update to my Cygwin installation, which updated the X11 packages amongst many other things, the 'convert' program stopped working. It simply exited silently with an error status. I discovered with gdb that it was failing with an unknown exception but I could find no more information. It turned out, thanks to running 'cygcheck convert', that this was because of a missing DLL, specifically /usr/X11R6/bin/cygdpstk-1.dll. A bit more digging and I found that this DLL used to be part of package xorg-x11-bin-dlls but has been removed with the latest release - 6.8.99.901-1. It existed in all versions (as far as I have been able to find out) up to this one. I also discovered that this DLL itself relies on another missing DLL: /usr/X11R6/bin/cygdps-1.dll which I found in the same package. Work-around: I've fixed the problem for myself by grabbing these DLLs from the previous version of this package (xorg-x11-bin-dlls-6.8.2.0) and hand-installing them by copying them into the relevant directory. Fortunately they are still compatible with the other DLLs they depend on. Andy -- 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: Problem with starting X server
Jim, It this is the root of your problem: Fatal server error: could not open default font 'fixed' winDeinitMultiWindowWM - Noting shutdown in progress This is what finally worked for me. Start cygwin and do a df, if this show the mount points, /usr, /usr/bin/, and /usr/lib. Then umount /usr and close the cygwin window. Now do the reinstall of the fonts as documented in the FAQ. The mount point mentioned in the FAQ doesn't exist, so this took care of my problem. I wished they where a little clearer in what has the wrong infomation that unumounting and reinstalling resolves. Hopes this helps. Steve Craig Smith wrote: I am getting the following text in XWin.log: (WW) /tmp mounted int textmode _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root (II) XF86Config is not supported (II) See 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: 1680 height: 1050 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 shar ed 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/CID/, removing from li st! Fatal server error: could not open default font 'fixed' winDeinitMultiWindowWM - Noting shutdown in progress I have tried the remedy noted at x.cygwin.com/docs/faq/cygwin-x-faq.html#q-error-font-eof to no avail. In fact the umount command noted returns no mount found. I have tried reinstalling X, completely uninstalling cygwin and reinstalling it, to no avail. Googling the problem only points me to the FAQ over and over again. Any ideas on some other things I could try? Thanks, Craig Smith -- 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: Problem with starting X server
Stephen A.Goulet wrote: This is what finally worked for me. Start cygwin and do a df, if this show the mount points, /usr, /usr/bin/, and /usr/lib. Then umount /usr and close the cygwin window. Now do the reinstall of the fonts as documented in the FAQ. I agree, but wanted to add to this feedback. I have found that you need to mount the fonts in binary mode. You see, I go against the recommended practice and install Cygwin in Text mode - i.e. text files have DOS line-endings. I find that this allows better inter-operation between Cygwin apps and Windows apps. However, this seems to break X11's fonts (I *suspect* that somewhere in X the fonts are being opened in text mode when they are binary files but I haven't been able to confirm this). If this is your problem, the solution is to separately mount the font directory in binary mode - for example, my mount table contains the following: e:\cygwin\usr\X11R6\lib\X11\fonts on /usr/X11R6/lib/X11/fonts type system (binmode) E:\cygwin\bin on /usr/bin type system (textmode) E:\cygwin\lib on /usr/lib type system (textmode) E:\cygwin on / type system (textmode) c: on /cygdrive/c type system (textmode,noumount) d: on /cygdrive/d type system (textmode,noumount) e: on /cygdrive/e type system (textmode,noumount) Note the first entry. Once I have this extra mount point for the X11 fonts, I reinstalled all the fonts using the Cygwin installer - which has a 'reinstall' option for each package. The reinstall means that the font indexes get regenerated. FYI the command for generating extra mount points is called 'mount'. -- 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/
