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: Cygwin-X on Windows 7 Beta Success!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Paul Loewenstein wrote: > GNUemacs does not survive rebaseall. Known issue; reinstall the libncurses7 (and libtiff4?) DLLs. Yaakov Cygwin/X -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkmku9sACgkQpiWmPGlmQSO4CACfXtoPzOo9p3zBXfpOuZ+Z+hWB JNwAn3AYjRvwZ7uwe7Nn/sLUniUreQvj =G4Xl -END PGP SIGNATURE- -- 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: X server causing IE lockups
On Tue, 10 Feb 2009 13:05:36 -0500 Frédéric Bron wrote: > > Maybe we have an exploit on our systems. > > Or possibly we have the same video driver? > > Or same network card. Etc. > > I'll gather together what hardware I've got and we can compare. > > I have a notebook : DELL Latitude D830, Video = nVidia Quadro NVS 140M I have an ATI Mobility FireGL V5k. But I have put this on the back-back burner for now. My work-around is to only use X for when I need gnuplot and then I exit from X. -- 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: Cygwin-X on Windows 7 Beta Success!
Fredrik, Thanks! I got it working with a reinstall and a rebaseall with double the default offset. GNUemacs does not survive rebaseall. Paul Fredrik Staxeng wrote: Paul Loewenstein writes: Fredrik, On 64-bit Windows 7, I cannot get Cygwin/X windows to accept keyboard input. Are you using 32-bit or 64-bit? 64. -- 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: xdvi unexplained locale problem
Dan Tsafrir wrote: On Wed, Feb 18, 2009 at 3:02 PM, Mike Ayers wrote: Dan Tsafrir wrote: open xdvi, I get the following error message: Warning: locale not supported by C library, locale unchanged Warning: locale not supported by Xlib, locale set to C Warning: X locale modifiers not supported, using default Warning: Unable to load any usable fontset Try unsetting LOCPATH: This didn't work either. In fact, I tried unset-ing this and very many other env variables before posting the question here. I'm sorry, I must have left my telepathy switched off. Anything else that you've tried that you'd like to mention now :-) Looking at your cygcheck output some more, I notice you seem to have a lot of old X DLLs in /usr/X11R6/bin/ (which should have been removed by setup, but haven't been for some reason [in use when setup was run?]). Since xdvi is still in /usr/X11R6/bin, this might well be causing a problem (the Windows loader looks in the directory from which the application loaded to find DLLs first, I think?) It seems to me that the behavior is unrelated to any env variables. It appears as though, for some unexplained reason, somewhere along the way, xdvi or X think they need to change to a locale other than C. Googling the error messages shows that ubuntu users faced a similar problem in early 2007 (related to xdvi and xfig): https://bugs.launchpad.net/ubuntu/+source/control-center/+bug/2066 I don't actually see the "locale not supported" warning anywhere in that bug report, so I am unsure of it's relevance. Some thought it was an xorg problem. The suggested workarounds (e.g., setting a LANG=C env var) don't work for me. Am I the only one that gets this error message for xdvi on cygwin? I'm sorry to say that, yes, you are abnormal :-) xdvi runs without this error message for me. -- 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: "-query" not working on cygwin/windows
km4hr wrote: > Phil Betts-2 wrote: >> >> km4hr wrote: >> >> Perhaps you missed my suggestions here: >> http://cygwin.com/ml/cygwin-xfree/2009-02/msg00222.html >> >> Try the telnet check first to see if the port is accessible from >> Windows >> because that only takes a few seconds. (Make sure you run the cygwin >> telnet.exe) >> > Phil, > > Thanks for hanging in there. > > I tried your telnet suggestion. I get the following: > > $telnet xxx.xxx.xxx.xxx 6000 > trying xxx.xxx.xxx.xxx... > Connected to xxx.xxx.xxx.xxx. > Escape character is '^]'. > > The above is all I get. A login prompt never appears. I waited for > several minutes. > > When I press Ctrl-c I get: > "Connection closed by foreign host. > > If I telnet using an unopen port I the response gets past the > "trying" > statement. > Your quoting went a bit wrong there. Sorry, I should have explained that that was the expected outcome. If you get the "Connected to" message, the port is open and you can close the connection. The proper way to terminated a telnet session from that situation is to press Ctrl-] (the "Escape character" mentioned in the message). You then get a telnet prompt, where you just type quit. You wouldn't normally expect a prompt (unless the port was 23 - telnet's own). In theory, if you knew enough about the protocol expected on the opened port, you could simulate a normal connection and debug the connection using telnet, but you have to have a certain masochistic streak to try it! So, now we know that the port is accessible from Windows. In that case, it *should* work, so something else is interfering. Have you investigated the BLODA angle? Prime suspects are anti-virus and other "security" software, but hardware drivers have caused problems too. These programs inject themselves into every running process at a fairly low level and, whilst they are mostly benign, can cause nasty, spurious problems, particularly when the code you are trying to run is slightly off the beaten track. X and XCMCP probably falls into that category for Windows machines. The usual advice is to uninstall these, rather than just disable them. The faulty components are frequently left in place when "disabled". Once you have ruled out a candidate, you can reinstall it. If you do find one that is causing the problem, it may be possible to configure it in a way which avoids the problem (e.g. disabling real-time virus scanning). You can often spot BLODA by running the program which is failing, and then seeing which DLLs are loaded using something like Process Explorer. Any unexpected DLLs, particularly if not under C:\Windows or C:\cygwin are prime suspects. In your case, because the -query option is failing, you won't get chance to see the DLLs before X terminates, so you could just start a normal server (e.g. via startxwin.bat) instead. You may find that an app that is not on the BLODA is causing the problem. If so, a message to the main cygwin list would be appreciated so that the BLODA can be updated. If the BLODA hunt fails, you could try running the server via strace so that the point of failure might be spotted, but I'm not familiar with the source. Yaakov or Jon would probably be better at making sense of that. 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/
Xwin_GL source (was Re: X.org 7.4 dying under Geomview)
Phil Betts wrote: If acceleration matters so much to you, I'm sure Yaakov and Jon would welcome patches to enable it ;-) The source for the experimental version isn't available via setup.exe, and I haven't been able to locate the source elsewhere. Since the original package is still available (even if obsolete), I thought that the GPL insisted that the source was similarly available. I would like to take a diff of the two X11R6 server packages, with a view to merging the changes into the current, much changed, source, but without access to the source for both accelerated and unaccelerated, this is impossible. Does anyone know where one might find the source package for xorg-x11-xwin-gl-6.8.99.901-1? I've tried the Cygwin Time Machine, but it appears to be down. As far as I know, there is no separate source package for xwin-gl, it is simply the same X server built with different flags. This mail [1], linked to from the todo web page, seems to explain how to build with the acceleration code enabled, in the old, Imakefile'd monolithic tree. I haven't looked at all as to if it's a simple of just finding the correct thing to turn on in the modular tree, or how much this has rusted due to other internal changes in the X server or GLX over the intervening years. http://cygwin.com/ml/cygwin-xfree/2004-03/msg1.html -- 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: update - Vista: no copy/paste X -> MS
Dick Repasky-2 wrote: > > not being able to copy from an X application (xterm or nedit) and paste > into Windows Notepad. > For what it's worth, and notwithstanding the need for deeper analysis and a fix, I can report that, disabling the Office clipboard (e.g. from Outlook), copy&paste work for me from emacs run on X to the Windows Notepad, on Vista. Marc Windows Longhorn/Vista (not yet supported!) Ver 6.0 Build 6000 ... Cygwin DLL version info: DLL version: 1.5.25 DLL epoch: 19 -- View this message in context: http://www.nabble.com/update---Vista%3A-no-copy-paste-X--%3E-MS-tp22164522p22181085.html Sent from the cygwin-xfree mailing list archive at Nabble.com. -- 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/
