This is the mail archive of the cygwin-xfree@cygwin.com mailing list for the Cygwin XFree86 project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Harold, The contents of the c:\cygwin\tmp\XWinrl.log (/tmp/XWinrl.log) file is listed below. From the contents, is this the same as /tmp/XWin.log? Anyway, looking at the end of the log file it looks like the clipboard option couldn't open the display. This raises several issues. 1) The DISPLAY variable may not be set when the "XWin -query" command is issued (no X server). 2) The user has to log on to the remote system via the CDE logon windows, set their DISPLAY, and open it up to remote access via "xhost +" 3) What should the timing be for the clipboard option (The wait period might need to be changed from 4 to 30 seconds). Using xwinclip by itself didn't work and it didn't write anything in /tmp/Xwinrl.log file. Thanks for attempting to resolve this issue! Rex ___________________________________________ $ cat /tmp/XWinrl.log ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 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: 1280 h: 1024 winCreateBoundingWindowWindowed - Current w: 1280 h: 1024 winAdjustForAutoHide - Original WorkArea: 0 0 1024 1280 winAdjustForAutoHide - Taskbar is auto hide winAdjustForAutoHide - Found BOTTOM auto-hide taskbar winAdjustForAutoHide - Adjusted WorkArea: 0 0 1023 1280 winCreateBoundingWindowWindowed - WindowClient w 1280 h 1023 r 1280 l 0 b 1023 t 0 winCreateBoundingWindowWindowed - Returning winCreatePrimarySurfaceShadowDDNL - Creating primary surface winCreatePrimarySurfaceShadowDDNL - Created primary surface winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface winAllocateFBShadowDDNL - lPitch: 5120 winAllocateFBShadowDDNL - Created shadow pitch: 5120 winAllocateFBShadowDDNL - Created shadow stride: 1280 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff winInitVisualsShadowDDNL - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 winCreateDefColormap - Deferring to fbCreateDefColormap () winFinishScreenInitFB - Calling winInitClipboard. winInitClipboard () winFinishScreenInitFB - returning winScreenInit - returning InitOutput - Returning. winClipboardProc - Hello winClipboardProc - Calling pthread_mutex_lock () (EE) No primary keyboard configured (==) Using compiletime defaults for keyboard Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" Options = "(n ull)" winBlockHandler - Releasing pmServerStarted winClipboardProc - pthread_mutex_lock () returned. DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - Calling setlocale () winBlockHandler - pthread_mutex_unlock () returned winClipboardProc - setlocale () returned winClipboardProc - pthread_mutex_unlock () returned. winClipboardProc - XInitThreads () returned. winClipboardProc - DISPLAY=:0.0 AUDIT: Mon May 12 13:35:24 2003: 1684 xwin: client 3 rejected from local host winClipboardProc - Could not open display, try: 1, sleeping: 4 AUDIT: Mon May 12 13:35:30 2003: 1684 xwin: client 5 rejected from local host winClipboardProc - Could not open display, try: 2, sleeping: 4 AUDIT: Mon May 12 13:35:34 2003: 1684 xwin: client 12 rejected from local host winClipboardProc - Could not open display, try: 3, sleeping: 4 winClipboardProc - Failed opening the display, giving up <<XWinrl.log>> > -----Original Message----- > From: KIDWELL, REX (SBCSI) > Sent: Monday, May 12, 2003 12:43 PM > To: 'cygwin-xfree@cygwin.com' > Subject: XFree86 - Windows cut/paste functionallity > > The following Xwin is used to start a full session on a remote system. > > xwin -kb -query hostname1 -nodecoration -clipboard -fp tcp/hostname2:7100 > & > > Xfree and Windows aren't seeing each others clipboards. Running xwinclip > in the background doesn't seem to help. Xwinclip also has bad side > effects on the xfree highlight (reverse video). > > The desktop system is Evo 510 running W2K with SP1. > > Cygwin/XFree86.base version is 4.2.0-1. > > Should xwinclip be started after "xwin -clipboard"? > > > > > -----Original Message----- > From: KIDWELL, REX (SBCSI) > Sent: Monday, May 12, 2003 10:39 AM > To: 'cygwin-xfree@cygwin.com' > Subject: RE: Running Xwin in passive mode > > Thanks for the help your suggestions did the job. > > This raised two unrelated questions. > > Where can I find a current list of command line options for Xwin? > I've seen and used -ac, -multiwindow, and -clipboard but they aren't > documented in the online reference or the supplied man page. > > I also could not find any help on how to use xwinclip. I was > looking for help on what the keyboard and mouse sequences are to cut and > paste between a X-term and Notepad. Control-C and Control-V don't mean > the same think within a x-term/dtterm. The documentation I found only > talks about how to start xwinclip. > > Rex > > -----Original Message----- > From: KIDWELL, REX (SBCSI) > Sent: Tuesday, May 06, 2003 8:50 AM > To: 'cygwin-xfree@cygwin.com' > Subject: Running Xwin in passive mode > > Has anyone figured out how to run Xwin in the passive mode > (sorry Exceed terminology)? > > Passive mode is defined as starting a Xserver in the > background without a full screen session manager. The goal is to display > individual X clients like any other program running on a Windows platform. > I.E. run remote xterms and dtterms from remote systems and display them > like a DOS CMD window. > > An additional requirement would be to run them from a single > Xwin invocation so cut and paste would be supported between xterms.
Attachment:
XWinrl.log
Description: Binary data
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |