public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Marc Girod <marc.girod@gmail.com> To: cygwin-xfree@cygwin.com Subject: Re: startx with different displays Date: Mon, 23 Apr 2012 09:34:00 -0000 [thread overview] Message-ID: <33732045.post@talk.nabble.com> (raw) In-Reply-To: <33702991.post@talk.nabble.com> Hi, I try a fresh start, not being clear about my complete failure to get any reply. I use XWin and GNU emacs (X11 version). My startup script is: /usr/bin/startx /usr/bin/emacs -g 90x37+150+0 -- /usr/bin/X :0 -multiwindow -clipboard This used to work for a few years, but recently started to loop and fail (plus 2 glitches). First the loop effect: after starting the server process (transcript not displayed in the first occurrence), which ends in: winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. ...the transcript gets into: waiting for X server to begin accepting connections . .. .. This eventually times out, unless sometimes gets a reply. However, recently, I have started to try different displays in parallel, e.g.: bash --login -c "/usr/bin/startx /usr/bin/emacs -g 90x37+150+0 -- /usr/bin/X :2 -multiwindow -clipboard" I have started to use higher and higher numbers. The effect is that one of then (today: 5) will unblock all the others, so that I got today 5 instances of GNU emacs, all reported a DISPLAY of ":5". The two glitches: Before starting the server, I get: /usr/bin/startx: line 47: 2188 Segmentation fault (core dumped) expr "$1" : ':[0-9][0-9]*$' > /dev/null 2>&1 At connecting, the first line is: xinit: XFree86_VT property unexpectedly has 0 items instead of 1 I notice that I have an old startx~, which helps me to see what has changed in recent versions of startx: bin> diff startx~ startx 34a35,43 > # Automatically determine an unused $DISPLAY > d=0 > while true ; do > [ -e /tmp/.X$d-lock ] || break > d=$(($d + 1)) > done > defaultdisplay=":$d" > unset d > 79c88 < # if no client arguments either, use rc file instead --- > # For compatibility reasons, only use startxrc if there were no client > command line arguments 92,93d100 < < clientargs=$defaultclientargs 96a104,108 > # if no client arguments, use defaults > if [ x"$clientargs" = x ]; then > clientargs=$defaultclientargs > fi > 101c113 < # if no server arguments or display either, use defaults --- > # For compatibility reasons, only use xserverrc if there were no > server command line arguments 103d114 < # For compatibility reasons, only use xserverrc if there were no server command line arguments 109,111d119 < < serverargs=$defaultserverargs < display=$defaultdisplay 114a123,132 > # if no server arguments, use defaults > if [ x"$serverargs" = x ]; then > serverargs=$defaultserverargs > fi > > # if no display, use default > if [ x"$display" = x ]; then > display=$defaultdisplay > fi > 155a174 > touch "$xserverauthfile" bin> ll startx startx~ -rwxr-xr-x 1 emagiro root 4917 Jan 30 03:12 startx -rwxr-xr-x 1 emagiro root 4540 Aug 22 2011 startx~ bin> ll /tmp/.X* -r--r--r-- 1 emagiro EEI-ATusers 11 Apr 23 09:38 /tmp/.X0-lock -r--r--r-- 1 emagiro EEI-ATusers 11 Apr 23 09:40 /tmp/.X1-lock -r--r--r-- 1 emagiro EEI-ATusers 11 Apr 23 09:42 /tmp/.X2-lock -r--r--r-- 1 emagiro EEI-ATusers 11 Apr 23 09:43 /tmp/.X3-lock -r--r--r-- 1 emagiro EEI-ATusers 11 Apr 23 09:44 /tmp/.X4-lock -r--r--r-- 1 emagiro EEI-ATusers 11 Apr 23 09:45 /tmp/.X5-lock /tmp/.X11-unix: total 38 drwxrwxrwt+ 1 root root 0 Apr 23 09:45 . drwxrwxrwt+ 1 emagiro root 0 Apr 23 09:45 .. srwxrwxrwx 1 emagiro EEI-ATusers 0 Apr 23 09:38 X0 srwxrwxrwx 1 emagiro EEI-ATusers 0 Apr 23 09:40 X1 srwxrwxrwx 1 emagiro EEI-ATusers 0 Apr 23 09:42 X2 srwxrwxrwx 1 emagiro EEI-ATusers 0 Apr 23 09:43 X3 srwxrwxrwx 1 emagiro EEI-ATusers 0 Apr 23 09:44 X4 srwxrwxrwx 1 emagiro EEI-ATusers 0 Apr 23 09:45 X5 I don't attempt here to interpret these facts myself. I am of course mostly annoyed by the failure to connect to the XWin server using the first port. Can anybody shed light on a possible explanation? I used Gmane and uploaded my cygcheck.out. Thanks, Marc http://old.nabble.com/file/p33732045/cygcheck.out cygcheck.out -- View this message in context: http://old.nabble.com/startx-with-different-displays-tp33702991p33732045.html Sent from the cygwin-xfree mailing list archive at Nabble.com. -- 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:[~2012-04-23 9:34 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-17 16:49 Marc Girod 2012-04-23 9:34 ` Marc Girod [this message] 2012-04-23 9:48 ` Marc Girod 2012-04-23 14:55 ` Larry Hall (Cygwin-X) 2012-04-24 6:58 ` Marc Girod 2012-04-24 17:33 ` Larry Hall (Cygwin-X) 2012-04-24 21:13 ` Marc Girod 2012-04-24 21:47 ` Larry Hall (Cygwin-X) 2012-04-25 11:50 ` Marc Girod 2012-04-25 21:06 ` Yaakov (Cygwin/X) 2012-04-25 21:27 ` Marc Girod
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=33732045.post@talk.nabble.com \ --to=marc.girod@gmail.com \ --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).