From owner-freebsd-ports@FreeBSD.ORG Tue Feb 19 20:04:35 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CEF16578; Tue, 19 Feb 2013 20:04:35 +0000 (UTC) (envelope-from freebsd-ports-local@be-well.ilk.org) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id A2C46327; Tue, 19 Feb 2013 20:04:35 +0000 (UTC) Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.41]) by be-well.ilk.org (Postfix) with ESMTP id 7C67233C1E; Tue, 19 Feb 2013 15:04:29 -0500 (EST) Received: by lowell-desk.lan (Postfix, from userid 1147) id 2467239829; Tue, 19 Feb 2013 15:04:27 -0500 (EST) From: Lowell Gilbert To: "A.J. 'Fonz' van Werven" Subject: Re: [games/xboing] Xlib error References: <20130219171832.GA75327@spectrum.skysmurf.nl> Date: Tue, 19 Feb 2013 15:04:27 -0500 In-Reply-To: <20130219171832.GA75327@spectrum.skysmurf.nl> (A. J. van Werven's message of "Tue, 19 Feb 2013 18:18:32 +0100") Message-ID: <44hal8m5o4.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: dinoex@FreeBSD.org, freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2013 20:04:35 -0000 "A.J. 'Fonz' van Werven" writes: > The games/xboing port builds fine, but when I try to run it I get the > following (and then it just exits): > > (159)fonz@ace% xboing > XBoing - Please wait (insert gecos name), initialising xboing ... > XBoing - Error: Xlib Error: BadMatch (invalid parameter attributes) > > Please read `/usr/local/lib/X11/xboing/problems.doc' document for help. > > Unfortunately the mentioned problems.doc file does not appear to contain > any clues for this particular issue. I seem to remember having had this > problem for quite a long time, perhaps since FreeBSD switched from XFree86 > to X.org, but that is admittedly just an educated guess. > > When I asked about this on the FreeBSD forums I got exactly zero replies, > so I figured I'd ask here before bugging the port maintainer directly. I'd say it's exactly the sort of thing to include the maintainer on, even if you're trying to not be pushy. I tried to take a look at this myself, but quickly hit a point where I wanted to have a dtrace-enabled system, which I don't at the current time. It's possible to debug more directly, but I'm not volunteering immediately...