(:

2005-05-18 Thread antiblast
(:

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

Contact: cygwin-xfree@cygwin.com

XWin was started with the following command line:

X :0 -multiwindow -clipboard

ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1280 h 1024
winInitializeDefaultScreens - Returning
(WW) /tmp mounted int textmode
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
winCheckDisplayNumber - Cygwin/X is already running on display 0

Fatal server error:
InitOutput - Duplicate invocation on display number: 0.  Exiting.



Problem with -multiwindow and -clipboard when using -nolisten tcp

2005-05-18 Thread Brian Willis
I'm trying to turn off the tcp port for Cygwin/X.  I would like to just 
close it down on the outside interface and still have it listen on the 
loopback device.  I have not been able to find a way to do that.  The 
closest thing I could find is to turn off tcp all together.  This does 
work.  I'm able to bring up xterms and the whole deal.  I get odd 
behavior after that.  The xterm allows me to copy and paste within the 
window, but it doesn't copy to the Microsoft Windows clipboard.   The x 
button on the upper right corner of the xterm also does not work.  You 
can only open one xterm or other type of xforwarding because multiwindow 
hasn't loaded.  Is there a setting to tell multiwindow and clipboard 
where the display is?  I can see them trying to access the loopback. 
Here is output from my xwin.log:

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.2.0-2
Contact: cygwin-xfree@cygwin.com
XWin was started with the following command line:
XWin :0 -multiwindow -nolisten tcp -silent-dup-error
ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1024 h 768
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: 1024 height: 768 depth: 32
winInitVisualsShadowGDI - Masks 00ff ff00 00ff 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: 0409 (0409)
(--) 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!
winInitMultiWindowWM - pthread_mutex_lock () returned.
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.
winMultiWindowXMsgProc - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - pthread_mutex_unlock () returned.
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - Could not open display, try: 1, sleeping: 5
winMultiWindowXMsgProc - Could not open display, try: 1, sleeping: 5
winProcEstablishConnection - Hello
winProcEstablishConnection - Clipboard is not enabled, returning.
winInitMultiWindowWM - Could not open display, try: 2, sleeping: 5
winMultiWindowXMsgProc - Could not open display, try: 2, sleeping: 5
(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/
winAllocateFBShadowGDI - Creating DIB with width: 1024 height: 768 depth: 32
winInitVisualsShadowGDI - Masks 00ff ff00 00ff 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 ()
MIT-SHM extension disabled due to lack of kernel support
winMultiWindowXMsgProc - Hello
winMultiWindowXMsgProc - Calling pthread_mutex_lock ()
winMultiWindowXMsgProc - Could not open display, try: 3, sleeping: 5
winMultiWindowXMsgProc - Could not open display, try: 4, sleeping: 5
XFree86-Bigfont extension local-client optimization disabled due to 
lack of shared memory support in the kernel
(--) Setting autorepeat to delay=500, rate=31
winInitMultiWindowWM - Could not open display, try: 3, sleeping: 5
winInitMultiWindowWM - Could not open display, try: 3, s(--) 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!
winInitMultiWindowWM - pthread_mutex_lock () returned.
winMultiWindowXMsgProc - pthread_mutex_lock () returned.
winMultiWindowXMsgProc - pthread_mutex_unlock () returned.

Re: Problem with -multiwindow and -clipboard when using -nolisten tcp

2005-05-18 Thread Alexander Gottwald
On Wed, 18 May 2005, Brian Willis wrote:

 I'm trying to turn off the tcp port for Cygwin/X.  I would like to just 
 close it down on the outside interface and still have it listen on the 
 loopback device.  I have not been able to find a way to do that.  The 
 closest thing I could find is to turn off tcp all together.  This does 
 work.  I'm able to bring up xterms and the whole deal.  I get odd 
 behavior after that.  The xterm allows me to copy and paste within the 
 window, but it doesn't copy to the Microsoft Windows clipboard.   The x 
 button on the upper right corner of the xterm also does not work.  You 
 can only open one xterm or other type of xforwarding because multiwindow 
 hasn't loaded.  Is there a setting to tell multiwindow and clipboard 
 where the display is?  I can see them trying to access the loopback. 
 Here is output from my xwin.log:
 
 Welcome to the XWin X Server
 Vendor: The Cygwin/X Project
 Release: 6.8.2.0-2
 
 Contact: cygwin-xfree@cygwin.com
 
 XWin was started with the following command line:
 
 XWin :0 -multiwindow -nolisten tcp -silent-dup-error
 
 winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
 winInitMultiWindowWM - Could not open display, try: 1, sleeping: 5
 
 I can see the clipboard and multiwin try and use the loopback and fail. 
   Is there something I'm missing?  Can I use loopback without the 
 outside interface listening?

Multiwindow and clipboard require enabled tcp transport. But you can create
patches which force the threads to use :0.0 instead of 127.0.0.1:0.0 if 
the tcp transport is switched off.

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723


Re: Problem with -multiwindow and -clipboard when using -nolisten tcp

2005-05-18 Thread Brian Willis
Alexander Gottwald wrote:
On Wed, 18 May 2005, Brian Willis wrote:

I'm trying to turn off the tcp port for Cygwin/X.  I would like to just 
close it down on the outside interface and still have it listen on the 
loopback device.  I have not been able to find a way to do that.  The 
closest thing I could find is to turn off tcp all together.  This does 
work.  I'm able to bring up xterms and the whole deal.  I get odd 
behavior after that.  The xterm allows me to copy and paste within the 
window, but it doesn't copy to the Microsoft Windows clipboard.   The x 
button on the upper right corner of the xterm also does not work.  You 
can only open one xterm or other type of xforwarding because multiwindow 
hasn't loaded.  Is there a setting to tell multiwindow and clipboard 
where the display is?  I can see them trying to access the loopback. 
Here is output from my xwin.log:

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 6.8.2.0-2
Contact: cygwin-xfree@cygwin.com
XWin was started with the following command line:
XWin :0 -multiwindow -nolisten tcp -silent-dup-error
winInitMultiWindowWM - DISPLAY=127.0.0.1:0.0
winInitMultiWindowWM - Could not open display, try: 1, sleeping: 5
I can see the clipboard and multiwin try and use the loopback and fail. 
 Is there something I'm missing?  Can I use loopback without the 
outside interface listening?

Multiwindow and clipboard require enabled tcp transport. But you can create
patches which force the threads to use :0.0 instead of 127.0.0.1:0.0 if 
the tcp transport is switched off.

bye
ago
Is there any way to make the X server listen on loopback but not on the 
outside interface?  The firewall software does all interfaces, not just 
the outside.
begin:vcard
fn:Brian Willis
n:Willis;Brian
email;internet:[EMAIL PROTECTED]
title:System Admin
tel;work:301-713-1669x155
version:2.1
end:vcard



Re: Problem with -multiwindow and -clipboard when using -nolisten tcp

2005-05-18 Thread Brian Willis
Corinna Vinschen wrote:
On May 18 10:35, Brian Willis wrote:
Is there any way to make the X server listen on loopback but not on the 
outside interface?  The firewall software does all interfaces, not just 
the outside.

That would be a surprise.  Are you using the XP SP2 firewall by any
chance?  It allows to customize trusted networks in it's GUI.
Corinna
We do use XP SP2, but it doesn't work well with our VPN client, so we 
use one from Computer Associates.  Unfortunatly I don't get much say in 
what we run on the desktops, just the servers.
begin:vcard
fn:Brian Willis
n:Willis;Brian
email;internet:[EMAIL PROTECTED]
title:System Admin
tel;work:301-713-1669x155
version:2.1
end:vcard



Re: AW: Getting multiple lines Xlib: unexpected async reply (sequence 0xAdress)! when runnning startx

2005-05-18 Thread Alexander Gottwald
On Wed, 18 May 2005, Vincenzo Daniele wrote:

 I can´t find fvwm.
 Funny effect with twm:
 
 The grey xwin window appears as I am running startx with  in the 
 background,
 but nothing goes on.

twm does not display anything special unless you have windows on the screen.

 In the bash following info was written after this exit:
 
 $ Xlib: sequence lost (0x1  0x71) in reply type 0x0!
 X connection to :0.0 broken (explicit kill or server shutdown).
 winDeinitMultiWindowWM - Noting shutdown in progress

I think it's xinit which has the problems.

How does this work
$ XWin :0 
$ sleep 5s
$ twm 

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723


mouse wheel not working with xterm

2005-05-18 Thread jose isaias cabrera
Greetings!
I am running cygwin with xwindows (XWin) and none of the xterm history is 
accessible through the mouse wheel.  I have a IBM R50 laptop, which has a 
touch wheel on the right side of the touch-mouse.  The touch mouse works 
perfectly, but the touch wheel does not.  I have another laptop (compaq) 
with similar touch mouse/wheel options that is working ok.  Yes, the mouse 
work perfectly on the MS Windows XP base.

Any ideas?
thanks,
josé 



Re: mouse wheel not working with xterm

2005-05-18 Thread Alexander Gottwald
On Wed, 18 May 2005, jose isaias cabrera wrote:

 
 Greetings!
 
 I am running cygwin with xwindows (XWin) and none of the xterm history is 
 accessible through the mouse wheel.  I have a IBM R50 laptop, which has a 
 touch wheel on the right side of the touch-mouse.  The touch mouse works 
 perfectly, but the touch wheel does not.  I have another laptop (compaq) 
 with similar touch mouse/wheel options that is working ok.  Yes, the mouse 
 work perfectly on the MS Windows XP base.

What does xev report when you scroll? Some mouse driver do strange stuff with
the button and don't report it as normal scroll messages.

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723


Re: mouse wheel not working with xterm

2005-05-18 Thread jose isaias cabrera
Ago,
first of all, thank you for all your help.  You are always willing to help. 
Thanks.
What does xev report when you scroll?
Well, it does not acknowledge the scroll.  Here is an excerpt of the run:
MotionNotify event, serial 25, synthetic NO, window 0xa1,
   root 0x3a, subw 0x0, time 12741160, (92,1), root:(591,45),
   state 0x0, is_hint 0, same_screen YES
MotionNotify event, serial 25, synthetic NO, window 0xa1,
   root 0x3a, subw 0x0, time 12741180, (91,2), root:(590,46),
   state 0x0, is_hint 0, same_screen YES
MotionNotify event, serial 25, synthetic NO, window 0xa1,
   root 0x3a, subw 0x0, time 12741190, (91,3), root:(590,47),
   state 0x0, is_hint 0, same_screen YES
MotionNotify event, serial 25, synthetic NO, window 0xa1,
   root 0x3a, subw 0x0, time 12741210, (90,5), root:(589,49),
   state 0x0, is_hint 0, same_screen YES
MotionNotify event, serial 25, synthetic NO, window 0xa1,
   root 0x3a, subw 0x0, time 12741240, (90,6), root:(589,50),
   state 0x0, is_hint 0, same_screen YES
ButtonPress event, serial 25, synthetic NO, window 0xa1,
   root 0x3a, subw 0x0, time 12742062, (90,6), root:(589,50),
   state 0x0, button 1, same_screen YES
ButtonRelease event, serial 25, synthetic NO, window 0xa1,
   root 0x3a, subw 0x0, time 12742442, (90,6), root:(589,50),
   state 0x100, button 1, same_screen YES
ButtonPress event, serial 25, synthetic NO, window 0xa1,
   root 0x3a, subw 0x0, time 12743123, (90,6), root:(589,50),
   state 0x0, button 3, same_screen YES
ButtonRelease event, serial 25, synthetic NO, window 0xa1,
   root 0x3a, subw 0x0, time 12743744, (90,6), root:(589,50),
   state 0x400, button 3, same_screen YES
ButtonPress event, serial 25, synthetic NO, window 0xa1,
   root 0x3a, subw 0x0, time 12745937, (90,6), root:(589,50),
   state 0x0, button 2, same_screen YES
ButtonRelease event, serial 25, synthetic NO, window 0xa1,
   root 0x3a, subw 0x0, time 12746558, (90,6), root:(589,50),
   state 0x200, button 2, same_screen YES
MotionNotify event, serial 25, synthetic NO, window 0xa1,
   root 0x3a, subw 0x0, time 12757013, (88,4), root:(587,48),
   state 0x0, is_hint 0, same_screen YES
LeaveNotify event, serial 25, synthetic NO, window 0xa1,
   root 0x3a, subw 0x0, time 12757033, (82,-3), root:(581,41),
   mode NotifyNormal, detail NotifyNonlinear, same_screen YES,
   focus YES, state 0
FocusOut event, serial 25, synthetic NO, window 0xa1,
   mode NotifyNormal, detail NotifyNonlinear
...
Some mouse driver do strange stuff with
the button and don't report it as normal scroll messages.
This is probably the case here.  Any ideas on how to make it acknowledge the 
scroll?

thanks.
josé 



Re: mouse wheel not working with xterm

2005-05-18 Thread Alexander Gottwald
On Wed, 18 May 2005, jose isaias cabrera wrote:

 Well, it does not acknowledge the scroll.  Here is an excerpt of the run:

What I see is: 

 ButtonPress event, serial 25, synthetic NO, window 0xa1,
 root 0x3a, subw 0x0, time 12742062, (90,6), root:(589,50),
 state 0x0, button 1, same_screen YES
 
 ButtonRelease event, serial 25, synthetic NO, window 0xa1,
 root 0x3a, subw 0x0, time 12742442, (90,6), root:(589,50),
 state 0x100, button 1, same_screen YES

Left mouse button
 
 ButtonPress event, serial 25, synthetic NO, window 0xa1,
 root 0x3a, subw 0x0, time 12743123, (90,6), root:(589,50),
 state 0x0, button 3, same_screen YES
 
 ButtonRelease event, serial 25, synthetic NO, window 0xa1,
 root 0x3a, subw 0x0, time 12743744, (90,6), root:(589,50),
 state 0x400, button 3, same_screen YES

Right Mouse button

 
 ButtonPress event, serial 25, synthetic NO, window 0xa1,
 root 0x3a, subw 0x0, time 12745937, (90,6), root:(589,50),
 state 0x0, button 2, same_screen YES
 
 ButtonRelease event, serial 25, synthetic NO, window 0xa1,
 root 0x3a, subw 0x0, time 12746558, (90,6), root:(589,50),
 state 0x200, button 2, same_screen YES

Middle Button.

  Some mouse driver do strange stuff with
  the button and don't report it as normal scroll messages.
 
 This is probably the case here.  Any ideas on how to make it acknowledge the 
 scroll?

The mouse driver configuration should provide a choice for this. I don't
know the driver for this kind so you're quite on your own there.

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723


RE(Re): Base-files 3.4-1: Problems for users with Non-Admin. priv

2005-05-18 Thread Angelo Graziosi

John,
you mailed to Igor that there will be a new release of base-files.


Will it fix also /etc/profile?   
==

As I wrote:

http://cygwin.com/ml/cygwin-xfree/2005-05/msg00140.html

the problem of

   chmod 1777 /tmp

is present also for the user (NOT-ADMIN.) that uses only the standard bash
shell, i.e. the user that does not use X (XWin etc.).

Thank you

angelo.



base-files 3.4-2: Permission denied!

2005-05-18 Thread Angelo Graziosi

With this new release there is a 

   Permission denied

when a NOT-ADMIN user starts the X system (startxwin.bat)
  

He has not access to remove .X11-unix (see startxwin.bat) when /tmp has
the t permission.

Every user (or only Administrator?) should remove manually .X11-unix
before the disconnetion from the machine.

In this case there is not permission denied for the simple user.

angelo.



question

2005-05-18 Thread Andrei Faraon
Hello,

I installed X-cygwin (the xorg-x11-base package) and I run it with the
comand startx and it enters a single-window mode. My intention is to
run it in multi-window mode and I know that the command startx should
launch the multi-window mode. Can you please give me some help with
respect to this problem?

Regards,
-- 
Andrei Faraon

Stanford University, Applied Physics
316 Via Pueblo Mall
Stanford, CA, 94305
Home: 650 495 3857
Office: 650 723 2279


Re: using xfree86 4.4.0 from remote host

2005-05-18 Thread nirus
 I am currently trying to use XFree86/cygwin 4.4.0. Maybe I would have 
 been more successful with cygwin stuff?
 The problem is that I can't use the X server from the remote host. I 
 have tried xhost +remoteIP and xhost + on the windows machine 
 running xfree86. Both succeeded, but the remote says the same thing as 
 before -
 Xlib: connection to 10.0.5.1:0.0 refused by server
 Xlib: No protocol specified

This has to do with your SSH client supporting X11 Forwarding. The companies
that I do work for quite often use a program called 'Erics Telnet' which works
just fine until you try and use it with Cygwin/X then it returns the error
displayed above.

However as soon as I use Putty...with X11 forwarding set correctly...it works
like a gem