public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: xwin on cygwin - cannot connect
Date: Sun, 30 Nov 2003 06:26:00 -0000 [thread overview]
Message-ID: <3FC98D9D.1010704@msu.edu> (raw)
In-Reply-To: <071B78D196015846A511D2EA6540766D0209E4@commandcenter.dijitalconceptions.com>
Andrew,
Hmm... the log file looks okay, you did try a failed connection, then
send in that XWin.log, right?
I'm going to bed. Maybe someone else can help.
Harold
Andrew Leung wrote:
> Thanks for the reply, here it is, This was my latest attempt, but now
> it seems the checkered screen stays.. but with no change. It does not
> disappear on me at this point.
>
> ddxProcessArgument - Initializing default screens
> winInitializeDefaultScreens - w 1024 h 768
> winInitializeDefaultScreens - Returning
> OsVendorInit - Creating bogus screen 0
> _XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
> (EE) Unable to locate/open config file
> InitOutput - Error reading config file
> winDetectSupportedEngines - Windows NT/2000/XP
> winDetectSupportedEngines - DirectDraw installed
> winDetectSupportedEngines - Allowing PrimaryDD
> winDetectSupportedEngines - DirectDraw4 installed
> winDetectSupportedEngines - Returning, supported engines 0000001f
> InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
> winSetEngine - Using Shadow DirectDraw NonLocking
> winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits
> per pixel
> winCreateBoundingWindowWindowed - User w: 1024 h: 768
> winCreateBoundingWindowWindowed - Current w: 1024 h: 768
> winAdjustForAutoHide - Original WorkArea: 0 100 718 1024
> winAdjustForAutoHide - Adjusted WorkArea: 0 100 718 1024
> winCreateBoundingWindowWindowed - WindowClient w 918 h 693 r 918 l 0 b
> 693 t 0
> winCreateBoundingWindowWindowed - Returning
> winCreatePrimarySurfaceShadowDDNL - Creating primary surface
> winCreatePrimarySurfaceShadowDDNL - Created primary surface
> winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface
> winAllocateFBShadowDDNL - lPitch: 3672
> winAllocateFBShadowDDNL - Created shadow pitch: 3672
> winAllocateFBShadowDDNL - Created shadow stride: 918
> winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
> winInitVisualsShadowDDNL - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24
> bpp 32
> 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
> (==) winConfigKeyboard - Layout: "00000409" (00000409)
> (EE) No primary keyboard configured
> (==) Using compiletime defaults for keyboard
> Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)"
> Options = "(null)"
> winPointerWarpCursor - Discarding first warp: 459 346
> winBlockHandler - Releasing pmServerStarted
> winBlockHandler - pthread_mutex_unlock () returned
>
>
> -----Original Message-----
> From: cygwin-xfree-owner@cygwin.com
> [mailto:cygwin-xfree-owner@cygwin.com] On Behalf Of Harold L Hunt II
> Sent: Sunday, November 30, 2003 1:09 AM
> To: cygwin-xfree@cygwin.com
> Subject: Re: xwin on cygwin - cannot connect
>
> Andrew,
>
> Andrew Leung wrote:
>
>>I've got cygwin on winxp machine - can't connect to the X server.
>
> When
>
>>using xwin.exe :0 -query <host> the checkered screen quickly comes up
>>and then disappears.. Anyone know whats happening? Also I remember
>>someone mentioning that X shouldn't be running on the linux box when
>>trying to connect. How do I stop this as the login screen loads up
>>everytime I boot up? The machine is running slackware. I'm pretty
>
> sure
>
>>there's communication since tcpdumps show some responsive port 117
>>traffic.. Any help is appreciated, I'm new to linux so I'm not sure
>>what to look for.. Thanks in advance.
>
>
> Sounds like you have a font problem on your Windows machine. Please
> send in the contents of /tmp/XWin.log after a failed attempt to connect.
>
> Harold
>
>
>
>
>
next prev parent reply other threads:[~2003-11-30 6:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 6:14 Andrew Leung
2003-11-30 6:26 ` Harold L Hunt II [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-02 3:36 Andrew Leung
2003-12-02 3:55 ` Harold L Hunt II
2003-12-01 2:01 Andrew Leung
2003-12-01 1:56 Andrew Leung
2003-12-01 11:06 ` Rasjid Wilcox
2003-12-01 1:04 Andrew Leung
2003-12-01 1:08 ` Harold L Hunt II
2003-11-30 23:53 Andrew Leung
2003-12-01 0:05 ` Harold L Hunt II
2003-11-30 4:13 Andrew Leung
2003-11-30 6:08 ` Harold L Hunt II
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=3FC98D9D.1010704@msu.edu \
--to=huntharo@msu.edu \
--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).