public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Frederick Hansen <polfam19@msn.com>
To: <cygwin-xfree@cygwin.com>
Subject: xorg-server-1.9.2-1 Fullscreen Issue
Date: Thu, 18 Nov 2010 12:33:00 -0000	[thread overview]
Message-ID: <SNT129-W66B341EE2B58251E6DD4DD4390@phx.gbl> (raw)


Greetings,

Just FYI, after upgrading to xorg-server 1.9.2, any attempt to run in fullscreen results in an error.  Downgrading to version 1.8.2 seems to correct the issue.  Running either version in multiwindow also works.

The contents of Xwin.log are shown below:


Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.9.2.0 (10902000)
Build Date: 2010-11-03

XWin was started with the following command line:

/usr/bin/XWin -fullscreen -depth 8 -clipboard -silent-dup-error 

ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 1920 h 1080
winInitializeDefaultScreens - native DPI x 96 y 96
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/HCU-47R4ZN1:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
[ 30090.218] winInitializeScreens - 1
[ 30090.218] winInitializeScreen - 0
[ 30090.234] (II) xorg.conf is not supported
[ 30090.234] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
[ 30090.265] LoadPreferences: /home/200007557/.XWinrc not found
[ 30090.265] LoadPreferences: Loading /etc/X11/system.XWinrc
[ 30090.265] LoadPreferences: Done parsing the configuration file...
[ 30090.265] winGetDisplay: DISPLAY=:0.0
[ 30090.265] winDetectSupportedEngines - Windows NT/2000/XP
[ 30090.265] winDetectSupportedEngines - DirectDraw installed
[ 30090.265] winDetectSupportedEngines - Allowing PrimaryDD
[ 30090.265] winDetectSupportedEngines - DirectDraw4 installed
[ 30090.265] winDetectSupportedEngines - Returning, supported engines 0000001f
[ 30090.265] winSetEngine - Using Shadow DirectDraw NonLocking
[ 30090.265] winScreenInit - Using command line depth of 8 bpp
[ 30090.734] winFinishScreenInitFB - Masks: 00000000 00000000 00000000
[ 30090.781] Screen 0 added at virtual desktop coordinate (0,0).
[ 30090.781] MIT-SHM extension disabled due to lack of kernel support
[ 30090.796] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel
[ 30091.140] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
[ 30091.140] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 30091.171] [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list!
[ 30091.171] [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list!
[ 30091.171] [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list!
[ 30091.406] (EE) XKB: Could not invoke xkbcomp
[ 30091.406] (EE) XKB: Couldn't compile keymap
[ 30091.406] XKB: Failed to compile keymap
[ 30091.406] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config.
[ 30091.406] 
Fatal server error:
[ 30091.406] Failed to activate core devices.


Thanks for your time,
Fred
 		 	   		  

--
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/


             reply	other threads:[~2010-11-18 12:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 12:33 Frederick Hansen [this message]
2010-11-19 13:37 ` Jon TURNEY
2011-01-21  4:38   ` Frederick D. Hansen
2011-01-24 17:48     ` Jon TURNEY
2011-01-26 13:24       ` Reinier Post

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SNT129-W66B341EE2B58251E6DD4DD4390@phx.gbl \
    --to=polfam19@msn.com \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).