RE: Still crash in xserv 4.3.0-42

RE: Still crash in xserv 4.3.0-42

[Harold L Hunt II]

Øyvind,

The problem you have found looks pretty generic, so it should be fixable.

I added two simple checks to winmultiwindowicons.c and check these into 
the CYGWIN branch on the xorg repository from freedesktop.org.  Please 
do a "cvs -z3 update" in hw/xwin, then run "cd 
build/std/programs/Xserver && make XWin.exe" and test the resulting 
executable.  If the crash still happens, then we will have to try again. 
  If the crash goes away, then check /tmp/XWin.log and send in the 
messages that mention winScaleXBitmapToWindows().

Harold

XWIN problem

[kelly quintero]

Hi everyone, I've been working with cygwin but i had
some trouble using the xwin option. There is an
specific laptop computer which doesn't want to connect
with XDMCP, i have tried in others and I know it
really works. When i use this command it shows an
error in Xwin.log. 

This is the command: 
xwin :0 -query sie 

This is the error: 
Fatal server error: XDMCP fatal error: Session failed
Session 129568516 failed for display 0.0.0.0:0: Cannot
open display 
winDeinitClipboard - Noting shutdown in progress
winDeinitMultiWindowWM - Noting shutdown in progress 

The laptop is a Dell computer with 512 RAM and
Processor of 1400 Mhz. It has an XSVGA screen. I think
it is a compurter problem but i really need how to
solve this error. I already have tried the startx
option and then using telnet to connect but it still
shows problems with the DISPLAY variable.... I
appreciate any help.....Thanks...


_________________________________________________________
Do You Yahoo!?
La mejor conexión a internet y 25MB extra a tu correo por $100 al mes. http://net.yahoo.com.mx

xwin problem

[Matthias Karl]

[-- Attachment #1: Type: text/plain, Size: 657 bytes --]

Hi,
I encountered a problem after making an update of cygwin with xwin.
The problem was not there before I made the update. I run setup.exe
today and accepted the new versions of xorg-x11. Afterwards the problem
with xwin appeared the first time.
Attached is the log-file which is generated in my tmp directory
after typing xwin on the cygwin command line.
Hope you can help me,

Matthias

-- 

Matthias Karl, PhD
Joint Research Centre, Institute for Environment and Sustainability
Climate Change Unit, TP280, I-21020 Ispra (Va), Italy.
Tel: (39)0332786761 (secr. -9958)  Fax: -6291
e-mail: matthias.karl@jrc.it
---
Climate Change Unit: http://ccu.jrc.it



[-- Attachment #2: XWin.log --]
[-- Type: text/plain, Size: 934 bytes --]

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.99.901-4

Contact: cygwin-xfree@cygwin.com

(WW) /tmp mounted int textmode
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
XWin was started with the following command line:

xwin 

(II) XF86Config is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
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"
(--) 3 mouse buttons found
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!

Fatal server error:
could not open default font 'fixed'
winDeinitMultiWindowWM - Noting shutdown in progress


[-- Attachment #3: Type: text/plain, Size: 223 bytes --]

--
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: xwin problem

[Andy Rushton]

bobby barcenas wrote:
> hello,
> I have been using cygwin and the x server very well for a couple of
> years now, thank you, but recently I tried to update some of my files
> because i was unable to run and opengl dependent file on xwin.  so i
> looked online and ran setup.exe and installed the appropate files.
> however, when that setup was compete i could no longer run xwin.
> whenever i type startx into cygwin, i get an error message because it
> cant find a font in a directory that does not exist on my computer:
> /usr/x11r6/lib/x11/fonts/Cid
Actually the log shows:
-------------
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing 
from list!

Fatal server error:
could not open default font 'fixed'
-------------

The first bit about dah/dit/dah/CID is just a warning. The other message 
is the error.

This issue has just been resolved in the thread "Problem with starting X 
server".

-- 
Andy Rushton, Southampton, UK

Fortune and love befriend the bold.
		-- Ovid


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

xwin problem

[bobby barcenas]

[-- Attachment #1: Type: text/plain, Size: 686 bytes --]

hello,
I have been using cygwin and the x server very well for a couple of
years now, thank you, but recently I tried to update some of my files
because i was unable to run and opengl dependent file on xwin.  so i
looked online and ran setup.exe and installed the appropate files.
however, when that setup was compete i could no longer run xwin.
whenever i type startx into cygwin, i get an error message because it
cant find a font in a directory that does not exist on my computer:
/usr/x11r6/lib/x11/fonts/Cid

I then tried to reinstall my entire cygwin and it still doesnt work.
could you help me out?
i have included the tmp log file.
thanks
-- 
bbarcenas@gmail.com
Bobby Barcenas

[-- Attachment #2: XWin.log --]
[-- Type: application/octet-stream, Size: 1406 bytes --]

(WW) /tmp mounted int textmode
_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: 1280 height: 854 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
winInitMultiWindowWM - Calling pthread_mutex_lock ()
winMultiWindowXMsgProc - Hello
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!

Fatal server error:
could not open default font 'fixed'
winDeinitMultiWindowWM - Noting shutdown in progress

[-- Attachment #3: Type: text/plain, Size: 223 bytes --]

--
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: XWIN problem

[Harold L Hunt II]

Kelly,

The problem with address 0.0.0.0 is known and there is a fix; however, 
no one implemented it until now because they (no one here) were too busy 
discussing the proper way to implement the fix.  Well, I just went and 
did and and blocked the address 0.0.0.0 from being sent to the remote 
machine (which it then tries to connect back to.  The reason that 
0.0.0.0 shows up in the list of addresses for your laptop is that 
Windows returns 0.0.0.0 for any interface that is unconfigured.  A lot 
of laptops have a wireless card now; if that wireless card doesn't have 
an address (or the wireless does but the wired does not) then you have a 
50-50 chance of 0.0.0.0 being sent as the first address in the list. 
XDM servers are dumb, so they try to connect only to the first address 
in the list, then they give up if that address fails (not much point in 
sending a list then, eh?).

I will be posting an updated version of the XFree86-xserv package later 
tonight after I can verify that this fixes the problem without 
introducing any obvious problems.

Harold