Re: Reproducing the cygwin X problems
Mike Ayers wrote: From: Dan Tsafrir Sent: Tuesday, February 24, 2009 11:03 PM However, in an attempt to test your hypothesis, I've set the affinity of XWin.exe, emacs, and the vncviewer to only use CPU0 (through the task manager). I don't think this is a valid test. What is wanted is a P4 single-core hyperthreader with BIOS hyperthread enable (or a multi processor and a screwdriver). Anyone have a single/nulti switchable handy? I'll check my BIOS next reboot. I think a boot.ini entry with /onecpu is the way to do this. But I'm not saying that these problems don't exist on single-core machines (they do, as I am able to reproduce something like the behaviour mentioned), I'm just saying the behaviour may be different (as I don't see exactly the behaviour described), and I do not have the resources to test on a multiple-core machine. -- 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: Reproducing the cygwin X problems; MinTTY, too
Lee D.Rothstein wrote: FWIW, I'm having a similar proble with MinTTY. If I select text in a MinTTY window, then copy text withing a GUI app, like TextPad (http://textpad.com), clipboard stops working for all apps. If I ten return to the original, MinTTY window, and reselect text, paste it, that works and then copy and paste work in all apps, again. MinTTY problems are probably better directed to the cyg...@cygwin.com list or at http://code.google.com/p/mintty/ -- 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: Reproducing the cygwin X problems
> From: Dan Tsafrir [mailto:dan.tsaf...@gmail.com] > Sent: Tuesday, February 24, 2009 11:03 PM > However, in an attempt to test your hypothesis, I've set the affinity > of XWin.exe, emacs, and the vncviewer to only use CPU0 (through the > task manager). I don't think this is a valid test. What is wanted is a P4 single-core hyperthreader with BIOS hyperthread enable (or a multi processor and a screwdriver). Anyone have a single/nulti switchable handy? I'll check my BIOS next reboot. Mike -- 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: Reproducing the cygwin X problems
I have two dual-core systems and they both have clipboard problems. -Chris -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Jon TURNEY Sent: Tuesday, February 24, 2009 2:14 PM To: cygwin-xfree@cygwin.com Cc: dan.tsaf...@gmail.com; mike_ay...@tvworks.com Subject: Re: Reproducing the cygwin X problems Dan Tsafrir wrote: > On Fri, Feb 20, 2009 at 1:05 PM, Mike Ayers wrote: >>I can neither confirm nor deny this, as I don't have ClipBook available. > > Did you try to run 'clipbrd' through start->run ? > > >>I just kill Xwin.exe forcibly in task manager - it takes all X apps with it. > > Right. > > >> However, the better trick I discovered recently is to click on VNC's taskbar >> icon and close it. Once it closes, the X applications recover and can >> cut-n-pste with Windows apps. Also, because VNC is VNC, no setup >> is lost there either - I can reconnect and my console is unharmed. > > This too works for me (but as you say, only if I kill the vncviewer > through the context menu that pops up when right clicking its taskbar > icon; strangely, killing it through the top right x doesn't produce a > similar effect). Thanks! > > >> I suspect the problem here may be contention between the two applications >> that want to share the clipboard. Our other report implicated Office clipboard, >> which may be doing the same thing..? Dan & Mike, Thanks very much for this information on the clipboard problems. I've been able to reproduce something similar to the problems you describe, so I will spend some time trying to fix it. It seems likely that this clipboard contention between multiple applications might behave differently on machines with multi-core processors (which I don't have the capability to test on), so can you indicate if you are using single-core or multi-core processor? -- 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/ -- 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: Reproducing the cygwin X problems; MinTTY, too
Dan Tsafrir wrote: On Tue, Feb 24, 2009 at 2:13 PM, Jon TURNEY > It seems likely that this clipboard contention between multiple applications might behave differently on machines with multi-core processors (which I don't have the capability to test on), so can you indicate if you are using single-core or multi-core processor? Indeed, I'm using a dual core machine. However, in an attempt to test your hypothesis, I've set the affinity of XWin.exe, emacs, and the vncviewer to only use CPU0 (through the task manager). This had no positive affect on the problem: the instant I highlighted some text within emacs my copy-paste functionality was dead, regardless of affinity. --Dan -- 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/ FWIW, I'm having a similar proble with MinTTY. If I select text in a MinTTY window, then copy text withing a GUI app, like TextPad (http://textpad.com), clipboard stops working for all apps. If I ten return to the original, MinTTY window, and reselect text, paste it, that works and then copy and paste work in all apps, again. Lee -- 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: Reproducing the cygwin X problems
On Tue, Feb 24, 2009 at 2:13 PM, Jon TURNEY > > > It seems likely that this clipboard contention between multiple applications > might behave differently on machines with multi-core processors (which I > don't have the capability to test on), so can you indicate if you are using > single-core or multi-core processor? Indeed, I'm using a dual core machine. However, in an attempt to test your hypothesis, I've set the affinity of XWin.exe, emacs, and the vncviewer to only use CPU0 (through the task manager). This had no positive affect on the problem: the instant I highlighted some text within emacs my copy-paste functionality was dead, regardless of affinity. --Dan -- 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: Reproducing the cygwin X problems
> From: cygwin-xfree-ow...@cygwin.com > [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Dan Tsafrir > Sent: Friday, February 20, 2009 6:30 PM > Pardon my ignorance, but until now I wasn't aware there is such a > thing as office clipboard. However, according to this > > http://en.wikipedia.org/wiki/Clipboard_manager > > even if I have it installed, the office clipboard is open as long as > one of the office suite applications are open, and my cygwin > copy-paste problems occur even if the only applications alive are (1) > a cygwin xterm and (2) a vncviewer. So it appears my problem is > unrelated to the office clipboard. Wikipedia?! Try the source. This was the only way I found to ensure that OC is not running: http://support.microsoft.com/kb/207438 I have Office 2003, and OC was disabled by default (because I have the value edition?) HTH, Mike -- 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: Reproducing the cygwin X problems
> From: Jon TURNEY [mailto:jon.tur...@dronecode.org.uk] > Sent: Tuesday, February 24, 2009 11:14 AM > Thanks very much for this information on the clipboard > problems. I've been > able to reproduce something similar to the problems you > describe, so I will > spend some time trying to fix it. Sweet! > It seems likely that this clipboard contention between > multiple applications > might behave differently on machines with multi-core > processors (which I don't > have the capability to test on), so can you indicate if you are using > single-core or multi-core processor? Multi-core, I believe, although I can't tell for sure if I'm not just hyperthreading without rebooting (not an option at the moment). HTH, Mike -- 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: Reproducing the cygwin X problems
Dan Tsafrir wrote: On Fri, Feb 20, 2009 at 1:05 PM, Mike Ayers wrote: I can neither confirm nor deny this, as I don't have ClipBook available. Did you try to run 'clipbrd' through start->run ? I just kill Xwin.exe forcibly in task manager - it takes all X apps with it. Right. However, the better trick I discovered recently is to click on VNC's taskbar icon and close it. Once it closes, the X applications recover and can cut-n-pste with Windows apps. Also, because VNC is VNC, no setup is lost there either - I can reconnect and my console is unharmed. This too works for me (but as you say, only if I kill the vncviewer through the context menu that pops up when right clicking its taskbar icon; strangely, killing it through the top right x doesn't produce a similar effect). Thanks! I suspect the problem here may be contention between the two applications that want to share the clipboard. Our other report implicated Office clipboard, which may be doing the same thing..? Dan & Mike, Thanks very much for this information on the clipboard problems. I've been able to reproduce something similar to the problems you describe, so I will spend some time trying to fix it. It seems likely that this clipboard contention between multiple applications might behave differently on machines with multi-core processors (which I don't have the capability to test on), so can you indicate if you are using single-core or multi-core processor? -- 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: Reproducing the cygwin X problems
Dan Tsafrir wrote: > I confirm this exact behavior. > > This is exactly the problem I'm experiencing in terms of copy-paste on > my XP machine. Specifically, if the vncviewer (TightVNC) is open, and > I select a text in a cygwin xterm or emacs, then copy-paste / > cut-and-paste completely stops functioning on my machine. This doesn't fix the problem, but in the meantime you might find the following makes emacs more usable (and quicker too). I use it because emacs was almost unusable over a slow VPN connection, but it should also help in this situation too. It prevents normal selections in emacs from synchronizing with the X clipboard. Cut/copy/paste within emacs itself works as normal, but much quicker. If you do need to copy from emacs to another app, just use S-delete instead of M-w. To paste from another app into emacs, use S-insert instead of C-y. It's a bit inconvenient, but I soon got used to it. Just add the following code to your .emacs --- snip --- ;;; ;; Code to prevent emacs synchronizing the clipboard with X for every ;; cut & paste operation. This is what slows down emacs most on slow ;; connections. ;; Originally obtained from: ;; http://snarfed.org/space/Emacs%20and%20remote%20X%20Windows ;; but changed the keystrokes to avoid messing up use of escape as meta (setq interprogram-cut-function nil) (setq interprogram-paste-function nil) (global-set-key [S-delete] (lambda () (interactive) (eval-expression '(setq interprogram-cut-function 'x-select-text)) (kill-ring-save (region-beginning) (region-end)) (eval-expression '(setq interprogram-cut-function nil (global-set-key [S-insert] (lambda () (interactive) (eval-expression '(setq interprogram-paste-function 'x-cut-buffer-or-selection-value)) (yank) (eval-expression '(setq interprogram-paste-function nil ;;; --- snip --- Phil -- This email has been scanned by Ascribe PLC using Microsoft Antigen for Exchange. -- 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: Reproducing the cygwin X problems
On Fri, Feb 20, 2009 at 6:21 PM, Williams, Chris (Marlboro) wrote: > > Are you running the office clipboard from Office 2003? Pardon my ignorance, but until now I wasn't aware there is such a thing as office clipboard. However, according to this http://en.wikipedia.org/wiki/Clipboard_manager even if I have it installed, the office clipboard is open as long as one of the office suite applications are open, and my cygwin copy-paste problems occur even if the only applications alive are (1) a cygwin xterm and (2) a vncviewer. So it appears my problem is unrelated to the office clipboard. --Dan -- 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: Reproducing the cygwin X problems
> I am not explicitly running xwinclip - is there an implicit way to be running it? I would think not, that might even be an outdated warning. I don't even have xwinclip installed in my system. If you have it I would just remove it to be on the safe side. -Chris -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Mike Ayers Sent: Friday, February 20, 2009 3:24 PM To: cygwin-xfree@cygwin.com Subject: RE: Reproducing the cygwin X problems > From: cygwin-xfree-ow...@cygwin.com > [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Williams, > Chris (Marlboro) > Sent: Friday, February 20, 2009 12:19 PM > There is also a warning about not usign xwinclip with the -clipboard > switch I am not explicitly running xwinclip - is there an implicit way to be running it? Thanks, Mike -- 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/ -- 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: Reproducing the cygwin X problems
Are you running the office clipboard from Office 2003? -Chris -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Dan Tsafrir Sent: Friday, February 20, 2009 3:55 PM To: cygwin-xfree@cygwin.com Subject: Re: Reproducing the cygwin X problems On Fri, Feb 20, 2009 at 3:19 PM, Williams, Chris (Marlboro) wrote: > > I use the file C:\cygwin\bin\startxwin.bat Me too, so I would guess that the difference in the copy-paste behavior we observe, is unrelated. --Dan -- 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/ -- 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: Reproducing the cygwin X problems
On Fri, Feb 20, 2009 at 3:19 PM, Williams, Chris (Marlboro) wrote: > > I use the file C:\cygwin\bin\startxwin.bat Me too, so I would guess that the difference in the copy-paste behavior we observe, is unrelated. --Dan -- 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: Reproducing the cygwin X problems
> From: cygwin-xfree-ow...@cygwin.com > [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Williams, > Chris (Marlboro) > Sent: Friday, February 20, 2009 12:19 PM > There is also a warning about not usign xwinclip with the -clipboard > switch I am not explicitly running xwinclip - is there an implicit way to be running it? Thanks, Mike -- 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: Reproducing the cygwin X problems
I use the file C:\cygwin\bin\startxwin.bat Which contains: SET CYGWIN_ROOT=\cygwin SET RUN=%CYGWIN_ROOT%\bin\run -p /usr/bin SET PATH=.;%CYGWIN_ROOT%\bin;%PATH% SET XAPPLRESDIR= SET XCMSDB= SET XKEYSYMDB= SET XNLSPATH= %RUN% XWin -multiwindow -clipboard -silent-dup-error -dpi 100 There is also a warning about not usign xwinclip with the -clipboard switch -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Mike Ayers Sent: Friday, February 20, 2009 2:44 PM To: cygwin-xfree@cygwin.com Subject: RE: Reproducing the cygwin X problems > From: cygwin-xfree-ow...@cygwin.com > [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Williams, > Chris (Marlboro) > Sent: Friday, February 20, 2009 11:40 AM > I use the vnc viewer from RealVNC and the X.org server from > cygwin I and > I don't have any copy and paste problems. My problems with > the clipboard > on Windows seem to be related to the Offfice clipboard > application. Once > I shut that down, everything seems fine. In fact, I copy/paste to/from > the RealVNC viewer and X apps all the time. H... which invocation method and clipboard type are you using? I am running `/usr/bin/startx -- -multiwindow -clipboard`. Thanks, Mike -- 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/ -- 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: Reproducing the cygwin X problems
> From: cygwin-xfree-ow...@cygwin.com > [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Williams, > Chris (Marlboro) > Sent: Friday, February 20, 2009 11:40 AM > I use the vnc viewer from RealVNC and the X.org server from > cygwin I and > I don't have any copy and paste problems. My problems with > the clipboard > on Windows seem to be related to the Offfice clipboard > application. Once > I shut that down, everything seems fine. In fact, I copy/paste to/from > the RealVNC viewer and X apps all the time. H... which invocation method and clipboard type are you using? I am running `/usr/bin/startx -- -multiwindow -clipboard`. Thanks, Mike -- 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: Reproducing the cygwin X problems
I use the vnc viewer from RealVNC and the X.org server from cygwin I and I don't have any copy and paste problems. My problems with the clipboard on Windows seem to be related to the Offfice clipboard application. Once I shut that down, everything seems fine. In fact, I copy/paste to/from the RealVNC viewer and X apps all the time. -Chris -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Mike Ayers Sent: Thursday, February 19, 2009 3:50 PM To: cygwin-xfree@cygwin.com Subject: Reproducing the cygwin X problems Lately, I have been having problems with the cygwin X server and cut-n-paste. I have reported a connection to vncclient (RealVNC) - in fact, I don't recall having problems with vncclient not running. These days I use one or the other - so far, so good. Unfortunately, though, I am in the habit of cutting and pasting between vncclient and cygwin X, so if I can be of any tracking the problem down, please let me know. If I have vncclient and an xterm running, simply selecting text on the xterm is sufficient to cause the problem, which I confirm by raising the xterm over the vncclient, then clicking the vncclient to raise it (it then exhibits responsiveness problems). Today I noticed a new problem, which may or may not be related: [SNIP] mike-ayers-lap> ssh -Y -l mayers mikeayers-linux-2 Warning: No xauth data; using fake authentication data for X11 forwarding. Last login: Thu Feb 19 11:54:55 2009 from 192.168.2.87 mikeayers-linux-2> export DISPLAY=192.168.2.87:0 mikeayers-linux-2> xterm Xlib: connection to "192.168.2.87:0.0" refused by server Xlib: No protocol specified xterm Xt error: Can't open display: 192.168.2.87:0 mikeayers-linux-2> [/SNIP] This same technique used to work. The only changes I have made since it last worked was (1) update cygwin, including X, and (2) add " -- -multiwindow -clipboard" to my invocation of startx (I used to get those by default). Let me know if you have trouble reproducing this. HTH, Mike -- 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: Reproducing the cygwin X problems
On Fri, Feb 20, 2009 at 1:05 PM, Mike Ayers wrote: > >I can neither confirm nor deny this, as I don't have ClipBook > available. Did you try to run 'clipbrd' through start->run ? >I just kill Xwin.exe forcibly in task manager - it takes all X apps > with it. Right. > However, the better trick I discovered recently is to click on VNC's taskbar > icon and close it. Once it closes, the X applications recover and can > cut-n-pste with Windows apps. Also, because VNC is VNC, no setup > is lost there either - I can reconnect and my console is unharmed. This too works for me (but as you say, only if I kill the vncviewer through the context menu that pops up when right clicking its taskbar icon; strangely, killing it through the top right x doesn't produce a similar effect). Thanks! > I suspect the problem here may be contention between the two applications > that want to share the clipboard. Our other report implicated Office > clipboard, > which may be doing the same thing..? I strongly suspect cygwin's xorg is solely to blame: this problem was created immediately after my last upgrade of cygwin during which I unwittingly moved from xfree to xorg. (This is only one of the things that want bad for me; I wish there was a way to return to xfree until most of the problems are resolved.) --Dan -- 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: Reproducing the cygwin X problems
> From: cygwin-xfree-ow...@cygwin.com > [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Dan Tsafrir > Sent: Friday, February 20, 2009 9:36 AM > Initially, the only way I was aware of to get the copy-paste > functionality back was to reboot the machine. But recently I've > noticed another way. I run XP's 'clipbrd', which (in the state of no > copy-paste functionality) produces one of these two strange outcomes: > > 1) clipboard displays the following message > > "ClipBook Viewer cannot display the information in its > current format > or there is not enough memory to display it. Quit one or more > applications to increase the available memory, and try again." > > 2) clipboard is "going insane", seemingly trying to endlessly scroll > down (while simultaneously displaying a message saying "Method Open > Fai") and taking up 25-30% of the CPU. > > In both case, if I click the 'delete' button within the clipboard > application (= clear content of clipboard) then the insane behavior > stops and copy-paste starts working again as long as no cygwin X > application is involved. I can neither confirm nor deny this, as I don't have ClipBook available. > But the minute I highlight some text in a > cygwin X application, the insane behavior within clipbrd resumes. The > only way to make things normal again (that I'm aware of) is to kill > cygwin/X (which, in this situation, mandates killing all cygwin > applications through the task-manager, otherwise they refuse to die > and just hang). I just kill Xwin.exe forcibly in task manager - it takes all X apps with it. However, the better trick I discovered recently is to click on VNC's taskbar icon and close it. Once it closes, the X applications recover and can cut-n-pste with Windows apps. Also, because VNC is VNC, no setup is lost there either - I can reconnect and my console is unharmed. I suspect the problem here may be contention between the two applications that want to share the clipboard. Our other report implicated Office clipboard, which may be doing the same thing..? HTH, Mike -- 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: Reproducing the cygwin X problems
On Thu, Feb 19, 2009 at 3:49 PM, Mike Ayers wrote: > >Lately, I have been having problems with the cygwin X server and > cut-n-paste. > I have reported a connection to vncclient (RealVNC) - in fact, I don't recall > having > problems with vncclient not running. These days I use one or the other - so > far, > so good. > >Unfortunately, though, I am in the habit of cutting and pasting > between vncclient > and cygwin X, so if I can be of any tracking the problem down, please let me > know. > >If I have vncclient and an xterm running, simply selecting text on the > xterm is > sufficient to cause the problem, which I confirm by raising the xterm over the > vncclient, then clicking the vncclient to raise it (it then exhibits > responsiveness > problems). I confirm this exact behavior. This is exactly the problem I'm experiencing in terms of copy-paste on my XP machine. Specifically, if the vncviewer (TightVNC) is open, and I select a text in a cygwin xterm or emacs, then copy-paste / cut-and-paste completely stops functioning on my machine. Initially, the only way I was aware of to get the copy-paste functionality back was to reboot the machine. But recently I've noticed another way. I run XP's 'clipbrd', which (in the state of no copy-paste functionality) produces one of these two strange outcomes: 1) clipboard displays the following message "ClipBook Viewer cannot display the information in its current format or there is not enough memory to display it. Quit one or more applications to increase the available memory, and try again." 2) clipboard is "going insane", seemingly trying to endlessly scroll down (while simultaneously displaying a message saying "Method Open Fai") and taking up 25-30% of the CPU. In both case, if I click the 'delete' button within the clipboard application (= clear content of clipboard) then the insane behavior stops and copy-paste starts working again as long as no cygwin X application is involved. But the minute I highlight some text in a cygwin X application, the insane behavior within clipbrd resumes. The only way to make things normal again (that I'm aware of) is to kill cygwin/X (which, in this situation, mandates killing all cygwin applications through the task-manager, otherwise they refuse to die and just hang). --Dan -- 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: Reproducing the cygwin X problems
> From: cygwin-xfree-ow...@cygwin.com > [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Phil Betts > Sent: Friday, February 20, 2009 4:25 AM > > I do not usually set it. I only did so in the sample to satisfy > > FAQ 6.1. ...but set it out of order. I didn't notice that because the results didn't change. Here's the more typical session: [SNIP] mike-ayers-lap> echo $DISPLAY 127.0.0.1:0.0 mike-ayers-lap> ssh -Y may...@mikeayers-linux-2 Warning: No xauth data; using fake authentication data for X11 forwarding. Last login: Fri Feb 20 09:23:39 2009 from 192.168.2.87 mikeayers-linux-2> echo $DISPLAY localhost:15.0 mikeayers-linux-2> xterm Xlib: connection to "localhost:15.0" refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key xterm Xt error: Can't open display: localhost:15.0 mikeayers-linux-2> [/SNIP] HTH, Mike
RE: Reproducing the cygwin X problems
Mike Ayers wrote: > > From: cygwin-xfree-owner at cygwin.com > > [mailto:cygwin-xfree-owner at cygwin.com] On Behalf Of Phil Betts ^^ http://cygwin.com/acronyms/#PCYMTNQREAIYR > > It might have worked, but it was wrong. Do not set the DISPLAY > > environment variable. It is set by ssh -Y to something similar to > > "localhost:10.0" - the actual value depends on whether there are > other > > forwarded X connections to that box. > > I do not usually set it. I only did so in the sample to satisfy > FAQ 6.1. What part of this (from FAQ 6.1): $ DISPLAY=localhost:0.0 $ export DISPLAY $ ssh -Y remotehost says set the DISPLAY to the IP address of the server after starting ssh? Please re-read the FAQ carefully. It works like this. You run "ssh -Y remotehost". ssh makes a connection to $DISPLAY on your local machine (probably ":0"). On the remotehost side, the sshd daemon starts a proxy X server (localhost:10.0 say), and sets $DISPLAY to match. When you start an X application on remotehost, it connects to the proxy server, which forwards all requests to the local host over the ssh tunnel. The ssh process then passes on the requests to the local X server. > >> BEFORE running ssh, you need to ensure that $DISPLAY is set correctly >> for local connections (probably ":0"). > > 127.0.0.1:0, set by the system. I ordinarily do not check it, as > I've never needed to set it when things worked. > >> By specifying your own value for $DISPLAY inside the ssh session, you >> are ensuring that all X traffic bypasses the ssh tunnel and >> sets up its own (insecure and not encrypted) connection. This new >> connection must >> then go through the normal authentication process and it will appear >> to the X server as a remote connection, whereas the ssh connection >> looks like a local connection to the server. > > FAQ needs updating, and my problem remains. No, the FAQ is correct. If you had followed it, and still couldn't connect, then your problem had changed. Your original problem was (probably) because you hadn't given permission for remote connections from mikeayers-linux-2. Since ssh -Y connects as a local program, there are no permission problems (assuming you can run a local xterm). First, make sure your X server is running, and your $DISPLAY is set correctly. Now enter the following commands _exactly_: echo $DISPLAY ssh -Y may...@mikeayers-linux-2 echo $DISPLAY xterm If that doesn't work, paste the results in a reply, along with the output of the xhost command (no parameters) run locally. Note that I sometimes have problems connecting to older Linux boxes, where the first ssh connection fails to set up the proxy. In that case, a second attempt (whilst the first is still connected) succeeds. For example, the first connection sets up a non-working proxy of localhost:10.0. Starting a new session sets up a working proxy of localhost:11.0. You might want to try that trick, but if that works, the problem is on the Linux end. Phil -- This email has been scanned by Ascribe PLC using Microsoft Antigen for Exchange.
RE: Reproducing the cygwin X problems
> From: cygwin-xfree-ow...@cygwin.com > [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Phil Betts > Sent: Thursday, February 19, 2009 1:34 PM > It might have worked, but it was wrong. Do not set the DISPLAY > environment variable. It is set by ssh -Y to something similar to > "localhost:10.0" - the actual value depends on whether there are other > forwarded X connections to that box. I do not usually set it. I only did so in the sample to satisfy FAQ 6.1. > BEFORE running ssh, you need to ensure that $DISPLAY is set correctly > for local connections (probably ":0"). 127.0.0.1:0, set by the system. I ordinarily do not check it, as I've never needed to set it when things worked. > By specifying your own value for $DISPLAY inside the ssh session, you > are ensuring that all X traffic bypasses the ssh tunnel and > sets up its > own (insecure and not encrypted) connection. This new > connection must > then go through the normal authentication process and it will appear > to the X server as a remote connection, whereas the ssh connection > looks like a local connection to the server. FAQ needs updating, and my problem remains. Thanks, Mike
RE: Reproducing the cygwin X problems
Mike Ayers wrote: > Today I noticed a new problem, which may or may not be related: > > [SNIP] > mike-ayers-lap> ssh -Y -l mayers mikeayers-linux-2 > Warning: No xauth data; using fake authentication data for X11 > forwarding. > Last login: Thu Feb 19 11:54:55 2009 from 192.168.2.87 > mikeayers-linux-2> export DISPLAY=192.168.2.87:0 > mikeayers-linux-2> xterm > Xlib: connection to "192.168.2.87:0.0" refused by server > Xlib: No protocol specified > > xterm Xt error: Can't open display: 192.168.2.87:0 > mikeayers-linux-2> > [/SNIP] > > This same technique used to work. The only changes I have made > since it last worked was (1) update cygwin, including X, and (2) add " > -- -multiwindow -clipboard" to my invocation of startx (I used to get > those by default). > It might have worked, but it was wrong. Do not set the DISPLAY environment variable. It is set by ssh -Y to something similar to "localhost:10.0" - the actual value depends on whether there are other forwarded X connections to that box. BEFORE running ssh, you need to ensure that $DISPLAY is set correctly for local connections (probably ":0"). By specifying your own value for $DISPLAY inside the ssh session, you are ensuring that all X traffic bypasses the ssh tunnel and sets up its own (insecure and not encrypted) connection. This new connection must then go through the normal authentication process and it will appear to the X server as a remote connection, whereas the ssh connection looks like a local connection to the server. Phil -- This email has been scanned by Ascribe PLC using Microsoft Antigen for Exchange.
