Re: XWin listens on too many TCP ports and killing existing connections.

2004-05-07 Thread Alexander Gottwald
On Thu, 6 May 2004, Caphe Noir wrote:

 I've been having problems with my current listening
 TCP connections in port range 3000-5000 (not exact)
 seems are getting disconnected because XWin spawns a
 new listening connection every second in this port
 range.  
 
 The listening ports by XWin seems to increment by 4
 every time, cycles up to 5000 then wrap back to 3000. 
 If the listening port by XWin happens to be a port
 that already have a listening server, then that
 listening server is removed.
 
 For example, if I currently have an SSH connection
 that listens on port 3008.  Then XWin starts a listen
 on port 3000; at the next second, it listen on 3004;
 and at the next second, it listens on port 3008,
 causing a conflict and my SSH connection disappear.
 
 Any body have any idea how to fix this?

Please send the /tmp/XWin.log logfile.

Do you have any kind of firewall or vpn software installed
on your computer?

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


Re: Silent exit after double-clicking on text in xterm

2004-05-07 Thread Colin Harrison
Hi,

This was also happening to me on XP, randomly, on closing any old windows
(fonts in the Control Panel was my test case!).
I've been chasing this one, on and off, for a few days with no luck!.
Fixed, I think, with the latest snapshot cygwin1.dll (6th May).
I'll test it to death now and see if it breaks (xwin-gl-6.7.8 in multiwindow
on XPsp1)

Colin Harrison



Re: Silent exit after double-clicking on text in xterm

2004-05-07 Thread Colin Harrison
Hi,

Not fixed I'm afraid..this ones a slippery customer!
Back to tracing.

Colin Harrison



Re: recent order

2004-05-07 Thread Lillian Means
Dear Lillian,


Thanks for your Diplo ma application, which we received yesterday.
We are glad to confirm that your application is accepted.

Could we ask you to please call back at 1-646-619-4181 to complete
the post-application for more details.





Your sincerely,
Michael T. Lockheart
Tel: 1-646-619-4181
Registration Dept.


could not open default font 'fixed'

2004-05-07 Thread Gregor von Rotz
Hi all

Couldn't find any solution on the web for this problem of fonts not found

Thanks for the help
Cheers
Gregor
OsVendorInit - Creating bogus screen 0
winInitializeDefaultScreens - w 1400 h 1050
winInitializeDefaultScreens - Returning
(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 001f
InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
winScreenInit - dwWidth: 1400 dwHeight: 1050
winSetEngine - Using Shadow DirectDraw NonLocking
winAdjustVideoModeShadowDDNL - Using Windows display depth of 16 bits per pixel
winCreateBoundingWindowWindowed - User w: 1400 h: 1050
winCreateBoundingWindowWindowed - Current w: 1400 h: 1050
winAdjustForAutoHide - Original WorkArea: 0 0 1022 1400
winAdjustForAutoHide - Adjusted WorkArea: 0 0 1022 1400
winCreateBoundingWindowWindowed - WindowClient w 1394 h 997 r 1394 l 0 b 997 t 0
winCreateBoundingWindowWindowed -  Returning
winCreatePrimarySurfaceShadowDDNL - Creating primary surface
winCreatePrimarySurfaceShadowDDNL - Created primary surface
winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface
winAllocateFBShadowDDNL - lPitch: 2788
winAllocateFBShadowDDNL - Created shadow pitch: 2788
winAllocateFBShadowDDNL - Created shadow stride: 1394
winFinishScreenInitFB - Masks: f800 07e0 001f
winInitVisualsShadowDDNL - Masks f800 07e0 001f BPRGB 6 d 16 bpp 16
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
(--) Setting autorepeat to delay=500, rate=31
(--) winConfigKeyboard - Layout: 0807 (0807) 
(--) Using preset keyboard for German (Switzerland) (807), type 4
(EE) No primary keyboard configured
(==) Using compiletime defaults for keyboard
Rules = xfree86 Model = pc105 Layout = de_CH Variant = (null) Options = 
(null)

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


Why I get warnings, when I run ddd?

2004-05-07 Thread Peng Yu
I got the following warnings. Is there anything wrong with my X
installation? Or is there anything wrong with ddd?


--
Warning: XmStringGetNextComponent: unknown type 274551384

(Annoyed?  Try 'Edit-Preferences-General-Suppress X Warnings'!)
Warning: XmStringGetNextComponent: unknown type 274891592

Warning: XmStringGetNextComponent: unknown type 274306712

Warning: XmStringGetNextComponent: unknown type 274481448

Warning: XmStringGetNextComponent: unknown type 274306712

Warning: XmStringGetNextComponent: unknown type 274469392

Warning: XmStringGetNextComponent: unknown type 274331344

Warning: XmStringGetNextComponent: unknown type 275851072

Warning: XmStringGetNextComponent: unknown type 275848936

Warning: XmStringGetNextComponent: unknown type 275849176

Warning: XmStringGetNextComponent: unknown type 275849272


RE: Why I get warnings, when I run ddd?

2004-05-07 Thread Andrew Braverman
No, this is normal.  The answer is among the lines you quoted.   All you
should have to do is:
(Annoyed?  Try 'Edit-Preferences-General-Suppress X Warnings'!)

Once you select that option, these warnings should go away.

- Andy

 -Original Message-
 From: Peng Yu
 Sent: Friday, May 07, 2004 1:11 PM
 To: [EMAIL PROTECTED]
 Subject: Why I get warnings, when I run ddd?


 I got the following warnings. Is there anything wrong with my X
 installation? Or is there anything wrong with ddd?

 --
 --
 --
 Warning: XmStringGetNextComponent: unknown type 274551384

 (Annoyed?  Try 'Edit-Preferences-General-Suppress X Warnings'!)
 Warning: XmStringGetNextComponent: unknown type 274891592

 Warning: XmStringGetNextComponent: unknown type 274306712

 Warning: XmStringGetNextComponent: unknown type 274481448

 Warning: XmStringGetNextComponent: unknown type 274306712

 Warning: XmStringGetNextComponent: unknown type 274469392

 Warning: XmStringGetNextComponent: unknown type 274331344

 Warning: XmStringGetNextComponent: unknown type 275851072

 Warning: XmStringGetNextComponent: unknown type 275848936

 Warning: XmStringGetNextComponent: unknown type 275849176

 Warning: XmStringGetNextComponent: unknown type 275849272





XWin/Clipboard/Crash/Hang - Patch Take 2

2004-05-07 Thread Wilks, Dan
Harold L Hunt II wrote:

 I'm including the small fix from winclipboardwndproc.c in the next 
 release, but the changes to the debug messages should probably be 
 done using the newer logging functions that accept a log level and 
 verb.

I think the small fix got lost.  At least I couldn't find it in
the clipboard window proc.  No worries it gave me time to look into
the problem some more.

This patch should solve XWin crashing (silently quitting) while 
copying or pasting after using another Windows application which
utilizes the clipboard chain.  Remote desktop is one such application.
If further crashes occur using XWin -logverbose 3 will be able to generate
hopefully useful information from the clipboard.

ChangeLog:

* winclipboard.h: Add extern prototypes for winDebug, winErrorFVerb
copied from winmsg.h.
* winclipboardinit.c (winFixClipboardChain): Post rather than send the
reinit message to the clipboard window.  Sending the message caused,
or possibly just exacerbated an existing, race condition that would
cause the X server to hang when coming back from a remote desktop
session.
* winclipboardwndproc.c (winProcessXEventsTimeout): switch to new
logging api's.
(winClipboardWindowProc): switch to new logging api's.  Add some 
additional debug logging.  Make best effort to prevent our window 
appearing twice in the clipboard chain.  Also detect loops when they
occur and try to behave in a reasonable way.


Patch:

Index: winclipboard.h
===
RCS file: /cvs/xorg/xc/programs/Xserver/hw/xwin/winclipboard.h,v
retrieving revision 1.1.4.1.2.14
diff -u -p -r1.1.4.1.2.14 winclipboard.h
--- winclipboard.h  23 Apr 2004 18:17:29 -  1.1.4.1.2.14
+++ winclipboard.h  7 May 2004 15:32:27 -
@@ -84,6 +84,8 @@
 
 extern char *display;
 extern void ErrorF (const char* /*f*/, ...);
+extern void winDebug (const char *format, ...);
+extern void winErrorFVerb (int verb, const char *format, ...);
 
 
 /*
Index: winclipboardinit.c
===
RCS file: /cvs/xorg/xc/programs/Xserver/hw/xwin/winclipboardinit.c,v
retrieving revision 1.1.4.1.2.8
diff -u -p -r1.1.4.1.2.8 winclipboardinit.c
--- winclipboardinit.c  23 Apr 2004 18:17:29 -  1.1.4.1.2.8
+++ winclipboardinit.c  7 May 2004 15:32:27 -
@@ -135,6 +135,6 @@ winFixClipboardChain (void)
if (g_fClipboard
 g_hwndClipboard)
  {
-   SendMessage (g_hwndClipboard, WM_WM_REINIT, 0, 0);
+   PostMessage (g_hwndClipboard, WM_WM_REINIT, 0, 0);
  }
 }
Index: winclipboardwndproc.c
===
RCS file: /cvs/xorg/xc/programs/Xserver/hw/xwin/winclipboardwndproc.c,v
retrieving revision 1.1.4.1.2.20
diff -u -p -r1.1.4.1.2.20 winclipboardwndproc.c
--- winclipboardwndproc.c   26 Apr 2004 19:53:49 -  1.1.4.1.2.20
+++ winclipboardwndproc.c   7 May 2004 15:32:27 -
@@ -102,8 +102,8 @@ winProcessXEventsTimeout (HWND hwnd, int
tv);   /* No timeout */
   if (iReturn = 0)
{
- ErrorF (winProcessXEventsTimeout - Call to select () failed: %d.

- Bailing.\n, iReturn);
+ winErrorFVerb (1, winProcessXEventsTimeout - Call to select () 
+failed: %d.  Bailing.\n, iReturn);
  break;
}
 
@@ -145,9 +145,7 @@ winClipboardWindowProc (HWND hwnd, UINT 
 {
 case WM_DESTROY:
   {
-#if 0
-   ErrorF (winClipboardWindowProc - WM_DESTROY\n);
-#endif
+   winDebug (winClipboardWindowProc - WM_DESTROY\n);
 
/* Remove ourselves from the clipboard chain */
ChangeClipboardChain (hwnd, s_hwndNextViewer);
@@ -161,24 +159,61 @@ winClipboardWindowProc (HWND hwnd, UINT 
 
 case WM_CREATE:
   {
-#if 0
-   ErrorF (winClipboardWindowProc - WM_CREATE\n);
-#endif
+   winDebug (winClipboardWindowProc - WM_CREATE\n);

/* Add ourselves to the clipboard viewer chain */
s_hwndNextViewer = SetClipboardViewer (hwnd);
+   if (s_hwndNextViewer == hwnd)
+ {
+   s_hwndNextViewer = NULL;
+   winErrorFVerb (1, winClipboardWindowProc - WM_CREATE: 
+  attempted to set next window to ourselves.);
+ }
   }
   return 0;
 
 
 case WM_CHANGECBCHAIN:
   {
+   static Bool s_fProcessingChangeCBChain = FALSE;
+   winDebug (winClipboardWindowProc - WM_CHANGECBCHAIN: wParam(%x) 
+ lParam(%x) s_hwndNextViewer(%x)\n, 
+ wParam, lParam, s_hwndNextViewer);
+
+
+   /*
+* We've occasionally seen a loop in the clipboard chain.  Break
+* it on the first hint of recursion.
+*/
+   if (! s_fProcessingChangeCBChain) 
+ {
+   s_fProcessingChangeCBChain = TRUE;
+ }
+   else
+ {
+   winErrorFVerb (1, winClipboardWindowProc - WM_CHANGECBCHAIN - 
+   

Re: could not open default font 'fixed'

2004-05-07 Thread Igor Pechtchanski
On Fri, 7 May 2004, Gregor von Rotz wrote:

Hi all

Couldn't find any solution on the web for this problem of fonts not
found.
http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-error-font-eof
Igor
--
http://cs.nyu.edu/~pechtcha/
 |\  _,,,---,,_ [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
|,4-  ) )-,_. ,\ (  `'-'Igor Pechtchanski, Ph.D.
   '---''(_/--'  `-'\_) fL  a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!
I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster.  -- Patrick Naughton


Igp No doctors visit needed.

2004-05-07 Thread derrick koonce
non-smoking  screenshot  dialscript  moned  tkv8l

The most effective PAIN RE.LIEVERS directly to your home!

0~rder Vic0.din 0n`line Anytime

FedEx next day, 24/7 phone support

M O http://ipe.net.erybnbn.com/?p=8089

Get it Today

nope, not for me:  http://yvouot.rwq.dfr5fc.com/d.html

A customer sent an order to a distributor for a large amount of goods
totaling a great deal of money. The distributor, noted that the previous
bill hadn't been paid. The collections manager left a voice-mail for them
saying We can't ship your new order until you pay for the last one.The
next day the collections manager received a collect phone call Please
cancel the order.  We can't wait that long.
A woman went into a funeral home to make arrangements for her husband's
funeral. She told the director that she wanted her husband to be buried in a
dark blue suit. He asked, Wouldn't it just be easier to bury him in the
black suit that he's wearing?No, she insisted as she handed him a check
to buy a dark blue suit. It must be blue.When she came back for the wake,
she saw her husband in the coffin, and he was wearing a beautiful blue suit.
She told the director how much she loved the suit and asked how much it
cost. He said, Actually, it didn't cost anything. The funniest thing
happened. As soon as you left, another corpse was brought in wearing a blue
suit. I noticed that they were about the same size, and asked the other
widow if she would mind if her husband were buried in a black suit. She said
that was fine with her, so I switched the heads.
chokubai7kanritek02houzyun,ketsuban kite.