Can't start X after upgrading to cygwin1.7

Jeff Spirko
Sat Jan 23 15:37:00 GMT 2010

> >> On Sat, Jan 16, 2010 at 12:56 PM, Andrew Senior <> 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
> >>
> >> 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 Spirko   WD3V   |=>

The study of non-linear physics is like the study of non-elephant biology.

Unsubscribe info:
Problem reports:

More information about the Cygwin-xfree mailing list