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 Cc: gbarrick@kent.edu Subject: Re: Dfficulty with xorg-server-1.17.1-2. Date: Tue, 24 Feb 2015 21:44:00 -0000 [thread overview] Message-ID: <54ECEFA2.7050207@dronecode.org.uk> (raw) In-Reply-To: <CAKST5xOu6paHhw=upDLk26Xe7_8xKiLM=M5V1LSJ8SKix8WCUw@mail.gmail.com> On 24/02/2015 18:03, GEORGE BARRICK wrote: > I've been using xlaunch with a windows desktop shortcut for > about a year to start a multi-window instance of xwin on my Win7 > computers. [snip] > OK. Now for the difficulty. I recently (today) updated my > cygwin system to include the newest xorg-server, xorg-server-common > and xorg-server-dmx (the 1.17.1-2 versions) as well as > xf86-video-dummy_0.3.7-3 xf86-video-nested-0.1.0-6 and xinit_1.3.4-5, > and have found that xlaunch no longer seems capable of finding my > .xlaunch-file. It starts X as before, but does not automatically spin > up the xterm that my .xlaunch-file requests. I wind up having to start > an xterm manually from the xwin "Applications" menu. > > In summary, I have changed _nothing_ except for the new X-stuff, > and have this problem. The log-file from xwin does not seem radically > different: [snip] > The other notable problem to report is that my X-server now > crashes after about 5-10 minutes of use. [snip] > P.S. Excuse verbosity of this report; I've tried to give complete > description. Thanks for providing such a detailed report, this enabled me to quickly reproduce what I think is the issue. This seems to be a problem with xlaunch, which needs a small update to work correctly with xserver 1.17. I've just uploaded xlaunch-20150224-1, which should fix this. I think this is actually also the cause of your 'crashes' as well. After about 12 minutes, xlaunch is deciding that the X server hasn't started successfully and is killing it. -- 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/
prev parent reply other threads:[~2015-02-24 21:39 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-24 18:13 GEORGE BARRICK 2015-02-24 19:36 ` Jim Reisert AD1C 2015-02-24 21:39 ` Jon TURNEY 2015-02-24 21:50 ` Jon TURNEY 2015-02-25 1:36 ` GEORGE BARRICK 2015-02-25 17:23 ` GEORGE BARRICK [not found] ` <54F2077C.9080802@dronecode.org.uk> 2015-03-01 14:06 ` GEORGE BARRICK 2015-02-25 13:26 ` Jim Reisert AD1C 2015-02-25 14:30 ` Jim Reisert AD1C 2015-02-25 17:22 ` Jon TURNEY 2015-02-24 21:44 ` Jon TURNEY [this message]
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=54ECEFA2.7050207@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=gbarrick@kent.edu \ /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).