On Thursday 08 December 2005 10:53 am, Kurt Miller wrote: > On Tuesday 06 December 2005 08:17 pm, Jolan Luff wrote: > > On Fri, Dec 02, 2005 at 09:20:09AM -0500, Kurt Miller wrote: > > > On Friday 02 December 2005 08:39 am, Christian Weisgerber wrote: > > > > Peter Str?mberg <[EMAIL PROTECTED]> wrote: > > > > > We'll have to add --enable-official-branding to > > > > > CONFIGURE_ARGS to get the right brand.dtd file. > > > > > > > > Yes, with that I get "Firefox". > > > > > > Unfortunately, we can't use --enable-official-branding without > > > permission from moz.org. They have started to enforce their > > > trademarks. We can use "Firefox Community Edition" branding in > > > the mean time. See: > > > > > > http://www.mozilla.org/foundation/trademarks/policy.html > > > http://www.mozilla.org/foundation/trademarks/l10n-policy.html > > > > > > Bernd's latest patch includes the branding change and also remove > > > some old freetype patches that are not needed anymore. > > > > It still says "Deer Park prevented this site from opening a popup > > window." Also, I believe patch-xpcom_io_nsNativeCharsetUtils_cpp > > might be unnecessary now.
Missed this the first time. Good catch the patch-xpcom_io_nsNativeCharsetUtils_cpp patch is not needed too. I think Bernd noted one more place to fix Deer Park and might have this one fixed too. > > > Please test Bernd's latest patch so we can get it in. > > > > Works fine on amd64 and i386 here. It doesn't work via remote X11 > > on macppc though. > > Yea, I'm seeing it fail on mappc too (not remote X). I debugged it a > little and found that we are hitting this cairo bug: > > https://bugs.freedesktop.org/show_bug.cgi?id=4505 > > Seems to be related to 8 bpp Depth. Regarding the crashes: they are from a cairo bug and effect all the gtk+2 apps I've tried. I've been able to reproduce it on multiple platforms in multiple apps. All you need to do is have your X server in Depth 8 and ssh -X to another box to run something like gftp to see it. For macpcc I can reproduce it locally (again Depth 8). Funny thing is I can't reproduce it locally on i386, but remote i386 fails too. Since this is a generic problem and not firefox specific I think firefox should not be held up by it. -Kurt
