[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[suse-security] OT: X Server with cygwin. Was Re:[suse-security] safety with scp



Hi


> Nevertheless gives a nice X-Server.
> ;-)

Oh, yes, i forgot it. Problem is... i am unable to use it. The first
time i used cygwin i did it with administrator w2k user. From then on,
i use a regular user, but with administration rights, though (company
policy). Administrator user can launch X server, but not any other
user (at this point, i really miss the su - linux capability).

When i launch the startx command, this is what i get (in a popup window):

A fatal error has occurred and Cygwin/X will now exit.
Please open /tmp/XWin.log for more information.

Vendor: The cygwin X Project
Release: 6.8.2.0-2
Contact: blah blah
XWin was started with the following command-line:

X :0 -multiwindow -clipboard


The main cygwin windows shows:

Mcalerom@MCALEROMAC2K ~
$ startx

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.2.0-2

Contact: cygwin-xfree@xxxxxxxxxx

XWin was started with the following command line:

X :0 -multiwindow -clipboard


Fatal server error:
Cannot open log file "/tmp/XWin.log"


waiting for X server to begin accepting connection
..
..
..
..
..
..
..
..
..
..
winDeinitMultiWindowWM - Noting shutdown in progre
giving up.
xinit:  Connection refused (errno 111):  unable to
xinit:  No such process (errno 3):  Server error.

The closest thing i could find to the log file mentioned above was
c:\cygwin\tmp\XWin.log, but the last time this file was updated was by
mid september :-?

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.2.0-2

Contact: cygwin-xfree@xxxxxxxxxx

XWin was started with the following command line:

X :0 -multiwindow -clipboard

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1400 h 1050
winInitializeDefaultScreens - Returning
_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
(==) FontPath set to
"/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/TTF/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/"
winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel
winAllocateFBShadowGDI - Creating DIB with width: 1400 height: 1050 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: "0000040a" (0000040a)
(--) Using preset keyboard for "Spanish (Spain, Traditional Sort)"
(40a), type "4"
(--) 3 mouse buttons found
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/,
removing from list!
winInitMultiWindowWM - pthread_mutex_lock () returned.
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
winProcEstablishConnection - Hello
winInitClipboard ()
winProcEstablishConnection - winInitClipboard returned.
winClipboardProc - Hello
DetectUnicodeSupport - Windows NT/2000/XP
winClipboardProc - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - XOpenDisplay () returned and successfully
opened the display.
winClipboardProc - XOpenDisplay () returned and successfully opened the display.
winMultiWindowXMsgProc - XOpenDisplay () returned and successfully
opened the display.
winMultiWindowXMsgProcErrorHandler - ERROR: BadWindow (invalid Window parameter)


I know it is very OT, but i thought it was worthy to give it a try...


--
Saludos,
miguel

--
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@xxxxxxxx
Security-related bug reports go to security@xxxxxxx, not here