> From [EMAIL PROTECTED] Fri Jul 18 18:01:50 2008 > From: Matthias Kilian <[EMAIL PROTECTED]> > To: Martynas Venckus <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], ports@openbsd.org > Subject: Re: UPDATE: mozilla-firefox-3.0 > Mail-Followup-To: Martynas Venckus <[EMAIL PROTECTED]>, > [EMAIL PROTECTED], [EMAIL PROTECTED], ports@openbsd.org > References: <[EMAIL PROTECTED]> > Mime-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > User-Agent: Mutt/1.4.2.3i > X-Loop: ports@openbsd.org > Precedence: bulk > Sender: [EMAIL PROTECTED] > > On Wed, Jul 16, 2008 at 09:25:31PM +0300, Martynas Venckus wrote: > > I've updated the diff. > > > > Changes: > > - security update to 3.0.1 > > - fix the ssl psm bug. you can't just cast a char* to an > > int* and access through it > > - fix arm endianness issue (armel abi) > > - strict alignment fixes for sparc64 > > - fix ppc invoke to skip first two vtable entries. might > > fix macppc to work again > > - update to accept standard dictionaries location, so that > > textproc/mozilla-dicts works again > > Sorry for the delay, I'm currently building it on macppc and armish. > > On i386, it seems to have some strange rendering problems. For example, > > http://www.csszengarden.com/?cssfile=/212/212.css&page=0 > http://www.csszengarden.com/?cssfile=/213/213.css&page=0 > > opened in two tabs look like this: > > http://openbsd.dead-parrot.de/tab1.png > http://openbsd.dead-parrot.de/tab2.png > > [be warned that each png is about one MB large] > > Is anyone else seeing similar effects?
Have you tried what i've mentioned in my very first post? - images rendered incorrectly on nvidia cards with 24 bits, due to incompatibilities between nvidia drivers and x; workaround: DefaultDepth 16 (This affects not only nvidia, but most of the cards.) The workaround exists in xserver-7.5, and it should 'just work' when our X hackers merge it. For some people, this work around is known to work, Option "AccelMethod" "EXA" Option "XAANoOffscreenPixmaps" This is not a OpenBSD-specific bug, and upstream X.Org is aware of it. The bug numbers in their bugzilla are: http://bugs.freedesktop.org/show_bug.cgi?id=13795 http://bugs.freedesktop.org/show_bug.cgi?id=15098