From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20332 invoked by alias); 8 Jan 2004 18:27:03 -0000 Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com Reply-To: cygwin-xfree@cygwin.com Received: (qmail 20316 invoked from network); 8 Jan 2004 18:27:02 -0000 Received: from unknown (HELO central.ixn.com) (65.19.132.2) by sources.redhat.com with SMTP; 8 Jan 2004 18:27:02 -0000 Received: from msu.edu (office.ixn.com [68.23.74.57]) (authenticated bits=0) by central.ixn.com (8.12.10/8.12.10) with ESMTP id i08IQvEZ054196 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 8 Jan 2004 13:26:58 -0500 (EST) Message-ID: <3FFDA0E6.5080001@msu.edu> Date: Thu, 08 Jan 2004 18:27:00 -0000 From: Harold L Hunt II User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com Subject: Re: XFree86-xserv-4.3.0-33 release pending References: <20040108152236.7B6E.MURAKAMI@ipl.t.u-tokyo.ac.jp> <20040108192802.0CD8.MURAKAMI@ipl.t.u-tokyo.ac.jp> <3FFD729C.6050202@msu.edu> <3FFD9EB5.1060807@gmx.de> In-Reply-To: <3FFD9EB5.1060807@gmx.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.5 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) X-SW-Source: 2004-01/txt/msg00163.txt.bz2 List-Id: Holger, Holger Krull wrote: > Hello, > i installed the -33 Version and the -clipboard feature doesn't work. > I started with xwin +kb -xkbmap de -query murpel -from 192.168.1.2 -fp > tcp/192.168.1.1:7100 -dpi 100 -once -clipboard > > What's different here? Xwinclip still works but needs -ac. Thanks, the log file was very useful. What is happening is that we have to wait to start the clipboard client until XDM has finished killing any connected clients. There is not a well-defined event that I can use to track this, so I have to try to find an artifact of the startup process that works with most XDM/KDM/GDM implementations. The current triggers I am using work fine with my KDM implementation, but they appear not to work with your XDM implementation. So, I will have to tweak the triggers a bit to see if I can make them more robust. Thanks for the report. Patiently wait for 4.3.0-34. Thanks, Harold