From owner-freebsd-java@FreeBSD.ORG Fri Jan 24 19:53:19 2014 Return-Path: Delivered-To: freebsd-java@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A24FA5E; Fri, 24 Jan 2014 19:53:19 +0000 (UTC) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D4C6012E3; Fri, 24 Jan 2014 19:53:18 +0000 (UTC) Received: from mouf.net (swills@mouf [199.48.129.64]) by mouf.net (8.14.5/8.14.5) with ESMTP id s0OJr9gC018237 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 24 Jan 2014 19:53:14 GMT (envelope-from swills@mouf.net) Received: (from swills@localhost) by mouf.net (8.14.5/8.14.5/Submit) id s0OJr9Vf018236; Fri, 24 Jan 2014 19:53:09 GMT (envelope-from swills) Date: Fri, 24 Jan 2014 19:53:09 +0000 From: Steve Wills To: bug-followup@FreeBSD.org, c.kworr@gmail.com, freebsd-java@FreeBSD.org Subject: Re: ports/173603: java/icedtea-web starts javaws incorrectly Message-ID: <20140124195306.GA13031@mouf.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Fri, 24 Jan 2014 19:53:14 +0000 (UTC) X-Spam-Status: No, score=0.0 required=4.5 tests=FAKE_REPLY_C autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mouf.net X-Virus-Scanned: clamav-milter 0.97.8 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jan 2014 19:53:19 -0000 Hi, This bug still seems to exist and the fix seems pretty simple. I just ran into it and the attached patch fixes it. Anyone have objections to committing this? Thanks, Steve