public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Fergus <fergus@bonhard.uklinux.net> To: Cygwin ML X <cygwin-xfree@cygwin.com> Cc: Fergus <fergus@bonhard.uklinux.net> Subject: Re: Updated: xorg-server-1.9.2-1 Date: Mon, 08 Nov 2010 11:51:00 -0000 [thread overview] Message-ID: <4CD7E3A7.3060704@bonhard.uklinux.net> (raw) Dear Jon, Since the update I have been unable to start XWin under [1.7]. Following my usual sequence at a bash prompt: mount n:/tmp /tmp # drive n: is NTFS as required run XWin -multiwindow & Normally these two would be followed by a command line for xterm, but I am not getting that far! The second line repeatedly generates a Cygwin/X error message box, where the reason given is very familiar: Can't read lock file /tmp/.X0-lock I used to get this when /tmp was FAT32 but as you see from line 1 I am making an explicit mount to a NTFS drive, and in the recent past this step has been all that is necessary to make progress. When I open /var/log/xwin/XWin.0.log for more information I read ~> cat /var/log/xwin/XWin.0.log Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.9.2.0 (10902000) Build Date: 2010-11-03 XWin was started with the following command line: /usr/bin/XWin -multiwindow ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1280 h 1024 winInitializeDefaultScreens - native DPI x 96 y 96 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/mandible:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 Fatal server error: Can't read lock file /tmp/.X0-lock [1]+ Done run XWin -multiwindow Can anything be determined from the 3 lines in this file beginning _XSERV ("Unable" .. "failed" .. "failed")? Do I need to change my command sequence? BTW it's interesting (is it?) that the error message refers to 1.9.2.0 not 1.9.2-1. I'm surprised that there are no other anguished reports to you following the update, but I guess that's because the fault/ problem/ difficulty is mine rather than general. ?? Any insights much appreciated. Thank you, Fergus PS It kills me not to copy this to cygwin at cygwin dot com which I feel will have a much wider readership and skill set amongst that readership, but anybody sinning in this regard is always referred straight to Cygwin-X. A strange separation of reporting. Not that I am doubting your specific capability, just the potential for "Me Too" amongst readers. (Or even "Not Me, but I Know What's Going Wrong".) -- 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 reply other threads:[~2010-11-08 11:51 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-08 11:51 Fergus [this message] 2010-11-08 14:06 ` Jon TURNEY 2010-11-09 9:12 ` Fergus 2010-11-10 16:25 ` Jon TURNEY 2010-11-08 17:34 ` Larry Hall (Cygwin X)
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=4CD7E3A7.3060704@bonhard.uklinux.net \ --to=fergus@bonhard.uklinux.net \ --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).