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: 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: 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/
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/
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
> 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 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
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
> 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 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
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 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' 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. -- 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: startxwin/XWin won't start properly
> 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. > Actually, that's not what I meant at all. Your cygcheck output showed that > you had, at one time, installed Cygwin to C:\cygwin and C:\cygwin\cygdrive, > both of which are now "ORPHANED", meaning that at least some (could be all) > of the installation is now missing. You should make sure that the entire > installation has been deleted in both places. > ... I did remove the orphaned directires, but it did not help. The good news is a complete re-install of cygwin does work, so I am (almost) up and running :-) Thanks, -Mike
Re: startxwin/XWin won't start properly
On 6/29/2010 6:56 PM, Bradley, Mike wrote: -Original Message- From: cygwin-xfree-ow...@... [mailto:cygwin-xfree-ow...@...] On Behalf Of Larry Hall (Cygwin X) Sent: Tuesday, June 29, 2010 6:40 PM To: cygwin-xf...@... Subject: Re: startxwin/XWin won't start properly <http://cygwin.com/acronyms/#PCYMTNQREAIYR> Also, there's nothing to be gained (and plenty to be lost) by including unneeded headers in your reply. Please consider removing them in future correspondences with the list. Remove the DISPLAY setting. Update your installation (your cygwin package is out-of-date). You also have a couple of orphaned installations of Cygwin. Make sure those are all cleaned up/out. Hi, 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? Not surprisingly, Chris got this right on the nose. It would be ludicrous for me to embellish. :-) (I have several times just run setup.exe, and it does seem to update some packages, but as you state, it is not completely clean) Actually, that's not what I meant at all. Your cygcheck output showed that you had, at one time, installed Cygwin to C:\cygwin and C:\cygwin\cygdrive, both of which are now "ORPHANED", meaning that at least some (could be all) of the installation is now missing. You should make sure that the entire installation has been deleted in both places. Once that is true, you should run 'cygcheck --delete-orphaned-installation-keys' so that cygcheck will not report those directories anymore. This is something completely different from 'setup.exe' and its installation process. 'setup.exe' knows what it has installed and where and will maintain those packages (updating them as required and requested) whenever you run it. It cannot, however, maintain an installation if it has been removed or manipulated by other tools, which is what seems to have happened to your two orphaned installations. So you need to finish cleaning these up as I described above. It may simply be a bookkeeping exercise or it might be more than that. But it's worth checking out. -- 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: startxwin/XWin won't start properly
On Tue, Jun 29, 2010 at 04:56:03PM -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? Every time you select a new package to install, it is added to the remembered list of packages on your system. So, the next time you run setup.exe it will update anything that is out of date automatically. 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
Hi, 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? I say this, because the only way I know to clean up the install is to delete it, and re-install. (I have several times just run setup.exe, and it does seem to update some packages, but as you state, it is not completely clean) Thanks, -Mike -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Larry Hall (Cygwin X) Sent: Tuesday, June 29, 2010 6:40 PM To: cygwin-xfree@cygwin.com Subject: Re: startxwin/XWin won't start properly On 6/29/2010 10:50 AM, Bradley, Mike wrote: > Hi, > > All was good, till a couple weeks ago when I added some packages to cygwin, > and several packages where also upgraded. Then xterm response time became > very slow. I tried a second upgrade yesterday, and now I cannot even start > an xterm, nor will startxwin start properly. This is a company computer > which has Symantec anti-virus. I tried disabling that as well. > > Here is the most obvious symptom: > > % echo $DISPLAY 127.0.0.1:0.0 % /usr/bin/startxwin.exe > > > waiting for X server to begin accepting connections . .. giving up. > /usr/bin/startxwin: Socket type not supported (errno 124): unable to > connect to X server /usr/bin/startxwin: No such process (errno 3): Server > error. > > Notice the value of $DISPLAY above, which does not match whats in XWin.0.log > (it has :0.0). No idea how/why that happens. Remove the DISPLAY setting. Update your installation (your cygwin package is out-of-date). You also have a couple of orphaned installations of Cygwin. Make sure those are all cleaned up/out. -- 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: startxwin/XWin won't start properly
On 6/29/2010 10:50 AM, Bradley, Mike wrote: Hi, All was good, till a couple weeks ago when I added some packages to cygwin, and several packages where also upgraded. Then xterm response time became very slow. I tried a second upgrade yesterday, and now I cannot even start an xterm, nor will startxwin start properly. This is a company computer which has Symantec anti-virus. I tried disabling that as well. Here is the most obvious symptom: % echo $DISPLAY 127.0.0.1:0.0 % /usr/bin/startxwin.exe waiting for X server to begin accepting connections . .. giving up. /usr/bin/startxwin: Socket type not supported (errno 124): unable to connect to X server /usr/bin/startxwin: No such process (errno 3): Server error. Notice the value of $DISPLAY above, which does not match whats in XWin.0.log (it has :0.0). No idea how/why that happens. Remove the DISPLAY setting. Update your installation (your cygwin package is out-of-date). You also have a couple of orphaned installations of Cygwin. Make sure those are all cleaned up/out. -- 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: startxwin/XWin won't start properly
I just tried your procedure, but still get the same error messages from startxwin. Maybe there is some helpful information in the logfiles I sent? -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Markus Hoenicka Sent: Tuesday, June 29, 2010 11:45 AM To: cygwin-xfree@cygwin.com Subject: RE: startxwin/XWin won't start properly "Bradley, Mike" was heard to say: > I don't see any difference if I set DISPLAY to :0.0 or > 127.0.0.1:0.0. However, in the past its only worked if I set to > 127.0.0.1:0.0 > My current procedure to start X is as follows: 1. do not set $DISPLAY anywhere. It is just empty. 2. open MinTTY 3. type something like "startxwin /usr/bin/emacs" That's about it. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 -- 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: startxwin/XWin won't start properly
"Bradley, Mike" was heard to say: I don't see any difference if I set DISPLAY to :0.0 or 127.0.0.1:0.0. However, in the past its only worked if I set to 127.0.0.1:0.0 My current procedure to start X is as follows: 1. do not set $DISPLAY anywhere. It is just empty. 2. open MinTTY 3. type something like "startxwin /usr/bin/emacs" That's about it. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 -- 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
I don't see any difference if I set DISPLAY to :0.0 or 127.0.0.1:0.0. However, in the past its only worked if I set to 127.0.0.1:0.0 -Original Message- From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Markus Hoenicka Sent: Tuesday, June 29, 2010 10:55 AM To: cygwin-xfree@cygwin.com Subject: RE: startxwin/XWin won't start properly "Bradley, Mike" was heard to say: > Notice the value of $DISPLAY above, which does not match whats in > XWin.0.log (it has :0.0). No idea how/why that happens. > $DISPLAY is empty over here unless I manually set it. But then, I'm not sure if it has something to do with your problems, as 127.0.0.1:0.0 points to the first display on localhost, which IMHO isn't all that wrong. What happens if you set $DISPLAY manually, e.g. to ":0.0". This always worked fine for me. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 -- 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: startxwin/XWin won't start properly
"Bradley, Mike" was heard to say: Notice the value of $DISPLAY above, which does not match whats in XWin.0.log (it has :0.0). No idea how/why that happens. $DISPLAY is empty over here unless I manually set it. But then, I'm not sure if it has something to do with your problems, as 127.0.0.1:0.0 points to the first display on localhost, which IMHO isn't all that wrong. What happens if you set $DISPLAY manually, e.g. to ":0.0". This always worked fine for me. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 -- 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/