From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 56473 invoked by alias); 25 Feb 2015 14:30:58 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Received: (qmail 56465 invoked by uid 89); 25 Feb 2015 14:30:58 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-HELO: mail-lb0-f182.google.com Received: from mail-lb0-f182.google.com (HELO mail-lb0-f182.google.com) (209.85.217.182) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Wed, 25 Feb 2015 14:30:56 +0000 Received: by lbvn10 with SMTP id n10so4196716lbv.6 for ; Wed, 25 Feb 2015 06:30:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=VRD9ZZjjGWnwietNphYz3Jpvp976luU0jcryBNhHc5Y=; b=hgMIrXW1VbMNUGrG5allC9y27CyXpSL7SuEatr4qAlS7XZT0mbEGbXa07P8zCaj/9S w6XR1bK7jvl+Cs6Whpru2O+3o7/F2hKX6QsoVrFrJG1KjtzBfFr5Zi+mAA9asLSyeBX3 WaIdgTb9+DjHFmqHAWYwomlCkUXfopHGIceSCXpfe4HOXLLA/NomJpWwVyo0GsjGwhEJ 9cJwS616s5bTrzlyfTubAEIfXPbOBUIOY9Xk0TMdeqOCk7+067Kec74Jk/9SoRb2rXcZ 8pM936yCAjm5kBhctEcwK/+4cXRasWYe0bcE5NSjBwE280r6dobM45clBrkNWvkT8vuM A+xg== X-Gm-Message-State: ALoCoQlsxAKf6BJbv0QHMGW1MEVeumbvBRLzetnqYDUF0eQUbLKqKaN3SglUp8z3DYA0R+Va+ixj MIME-Version: 1.0 X-Received: by 10.152.120.225 with SMTP id lf1mr3113026lab.20.1424874653027; Wed, 25 Feb 2015 06:30:53 -0800 (PST) Received: by 10.112.242.1 with HTTP; Wed, 25 Feb 2015 06:30:52 -0800 (PST) In-Reply-To: References: <54ECD29B.7050001@dronecode.org.uk> <54ECEFDC.5080107@dronecode.org.uk> Date: Wed, 25 Feb 2015 17:23:00 -0000 Message-ID: Subject: Re: Dfficulty with xorg-server-1.17.1-2. From: GEORGE BARRICK To: cygwin-xfree@cygwin.com Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2015-02/txt/msg00091.txt.bz2 2015.02.25.09:27:05 Hey Jon and cygwin staff, As you surmised, the difficulty was with xlaunch starting the new xwin-1.17.2-1. The xlaunch-20150224-1 that you posted yesterday works like a charm. I have one small note for other folks who might like to run their system in a way similar to mine. I like to have xlaunch automatically start a single colored xterm for me (in multi-window mode). After that I just open more from the command line as it suits me. If I use the command line embedded in the installed xlaunch.lnk file: C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/xlaunch.exe it always prompts me through the tiresome "configure & start" GUI at the beginning. Adding the phrase -run ~/config/config.xlaunch at the end of that command line always gets ignored in favor of the "configure & start" GUI. However, when I strip the invocation of the bash from that command: C:\cygwin\bin\run.exe /usr/bin/xlaunch.exe -run ~/config/config.xlaunch the xlaunch goes right ahead to run the single xterm that's described in my ~/config/config.xlaunch file. This is a petty subtlety, but I know there are a lot of desktop tweakers out there who might find it a little bit helpful. George gee_barrick_kent_dot_edu P.S. Thanks_x_10^{12} to cygwin for your great system and service to the FOSS community. On 2/24/15, GEORGE BARRICK wrote: > 2015.02.24.18:06:36 EST > > Hey Jon, > > Thanks for your attention to all that detail. > I will test the updated xlaunch-20150224-1 when > it hits some of the mirrors tomorrow morning. > > George gee_barrick_at_kent_dot_edu > > > On 2/24/15, Jon TURNEY wrote: >> On 24/02/2015 19:35, Jon TURNEY wrote: >>> On 24/02/2015 19:05, Jim Reisert AD1C wrote: >>>> On Tue, Feb 24, 2015 at 11:03 AM, GEORGE BARRICK wrote: >>>> >>>>> The other notable problem to report is that my X-server now >>>>> crashes after about 5-10 minutes of use. Since this issue does >>>>> not get reported in xwin.0.log or xwin.0.log.old, I do not yet >>>>> know how to provide more information. >>>> >>>> I have seen this also. It only happens on my PC at home, if I leave it >>>> alone for hours on end. It's not nearly as frequent as 5-10 minutes. >>>> I need to check the log files again, but I don't remember seeing >>>> anything there the first time I looked. >>> >>> With regard to the crash problems, can you please try the instructions >>> at [1] to generate a backtrace. >>> >>> [1] http://x.cygwin.com/devel/backtrace.html >> >> Possibly this was xlaunch deciding that the X server hasn't started >> successfully after ~12 minutes or so, and killing it. >> >> So don't bother, unless you have crash problems after upgrading to >> xlaunch-20150224-1, or when not using xlaunch. >> >> -- >> 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/