Re: Can't start X after upgrading to cygwin1.7
On 03/02/2010 19:43, Jon TURNEY wrote: I had the same symptoms. Non-administrator WinXP users couldn't start the XWin Server, and no /var/log/XWin.0.log was created. The log file could get created if there wasn't one already present, which led me to put the log file in the user's directory instead of /var/log. The other problem was that users couldn't create the /tmp/.X0-lock file and /tmp/.X11-unix/X0 socket if they were left by another user. The solution was to give each user their own /tmp directory. I fixed it with the following: 1. Added a line in /etc/profile, just before the chmod 1777 /tmp line: mount -f $USERPROFILE/Local Settings/Temp /tmp 2. Changed the XWin Server icon so instead of just startxwin.exe, it says: ... startxwin.exe -- -logfile ~/XWin.log (Don't take out the beginning of the command that runs startxwin through bash, or the /etc/profile won't get run. The quotes are needed because this is the argument to bash's -c option.) Could any of the guru's comment on how good or bad these solutions are? Thanks. It's long been suspected that there is some problem with lockfiles running XWin as a non-administrator user (See FAQ 3.4,[1]), but I've never had a sufficient clear description to understand what the problem is, until now. Okay, thanks to having some useful reproduction steps I've done a bit of testing and generated some patches (at [1]) which should hopefully address some of these issues. The thing I don't understand at this stage is that the /tmp/.X0-lock file and /tmp/.X11-unix/X0 socket should be removed when the X server shuts down, so shouldn't be causing problems. Is there some specific way the server is being exited which doesn't remove these files? [1] http://sourceware.org/bugzilla/show_bug.cgi?id=9778 -- 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: Can't start X after upgrading to cygwin1.7
From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- ow...@cygwin.com] On Behalf Of Jon TURNEY Sent: Wednesday, February 03, 2010 11:44 AM 1. Added a line in /etc/profile, just before the chmod 1777 /tmp line: mount -f $USERPROFILE/Local Settings/Temp /tmp I think it would be better to find the actual /tmp directory and change the Windows permissions to give Full Control to Everyone. This should make the problem 2. Changed the XWin Server icon so instead of just startxwin.exe, it says: ... startxwin.exe -- -logfile ~/XWin.log (Don't take out the beginning of the command that runs startxwin through bash, or the /etc/profile won't get run. The quotes are needed because this is the argument to bash's -c option.) This isn't bad at all. An alternative is to change the permissions on /var/log as above, if you don't mind letting all your users see, and be able to delete or modify, all the cygwin logfiles, but I don't see it as any better. HTH, Mike
Re: Can't start X after upgrading to cygwin1.7
On 23/01/2010 15:37, Jeff Spirko wrote: On Sat, Jan 16, 2010 at 12:56 PM, Andrew Seniora...@andrewsenior.com wrote: I've had cygwin installed for a year on my Thinkpad T61, running Windows XP professional, and just ran the latest setup.exe from cygwin.com. I now can't run X with startxwin.exe (no process appears, no icon in the system tray, clients won't start) No /var/log/Xwin.0.log is written, nor anywhere else I can see in /var/log I think the original poster had a broken installation, there's no other reason for it to get fixed by a reinstall :-) I had the same symptoms. Non-administrator WinXP users couldn't start the XWin Server, and no /var/log/XWin.0.log was created. The log file could get created if there wasn't one already present, which led me to put the log file in the user's directory instead of /var/log. The other problem was that users couldn't create the /tmp/.X0-lock file and /tmp/.X11-unix/X0 socket if they were left by another user. The solution was to give each user their own /tmp directory. I fixed it with the following: 1. Added a line in /etc/profile, just before the chmod 1777 /tmp line: mount -f $USERPROFILE/Local Settings/Temp /tmp 2. Changed the XWin Server icon so instead of just startxwin.exe, it says: ... startxwin.exe -- -logfile ~/XWin.log (Don't take out the beginning of the command that runs startxwin through bash, or the /etc/profile won't get run. The quotes are needed because this is the argument to bash's -c option.) Could any of the guru's comment on how good or bad these solutions are? Thanks. It's long been suspected that there is some problem with lockfiles running XWin as a non-administrator user (See FAQ 3.4,[1]), but I've never had a sufficient clear description to understand what the problem is, until now. The only problem I see with your solution is that you are assuming only a single user is logged in. This might not be the case on a Terminal Server (although it would probably take a specific sequence of privileged/unprivileged logins and XWin startups/shutdowns to show a problem) This would be better fixed in XWin itself by arranging to give these files the correct permissions, if we could work out how to do that :-) [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cant-read-lock-file -- 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: Can't start X after upgrading to cygwin1.7
On 2/3/10 12:43 PM, Jon TURNEY wrote: On 23/01/2010 15:37, Jeff Spirko wrote: On Sat, Jan 16, 2010 at 12:56 PM, Andrew Seniora...@andrewsenior.com wrote: I've had cygwin installed for a year on my Thinkpad T61, running Windows XP professional, and just ran the latest setup.exe from cygwin.com. I now can't run X with startxwin.exe (no process appears, no icon in the system tray, clients won't start) No /var/log/Xwin.0.log is written, nor anywhere else I can see in /var/log I think the original poster had a broken installation, there's no other reason for it to get fixed by a reinstall :-) Maybe there was a reboot in there somewhere. On my XP32 on T61 (configuration determined by my employer) it was frequently necessary and sufficient to reboot before running startxwin. Now I have to take it back as it's failing to perform the first mount during Windows boot. -- 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: Can't start X after upgrading to cygwin1.7
Trying to downgrade to 1.5 with the legacy installer from http://www.cygwin.com/win-9x.html (which would never terminate) and then reinstalling after a reboot with the latest installer fixed the problem. Andrew On Mon, Jan 18, 2010 at 11:27 PM, Andrew Senior a...@andrewsenior.com wrote: Getting the latest cygwin installer (2.677) didn't seem to help with any of my problems. Is there somewhere other than /var/log/Xwin.0.log that I can see some logs for startxwin? I don't see any command line arguments for startxwin that might give me verbose output. Andrew On Sat, Jan 16, 2010 at 12:56 PM, Andrew Senior a...@andrewsenior.com wrote: I've had cygwin installed for a year on my Thinkpad T61, running Windows XP professional, and just ran the latest setup.exe from cygwin.com. At installation time there were some complaints about in use files, though I wasn't to my knowledge running any cygwin processes at the time. I now can't run X with startxwin.exe (no process appears, no icon in the system tray, clients won't start) It (and startx, xinit, Xwin :0) gives me no logging on the console (an rxvt window). No /var/log/Xwin.0.log is written, nor anywhere else I can see in /var/log I've tried reinstalling all the X base packages I can find, or uninstalling and reinstalling a few (including xinit and xorg-server). I've also rebooted several times since first trying this. The start menu icons give me no feedback either, except idle which says Error: could not start C:\Cygwin\bin\idle -display 127.0.0.1:0.0 running xterm, xeyes on the command line gives no error message either. Does anyone have any suggestions please? (One odd thing I notice with 1.7 is that when starting rxvt -e /usr/bin/bash -login it puts me in /bin, whereas it used to put me in my home directory. ~ and $HOME both correctly resolve to c:/aws which is in fstab as /home/aws, as well as listed if I type mount. This happened without running /bin/copy-user-registry-fstab, and that didn't put anything in /etc/fstab.d/. Another is that four packages are always scheduled to be installed (as New) in partial view of setup.exe : glib, gtk+, imlib, tetex, but never seem to be installed, nor are there any failure messages.) Thanks, Andrew I attach a cygcheck output, though I notice various things that look like errors in it: I was using http://www.gtlib.gatech.edu/pub/cygwin/ as my mirror, but setup.exe complained it wasn't an official mirror, so the recent installation was from anl.gov, and I tried pointing to waterloo.edu more recently. Also, it complains that things are hidden in my path by directories, e.g. perl is hidden by a directory named perl. 'which perl' gives the location of the binary. -- 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: Can't start X after upgrading to cygwin1.7
On Sat, Jan 16, 2010 at 12:56 PM, Andrew Senior a...@andrewsenior.com wrote: I've had cygwin installed for a year on my Thinkpad T61, running Windows XP professional, and just ran the latest setup.exe from cygwin.com. I now can't run X with startxwin.exe (no process appears, no icon in the system tray, clients won't start) No /var/log/Xwin.0.log is written, nor anywhere else I can see in /var/log I had the same symptoms. Non-administrator WinXP users couldn't start the XWin Server, and no /var/log/XWin.0.log was created. The log file could get created if there wasn't one already present, which led me to put the log file in the user's directory instead of /var/log. The other problem was that users couldn't create the /tmp/.X0-lock file and /tmp/.X11-unix/X0 socket if they were left by another user. The solution was to give each user their own /tmp directory. I fixed it with the following: 1. Added a line in /etc/profile, just before the chmod 1777 /tmp line: mount -f $USERPROFILE/Local Settings/Temp /tmp 2. Changed the XWin Server icon so instead of just startxwin.exe, it says: ... startxwin.exe -- -logfile ~/XWin.log (Don't take out the beginning of the command that runs startxwin through bash, or the /etc/profile won't get run. The quotes are needed because this is the argument to bash's -c option.) Could any of the guru's comment on how good or bad these solutions are? -Jeff -- Jeff Spirko spi...@gmail.com WD3V |= The study of non-linear physics is like the study of non-elephant biology. -- 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: Can't start X after upgrading to cygwin1.7
Getting the latest cygwin installer (2.677) didn't seem to help with any of my problems. Is there somewhere other than /var/log/Xwin.0.log that I can see some logs for startxwin? I don't see any command line arguments for startxwin that might give me verbose output. Andrew On Sat, Jan 16, 2010 at 12:56 PM, Andrew Senior a...@andrewsenior.com wrote: I've had cygwin installed for a year on my Thinkpad T61, running Windows XP professional, and just ran the latest setup.exe from cygwin.com. At installation time there were some complaints about in use files, though I wasn't to my knowledge running any cygwin processes at the time. I now can't run X with startxwin.exe (no process appears, no icon in the system tray, clients won't start) It (and startx, xinit, Xwin :0) gives me no logging on the console (an rxvt window). No /var/log/Xwin.0.log is written, nor anywhere else I can see in /var/log I've tried reinstalling all the X base packages I can find, or uninstalling and reinstalling a few (including xinit and xorg-server). I've also rebooted several times since first trying this. The start menu icons give me no feedback either, except idle which says Error: could not start C:\Cygwin\bin\idle -display 127.0.0.1:0.0 running xterm, xeyes on the command line gives no error message either. Does anyone have any suggestions please? (One odd thing I notice with 1.7 is that when starting rxvt -e /usr/bin/bash -login it puts me in /bin, whereas it used to put me in my home directory. ~ and $HOME both correctly resolve to c:/aws which is in fstab as /home/aws, as well as listed if I type mount. This happened without running /bin/copy-user-registry-fstab, and that didn't put anything in /etc/fstab.d/. Another is that four packages are always scheduled to be installed (as New) in partial view of setup.exe : glib, gtk+, imlib, tetex, but never seem to be installed, nor are there any failure messages.) Thanks, Andrew I attach a cygcheck output, though I notice various things that look like errors in it: I was using http://www.gtlib.gatech.edu/pub/cygwin/ as my mirror, but setup.exe complained it wasn't an official mirror, so the recent installation was from anl.gov, and I tried pointing to waterloo.edu more recently. Also, it complains that things are hidden in my path by directories, e.g. perl is hidden by a directory named perl. 'which perl' gives the location of the binary. -- 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/
