X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Robert Neville Subject: Problems with X, fonts, and clipboard module Date: Tue, 08 May 2007 18:14:10 -0700 Lines: 79 Message-ID: <6a72435r4rqjcmgdu9ejkth7ag0mk778l9@4ax.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com I am not sure if this is the appropriate group, yet it has been the main resource for cygwin. In addition, searching through these gmane newsgroups is not straightforward since Google groups do not return them. Startx failed to initialize when it had been working in the past. I ran setup and the process may have not completed (it was late). After running setup.exe again, I navigated to the System category and reinstalled rebase. Then I reviewed the README file; kill all processes associated with cygwin; ran ash; and typed /bin/rebaseall -v; the utility performed some actions and returned without errors. I fired up a cygwin console and startx would still not initialize. The console gave me the following font error. sageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. FreeFontPath: FPE "/usr/X11R6/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing. I have also removed the -clipboard and multiplewindows arguments from the startx script; it did not help. The clipboard module is the main advantage of running X for me. Startxwin.bat and starxwin.sh do not launch Xwin either. Xwin should not conflicting with my firewall; since this system does not have software firewall. After reinstalling X and all fonts, I mounted the font path and still receive this error. Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from li st! The cygwin console appears fully functional. Please give me whatever insight you may have on these scenarios. I have already spent two weeks troubleshooting these issues and need better guidance. I can read the logs, but I am not familiar with the action necessary. _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: 2048 height: 768 depth: 32 winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff 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: "00000409" (00000409) (--) 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! winInitMultiWindowWM - pthread_mutex_lock () returned. winProcEstablishConnection - Hello winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0 winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0 winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winClipboardProc - DISPLAY=127.0.0.1:0.0 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! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/