public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk> To: cygwin-xfree@cygwin.com Subject: Re: Can't start X after upgrading to cygwin1.7 Date: Wed, 03 Feb 2010 19:43:00 -0000 [thread overview] Message-ID: <4B69D1F3.704@dronecode.org.uk> (raw) In-Reply-To: <fe760d9b1001230737l12389acdjaa3f61c75e7f423a@mail.gmail.com> On 23/01/2010 15:37, Jeff Spirko wrote: >>>> On Sat, Jan 16, 2010 at 12:56 PM, Andrew Senior<aws@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/
next prev parent reply other threads:[~2010-02-03 19:43 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <4d810821001160955i5026ff4cyd6ec87b960d6adc7@mail.gmail.com> [not found] ` <4d810821001160956n77aaf352n7b391176a03eb096@mail.gmail.com> 2010-01-17 1:43 ` Fwd: " Larry Hall (Cygwin X) 2010-01-19 4:27 ` Andrew Senior 2010-01-23 14:02 ` Andrew Senior 2010-01-23 15:37 ` Jeff Spirko 2010-02-03 19:43 ` Jon TURNEY [this message] 2010-02-03 22:51 ` Tim Prince 2010-02-04 22:06 ` Mike Ayers 2010-02-09 18:20 ` Jon TURNEY
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4B69D1F3.704@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).