From owner-freebsd-questions Mon Dec 11 14:26: 2 2000 From owner-freebsd-questions@FreeBSD.ORG Mon Dec 11 14:25:58 2000 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from giroc.albury.net.au (giroc.albury.NET.AU [203.15.244.13]) by hub.freebsd.org (Postfix) with ESMTP id 6571437B402 for ; Mon, 11 Dec 2000 14:25:57 -0800 (PST) Received: (from nicks@localhost) by giroc.albury.net.au (8.11.1/8.11.1) id eBBMPgH03047; Tue, 12 Dec 2000 09:25:42 +1100 (EST) Date: Tue, 12 Dec 2000 09:25:41 +1100 From: Nick Slager To: arr@oceanwave.com Cc: questions@FreeBSD.ORG Subject: Re: acroread4 Message-ID: <20001212092541.B99071@albury.net.au> References: <14901.2880.319667.763013@sekrit.office.oceanwave.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14901.2880.319667.763013@sekrit.office.oceanwave.com>; from arr@oceanwave.com on Mon, Dec 11, 2000 at 12:13:36PM -0500 X-Homer: Whoohooooooo! Sender: nicks@giroc.albury.net.au Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake arr@oceanwave.com (arr@oceanwave.com): > I'm currently running 4.2-STABLE (and cvsuped ports) as of 12/10/2000. > I've wiped out /compat/linux and done a make install in > /usr/ports/printing/acroread4 so that it installs the linux_base stuff > from scratch. > > When I attempt to run acroread4 /usr/local/Acrobat4/Reader/License.pdf, > acroread starts, the splash screen comes up, and the acrobat window > appears for a fraction of a second and then bombs with the following: > > Exited with error code: 0x400e0009. > > If I start acroread4 without specifying a file to read, it does fine. > Once I try to open an existing file, though, it exits with the above > mentioned error. > > It doesn't appear to be a branding issue (no error about libraries not > being found), and it doesn't say it's an FPE, so what's the issue > here? Are you by any chance running XFree86 4.0.1? I've seen a problem similar to this running XFree86 4 CVS from about 4-6 weeks ago. Haven't looked into it further, though. I'm guessing it's a font issue. Nick -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message