RE: startxwin/XWin won't start properly
Larry Hall (Cygwin X) wrote: On 6/30/2010 1:07 AM, Bradley, Mike wrote: OK, I removed my old cygwin installation (the directory which contains/usr, /bin/, etc.), and re-installed a new version. I kept the cygwin_package directory, but setup.exe did not remember my previous installation. In the past I have had to install cygwin on multiple machines, and it would be nice to learn a way to have a file which describes the packages I want to install, rather than having to recall them all. 'setup.exe' doesn't remember your previous installations - ones you have removed. There'd be little call for that kind of functionality. 'setup.exe' I disagree. I've had to reinstall cygwin from scratch several times, and also have different coworkers who can benefit from cygwin, but saying Go through the long list of groupings, including the even longer sublist of packages, ignoring lib* is not very helpful. Most of my coworkers are not sysadmins or Unix gurus so they look at a lot of packages and say I'll just use puTTY. And it takes a lot of time. But no one wants EVERYTHING, a lot of it is not useful to us. It would be great to be able to have a file I can email them saying Use this, it'll load everything you need.. And of course have a copy for myself for when I get a new machine, or the OS has to be reloaded, or I have cygwin problems (perhaps related to the anti-virus, but still). Such a thing would be great for anyone who wants to test the bleeding edge. If they knew rolling back was simple they'd be encouraged to be daring. does allow you to install from a local directory though. So if you keep the directory that contained all the packages you've downloaded previously, you can point 'setup.exe' at this directory and tell it to install everything. This will help me in some cases, though it won't for my coworkers (none of whom are local to my area). If I renamed the local directory from, say http%3a%2f%2fmirror.mcs.anl.gov%2fcygwin%2f to say http%3a%2f%2fmirror.cs.vt.edu%2fcygwin%2f, will that work? Brian Timares
Re: startxwin/XWin won't start properly
On Tue, Jun 29, 2010 at 11:07:44PM -0600, Bradley, Mike wrote: In the past I have not found a good way to remember which packages where installed (e.g. non-default packages). Is there a file/way to run setup.exe so that a specified set of packages are installed? OK, I removed my old cygwin installation (the directory which contains /usr, /bin/, etc.), and re-installed a new version. I kept the cygwin_package directory, but setup.exe did not remember my previous installation. In the past I have had to install cygwin on multiple machines, and it would be nice to learn a way to have a file which describes the packages I want to install, rather than having to recall them all. So, after being told that Cygwin remembers your previous installation and to just run setup.exe, you removed your previous installation and are surprised that Cygwin doesn't remember it. Here's some more advice for you to misunderstand/ignore: Don't do that. cgf -- 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: startxwin/XWin won't start properly
It would be great to be able to have a file I can email them saying Use this, it'll load everything you need.. And of course have a copy for myself for when I get a new machine, or the OS has to be reloaded, or I have cygwin problems Such a thing would be great for anyone who wants to test the bleeding edge. If they knew rolling back was simple they'd be encouraged to be daring. Absolutely! And I suspect a relatively easy modification/addition for setup.exe. It already has the concept of what's loaded, it's just a matter of storing this off into a single file that is read on subsequent runs of setup.exe. Then when the new install is complete the file is written to. In practice setup.exe would ask if you want to use the default configuration file, or load a separate one. The default Would always be written to. After install the user would then copy and store the default configuration file as a separate one for subsequent use. -Mike
Re: startxwin/XWin won't start properly
On Wed, Jun 30, 2010 at 09:02:34AM -0500, Timares, Brian (Harris) wrote: Larry Hall (Cygwin X) wrote: On 6/30/2010 1:07 AM, Bradley, Mike wrote: OK, I removed my old cygwin installation (the directory which contains/usr, /bin/, etc.), and re-installed a new version. I kept the cygwin_package directory, but setup.exe did not remember my previous installation. In the past I have had to install cygwin on multiple machines, and it would be nice to learn a way to have a file which describes the packages I want to install, rather than having to recall them all. 'setup.exe' doesn't remember your previous installations - ones you have removed. There'd be little call for that kind of functionality. 'setup.exe' I disagree. I've had to reinstall cygwin from scratch several times, and also have different coworkers who can benefit from cygwin, but saying Go through the long list of groupings, including the even longer sublist of packages, ignoring lib* is not very helpful. Most of my coworkers are not sysadmins or Unix gurus so they look at a lot of packages and say I'll just use puTTY. And it takes a lot of time. But no one wants EVERYTHING, a lot of it is not useful to us. You misunderstand what Larry is saying. He is referring to wiping out your installation and then expecting Cygwin to magically remember what you used to have. You are talking about having a fixed set of packages to install and apparently expect that you will be able to use software without actually investigating how to use it. If you read the documentation on setup.exe you'll find how to specify the packages you want on the command line. If you make a .bat file available with the right packages then all of the poor non-UNIX-gurus who can't figure out how to pick openssh from a list will be able to just run pleasedoitforme.bat . OTOH, why not use putty if you don't know linux? cgf -- 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: startxwin/XWin won't start properly
On 6/30/2010 10:15 AM, Christopher Faylor wrote: OTOH, why not use putty if you don't know linux? You haven't been mean enough. ssh is easier to use than putty, regardless of knowledge of linux. -- Tim Prince -- 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: startxwin/XWin won't start properly
So, after being told that Cygwin remembers your previous installation and to just run setup.exe, you removed your previous installation and are surprised that Cygwin doesn't remember it. What I did was re-run setup.exe. XWin would still not startup. Then I Deleted the cygwin install (except for the package directory). Setup.exe Did not recall/remember/read the package directory, it did a default install. The good news is XWin works now. The bad news is I must remember/find/set the Various packages I need in addition to the default. I'm confused as to why the notion of setup.exe to leave a bread-crumb-trail of what was installed for-the-purpose-of driving a subsequent installation is such a controversial issue Here's some more advice for you to misunderstand/ignore: Don't do that. Uh, I think we have a simple misunderstanding... -- 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: startxwin/XWin won't start properly
On Wed, Jun 30, 2010 at 08:36:05AM -0600, Bradley, Mike wrote: cgf wrote: So, after being told that Cygwin remembers your previous installation and to just run setup.exe, you removed your previous installation and are surprised that Cygwin doesn't remember it. What I did was re-run setup.exe. XWin would still not startup. Then I Deleted the cygwin install (except for the package directory). Setup.exe Did not recall/remember/read the package directory, it did a default install. I guess what you're not getting is that the list of installed packages is located within the cygwin installation itself. If you wipe out then setup.exe won't know what's installed. The good news is XWin works now. The bad news is I must remember/find/set the Various packages I need in addition to the default. I'm confused as to why the notion of setup.exe to leave a bread-crumb-trail of what was installed for-the-purpose-of driving a subsequent installation is such a controversial issue It's not controversial since setup.exe already does that. You just chose to wipe out the record of what's installed. If you wanted to just reinstall X you could have just chosen Reinstall and not gone through the pain of wiping out everything. cgf -- 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: startxwin/XWin won't start properly
cgf, I'll start off by saying I sense an attitude of only gurus need apply and gurus don't need help from you. To me that's very OpenBSD, but not very Cygwin. If I sense incorrectly, I suggest what you are writing leads me to feel that way. If that's correct, I suggest we'll never come to an agreement and we may as well drop the subject. Christopher Faylor wrote: On Wed, Jun 30, 2010 at 09:02:34AM -0500, Timares, Brian (Harris) wrote: Larry Hall (Cygwin X) wrote: On 6/30/2010 1:07 AM, Bradley, Mike wrote: OK, I removed my old cygwin installation (the directory which contains/usr, /bin/, etc.), and re-installed a new version. I kept the cygwin_package directory, but setup.exe did not remember my previous installation. In the past I have had to install cygwin on multiple machines, and it would be nice to learn a way to have a file which describes the packages I want to install, rather than having to recall them all. 'setup.exe' doesn't remember your previous installations - ones you have removed. There'd be little call for that kind of functionality. 'setup.exe' I disagree. I've had to reinstall cygwin from scratch several times, and also have different coworkers who can benefit from cygwin, but saying Go through the long list of groupings, including the even longer sublist of packages, ignoring lib* is not very helpful. Most of my coworkers are not sysadmins or Unix gurus so they look at a lot of packages and say I'll just use puTTY. And it takes a lot of time. But no one wants EVERYTHING, a lot of it is not useful to us. You misunderstand what Larry is saying. Actually no, I don't. Although I will admit as I get older I do miss more and more and it is frustrating! He is referring to wiping out your installation and then expecting Cygwin to magically remember what you used to have. Hmm, I don't recall magic being mentioned. I know I have had to wipe out the installation (new laptop, troubles with PC, troubles with Cygwin where one wants a clean install), or find that my chosen install site has dropped off the list, or found that some other site has more up-to-date updates [that matter to me]. And I've wished everytime, from the first reinstallation to the most recent, that I didn't have to go through the list, picking what I know is useful and leaving out what my I don't want or my constraints don't allow. You are talking about having a fixed set of packages to install and apparently expect that you will be able to use software without actually investigating how to use it. If you read the documentation on setup.exe Yes, then no. How long has it been since you've gone through the full list of packages that Cygwin offers? There are 29 catagories and I am NOT counting what is underneath them. Yes, I feel that my coworkers should be able to use, say, X Windows programs, without understanding unix. Or if they do know unix, they should be able to expect that, say, bc is there w/o having to look for it. However this discussion more properly belongs on a more general Cygwin list. I'll see if it makes sense to post a suggestion there. you'll find how to specify the packages you want on the command line. If you make a .bat file available with the right packages then all of the poor non-UNIX-gurus who can't figure out how to pick openssh from a list will be able to just run pleasedoitforme.bat . How many packages are we talking about here? Wait, you don't know. So I'll just reject your suggestion as inappropriate for my situation, although I think for some people it is a pretty good work-around. What Mike and I want is actually pretty reasonable. We want to be able to preserve the work we do in picking the wheat from the chaff (from our point of view) to avoid having our coworkers or ourselves duplicate that work, whether they understand Unix or not (I'm sorry I brought it up! It is largely irrelevant.). It seems simple--at some point the Setup program knows what was selected. It just needs to save it out and be able to read it back in. Brian Timares -- 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/
Setup retaining or saving package selections (was: startxwin/XWin won't start properly)
Brian Timares (me! self-replying) wrote: However this discussion more properly belongs on a more general Cygwin list. I'll see if it makes sense to post a suggestion there. I found something where cgf says the big reason remembered installs aren't done are because it takes someone with the time and skills to do it (SHTDI). http://www.mail-archive.com/cyg...@cygwin.com/msg62416.html I found this http://marc.info/?l=cygwinm=114858695408427w=2 which kinda does what I want. It is still more trouble than I want, but less than giving someone a list of n packages that I've found useful and expecting them to go through the list. Mike, that might be worth a try, though I don't know if it would still work. On considering the later link I realize that it might not be 100% as simple as just saving out a list, unless installing package X automatically and at that point did dependency resolution. I find discussions of this going back to 2002, but the search for the main mail list timed out on me. Anyway, I have to get back to work so I'll try to post to the main list after work. Brian Timares -- 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: RE: startxwin/XWin won't start properly
What Mike and I want is actually pretty reasonable. We want to be able to preserve the work we do in picking the wheat from the chaff (from our point of view) to avoid having our coworkers or ourselves duplicate that work, whether they understand Unix or not (I'm sorry I brought it up! It is largely irrelevant.). It seems simple--at some point the Setup program knows what was selected. It just needs to save it out and be able to read it back in. vote +1 I've also had this need many times. Most recently, the update to the latest cygwin dll, which the instructions specifically said should be a clean install rather than an in-place upgrade. Migration wizard would have been nice... Ryan -- 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/
XTerm scrollbar issue
All releases of xterm newer that 229 (i.e. since June '08) have a broken scrollbar. It never bothered me enough to post a message, but I've been setting up some new systems and have found it annoying to dig up xterm-229 and manually install it. These images show what the scrollbar used to look like (and what it still looks like in all recent Linux distributions, even with latest xterm builds): http://www.donsbox.com/~dfelicia/cygwin-xterm/xterm-229-1.jpg http://www.donsbox.com/~dfelicia/cygwin-xterm/xterm-229-2.jpg The 1st one shows the gray scrollbar shrinking as the history buffer gets filled. The 2nd shows the gray scrollbar moving with a middle-button click-n-drag upwards to view history. These images show what the scrollbar looks like, now, in version 260 (and all versions in between 229 and 260): http://www.donsbox.com/~dfelicia/cygwin-xterm/xterm-260-1.jpg http://www.donsbox.com/~dfelicia/cygwin-xterm/xterm-260-2.jpg The 1st one shows the gray scrollbar as a constant tiny rectangle always at the top, regardless of how many lines of history there are. The 2nd one shows what happens when you do a middle-button click-n-drag. Seemingly a minor nit, especially since we live in an age of wheel mice, but annoying for those of us accustomed to scrolling the old fashioned way. BTW, here's my ~/.Xdefaults, though even without it the behavior is the same: ! Font XTerm*VT100*font: -xos4-terminus-bold-r-normal-*-12-*-*-*-*-*-*-* ! These affect apps like man XTerm*VT100*highlightSelection: true XTerm*VT100*highlightColorMode: true XTerm*VT100*colorBDMode: on XTerm*VT100*colorBD: green XTerm*VT100*colorULMode: on XTerm*VT100*underLine: on XTerm*VT100*colorUL: yellow ! Pretty colors. XTerm*VT100*dynamicColors: on XTerm*VT100*foreground: white XTerm*VT100*background: black XTerm*VT100*cursorColor: white XTerm*VT100*highlightColor: orange ! I need to scroll XTerm*VT100*scrollBar: true XTerm*VT100*saveLines: 2000 XTerm*VT100*scrollTtyOutput:false XTerm*VT100*scrollKey: true XTerm*VT100*JumpScroll: true ! Run login scripts XTerm*VT100*loginShell:true ! Make use of that big monitor XTerm*VT100*geometry: 110x25 ! Allow backspace to work on wrapped lines XTerm*VT100*reverseWrap:true ! I hate beeping XTerm*VT100*visualBell: true ! This resource specifies whether or not to ignore the alternate screen ! of applications such as vi. When it is on, these applications will restore ! the contents of the screen when they are exited to what they were before ! they were started. When it is off, the contents of vi will remain on the ! screen after the program is quit. XTerm*VT100*titeInhibit: true ! New cygwin xterm includes a toolBar by default. Disable it. XTerm*toolBar:false -- 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: startxwin/XWin won't start properly
On 6/30/2010 11:22 AM, Timares, Brian (Harris) wrote: What Mike and I want is actually pretty reasonable. We want to be able to preserve the work we do in picking the wheat from the chaff (from our point of view) to avoid having our coworkers or ourselves duplicate that work, whether they understand Unix or not (I'm sorry I brought it up! It is largely irrelevant.). It seems simple--at some point the Setup program knows what was selected. It just needs to save it out and be able to read it back in. As you mentioned in your follow-up, if what's already supported in 'setup.exe' doesn't meet your needs, you're welcome to modify it. There are several ways to grab a list of installed packages, as has been discussed already (assuming an installation exists at the time you're doing the grabbing). If you want to the dead-simple approach, then you need to use 'setup.exe' to manage and maintain your local installation. If you need to duplicate that installation elsewhere, you use the same installation directory and point 'setup.exe' to it instead of mirrors. Or you set up your own local mirror that you maintain with the packages and versions you want and point 'setup.exe' at that mirror only. Or you grab the output of 'cygcheck -cd' \ (or /etc/setup/installed.db directly) and gently message it to create script with calls 'setup.exe' with the list of packages you'd like from a mirror. Given all the existing options, it's worth your while to take a good look at them all and figure out what they give you and what they don't when matching them against what you need/want. You may find that the solution you want is simply an extension of something that's already there, saving you time and effort all around. If you decide to create a patch, those would go to the cygwin-apps list. Discussion of 'setup.exe' bugs and enhancements go to that list as well. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: Slow response to keypresses in xorg-server-1.8.0-1
On 02/05/2010 21:52, Ken Brown wrote: On 5/1/2010 9:49 AM, Ken Brown wrote: I'm often seeing a very slow response to keypresses under xorg-server-1.8.0-1. The problem is intermittent, but it always happens within a few minutes after starting the server (via the start menu shortcut or a slight variant). Here are some examples: 1. Switching windows with Alt-Tab sometimes takes up to 15 seconds or doesn't work at all (i.e., I get tired of waiting to see if the focus is ever going to switch). 2. When using 'less' to view a file in an xterm window, there is sometimes a delayed response to 'space' or 'q'. 3. When viewing a directory in emacs-X11, pressing 'v' to start viewing a file can sometimes result in a long delay, pressing 'space' to scroll in view mode can be slow, and pressing 'q' to exit view mode can be slow. In some of these cases, I sometimes don't get a response to the first keypress until I press a second key. For example, if I'm viewing a file with 'less', I may press 'q' and get no response. Then pressing 'q' a second time exits 'less' and also produces an echoed 'q' in xterm. Similarly, I'll sometimes press a key, see no echo, and then get two characters echoed at once after pressing a second key. Reverting to xorg-server-1.7.6-2 solves the problem. I'm attaching cygcheck output and an XWin log. I found a test case that I can reproduce reliably on my system. 1. With no .Xdefaults or .startxwinrc, start the X server via the start menu shortcut. 2. Start xfig (with 'xfig ' in the xterm window). 3. Repeatedly press Alt-Tab to switch between the xterm and xfig windows. At some point the focus fails to switch. When this happens, press Alt and the focus switches. Thanks for the clear reproduction steps. And thanks to the other reporters of this problem :-) This is fallout from a change [1] to the way we process Windows messages to handle large bursts of them overflowing the Xserver's internal event queue. It seems that sometimes /dev/windows doesn't seem ready to select() even when there is still Windows messages to process. I can't quite understand how this happens. I don't think this is a bug in cygwin, but probably something subtle to do with message ordering and nonqueued messages (like WM_ACTIVATE). Anyhow, I've cooked up a small additional change which should prevent this blocking behaviour and uploaded a build [2]. It seems to resolve the problem in this specific case. Perhaps you could try it out and see if it helps? [1] http://cygwin.com/ml/cygwin-xfree/2010-02/msg00124.html [2] ftp://cygwin.com/pub/cygwinx/XWin.20100630-git-bc2f74e105146c36.exe.bz2 -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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: RE: startxwin/XWin won't start properly
On Wed, Jun 30, 2010 at 06:11:49PM +0200, Ryan Johnson wrote: What Mike and I want is actually pretty reasonable. We want to be able to preserve the work we do in picking the wheat from the chaff (from our point of view) to avoid having our coworkers or ourselves duplicate that work, whether they understand Unix or not (I'm sorry I brought it up! It is largely irrelevant.). It seems simple--at some point the Setup program knows what was selected. It just needs to save it out and be able to read it back in. vote +1 I've also had this need many times. Most recently, the update to the latest cygwin dll, which the instructions specifically said should be a clean install rather than an in-place upgrade. Sheesh. The instructions did *not* say that a clean install was needed. We tried hard to make sure that wasn't necessary in fact. -- 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: Problem when trying to use -nolock Option
On 29/06/2010 17:13, Mathias Friesenbichler wrote: Hi, I posted this Problem 2 Weeks ago and no one answered yet. Is there anyone who can help me? Yourself, first of all. Try reading the 'Xserver' man page. Thanks, Mathias Original-Nachricht Datum: Thu, 17 Jun 2010 08:24:03 +0200 Von: Mathias Friesenbichlerhia...@gmx.at An: cygwin-xfree@cygwin.com Betreff: Problem when trying to use -nolock Option Hi, My CygwinX is installed on a server. Several users are accessing this installation and therefore i want to use the -nolock option. No. If several users are running X servers on the same computer at the same time, they need to each use a unique display number. '-nolock' is only useful if /tmp resides on a FAT filesystem, which doesn't support the semantics needed by lockfiles, or if a stale lockfile has been left behind by a crashed XWin which you don't have rights to remove. Although i have added this option, cygwinx creates the X1 File in tmp/.X11-unix. So no other user can access cygwin while it is open. The logbook output is then: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.8.0.0 (1080) Build Date: 2010-04-02 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: /usr/bin/Xwin :1 -ac -query 10.8.248.101 -clipboard -logfile C:\DOKUME~1\fltplehr\LOKALE~1\Temp\xwin.fltplehr.1.log -nolock -dpi 75 ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - primary monitor w 1280 h 1024 winInitializeDefaultScreens - native DPI x 96 y 96 winInitializeDefaultScreens - Returning [1061722.984] _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 [1061722.984] _XSERVTransOpen: transport open failed for inet6/pc08309:1 [1061722.984] _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 [1061723.015] _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed [1061723.015] _XSERVTransMakeAllCOTSServerListeners: server already running [1061723.015] Fatal server error: [1061723.015] Cannot establish any listening sockets - Make sure an X server isn't already running I am starting the program with the following code: start O:\PLS_Faser\Cygwin_PLSStarter\cygwin_installed\bin\Xwin.exe :1 -ac -query IP -clipboard -logfile %TEMP%\xwin.%USERNAME%.1.log -nolock -dpi 75 Can you help me? -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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: Setup retaining or saving package selections (was: startxwin/XWin won't start properly)
On Wed, Jun 30, 2010 at 10:51:57AM -0500, Timares, Brian (Harris) wrote: Brian Timares (me! self-replying) wrote: However this discussion more properly belongs on a more general Cygwin list. I'll see if it makes sense to post a suggestion there. I found something where cgf says the big reason remembered installs aren't done are because it takes someone with the time and skills to do it (SHTDI). http://www.mail-archive.com/cyg...@cygwin.com/msg62416.html That post is five years old and unrelated to the topic at hand. This message is referencing the idea to make a windows library for accessing the cygwin mount table. We actually pretty much have that now in fact. But, that message has nothing to do with this. I found this http://marc.info/?l=cygwinm=114858695408427w=2 which kinda does what I want. It is still more trouble than I want, but less than giving someone a list of n packages that I've found useful and expecting them to go through the list. Mike, that might be worth a try, though I don't know if it would still work. You're talking about giving someone a file. So just give them a .bat file that contains something like: setup.exe -P openssh,xorg-x11-base,xorg-x11-bin,xterm and let them run it. That will pull in all of the listed packages and any needed dependencies. On considering the later link I realize that it might not be 100% as simple as just saving out a list, unless installing package X automatically and at that point did dependency resolution. setup.exe handles dependencies. That's a big part of its job. I find discussions of this going back to 2002, but the search for the main mail list timed out on me. Anyway, I have to get back to work so I'll try to post to the main list after work. You can find the discussion by people who don't know about setup.exe command-line options nearly every month in the cygwin mailing list. But, anyway, as Larry says, if you don't like the solutions that are available to do what you want then offering a patch is how you will make things happen. I think most of the setup.exe developers are satisfied with the way things work now and aren't looking to implement something else. cgf -- 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: XTerm scrollbar issue
On Wed, 30 Jun 2010, webmaster wrote: All releases of xterm newer that 229 (i.e. since June '08) have a broken scrollbar. It never bothered me enough to post a message, but I've been setting up some new systems and have found it annoying to dig up xterm-229 and manually install it. These images show what the scrollbar used to look like (and what it still looks like in all recent Linux distributions, even with latest xterm builds): Problems like that shown with the scrollbar are usually a compile-time mismatch on floating-point. There's a configure option for xterm to address this (--enable-narrowproto or --disable-narrowproto), since the mismatch is not detectable via automatic checks. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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: Slow response to keypresses in xorg-server-1.8.0-1
On 6/30/2010 1:40 PM, Jon TURNEY wrote: On 02/05/2010 21:52, Ken Brown wrote: On 5/1/2010 9:49 AM, Ken Brown wrote: I'm often seeing a very slow response to keypresses under xorg-server-1.8.0-1. The problem is intermittent, but it always happens within a few minutes after starting the server (via the start menu shortcut or a slight variant). Here are some examples: 1. Switching windows with Alt-Tab sometimes takes up to 15 seconds or doesn't work at all (i.e., I get tired of waiting to see if the focus is ever going to switch). 2. When using 'less' to view a file in an xterm window, there is sometimes a delayed response to 'space' or 'q'. 3. When viewing a directory in emacs-X11, pressing 'v' to start viewing a file can sometimes result in a long delay, pressing 'space' to scroll in view mode can be slow, and pressing 'q' to exit view mode can be slow. In some of these cases, I sometimes don't get a response to the first keypress until I press a second key. For example, if I'm viewing a file with 'less', I may press 'q' and get no response. Then pressing 'q' a second time exits 'less' and also produces an echoed 'q' in xterm. Similarly, I'll sometimes press a key, see no echo, and then get two characters echoed at once after pressing a second key. Reverting to xorg-server-1.7.6-2 solves the problem. I'm attaching cygcheck output and an XWin log. I found a test case that I can reproduce reliably on my system. 1. With no .Xdefaults or .startxwinrc, start the X server via the start menu shortcut. 2. Start xfig (with 'xfig' in the xterm window). 3. Repeatedly press Alt-Tab to switch between the xterm and xfig windows. At some point the focus fails to switch. When this happens, press Alt and the focus switches. Thanks for the clear reproduction steps. And thanks to the other reporters of this problem :-) This is fallout from a change [1] to the way we process Windows messages to handle large bursts of them overflowing the Xserver's internal event queue. It seems that sometimes /dev/windows doesn't seem ready to select() even when there is still Windows messages to process. I can't quite understand how this happens. I don't think this is a bug in cygwin, but probably something subtle to do with message ordering and nonqueued messages (like WM_ACTIVATE). Anyhow, I've cooked up a small additional change which should prevent this blocking behaviour and uploaded a build [2]. It seems to resolve the problem in this specific case. Perhaps you could try it out and see if it helps? That seems to have fixed it. I've run it for several hours without any problems. Thanks. Ken -- 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: Problem when trying to use -nolock Option
Hi, Thanks for the reply. But you didn’t get my problem. We are several users running X servers over several computers, but starting the X from the same Installation on the network. So the local Computer doesn’t know anything about the other users and therefore we have written a program that manages this problem for us. This program gives each user a unique display number. The problem now is that if I use the “-nolock” option it does the same as if I don’t use it. It also creates those lockfiles. So what can I do to fix this? Thanks, Mathias -Ursprüngliche Nachricht- Von: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] Im Auftrag von Jon TURNEY Gesendet: Mittwoch, 30. Juni 2010 20:03 An: cygwin-xfree@cygwin.com Cc: hia...@gmx.at Betreff: Re: Problem when trying to use -nolock Option On 29/06/2010 17:13, Mathias Friesenbichler wrote: Hi, I posted this Problem 2 Weeks ago and no one answered yet. Is there anyone who can help me? Yourself, first of all. Try reading the 'Xserver' man page. Thanks, Mathias Original-Nachricht Datum: Thu, 17 Jun 2010 08:24:03 +0200 Von: Mathias Friesenbichlerhia...@gmx.at An: cygwin-xfree@cygwin.com Betreff: Problem when trying to use -nolock Option Hi, My CygwinX is installed on a server. Several users are accessing this installation and therefore i want to use the -nolock option. No. If several users are running X servers on the same computer at the same time, they need to each use a unique display number. '-nolock' is only useful if /tmp resides on a FAT filesystem, which doesn't support the semantics needed by lockfiles, or if a stale lockfile has been left behind by a crashed XWin which you don't have rights to remove. Although i have added this option, cygwinx creates the X1 File in tmp/.X11-unix. So no other user can access cygwin while it is open. The logbook output is then: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.8.0.0 (1080) Build Date: 2010-04-02 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: /usr/bin/Xwin :1 -ac -query 10.8.248.101 -clipboard -logfile C:\DOKUME~1\fltplehr\LOKALE~1\Temp\xwin.fltplehr.1.log -nolock -dpi 75 ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - primary monitor w 1280 h 1024 winInitializeDefaultScreens - native DPI x 96 y 96 winInitializeDefaultScreens - Returning [1061722.984] _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 [1061722.984] _XSERVTransOpen: transport open failed for inet6/pc08309:1 [1061722.984] _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 [1061723.015] _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed [1061723.015] _XSERVTransMakeAllCOTSServerListeners: server already running [1061723.015] Fatal server error: [1061723.015] Cannot establish any listening sockets - Make sure an X server isn't already running I am starting the program with the following code: start O:\PLS_Faser\Cygwin_PLSStarter\cygwin_installed\bin\Xwin.exe :1 -ac -query IP -clipboard -logfile %TEMP%\xwin.%USERNAME%.1.log -nolock -dpi 75 Can you help me? -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/ -- Sicherer, schneller und einfacher. Die aktuellen Internet-Browser - jetzt kostenlos herunterladen! http://portal.gmx.net/de/go/atbrowser -- 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/
