34748 - Serious display problem

Status: RESOLVED WORKSFORME

(Core :: Layout, defect, P3)

Description

[tylerv]

On Linux (but not Windows) www.espn.com is unreadable.  Moving my cursor around
the Mozilla window makes some items visible.  I am attaching a screenshot of the
problem.

I am running RH 6.1 stock under KDE using an ATI Mach 64 video chipset.
Please let me know if you need additional information.  I did not see any other
bugs similar to this problem.

[tylerv@braddock package]$ ldd mozilla-bin
        libraptorgfx.so => ./libraptorgfx.so (0x40013000)
        libmozjs.so => ./libmozjs.so (0x4003a000)
        libxpcom.so => ./libxpcom.so (0x40097000)
        libjsj.so => ./libjsj.so (0x40121000)
        libplds4.so => ./libplds4.so (0x40138000)
        libplc4.so => ./libplc4.so (0x4013b000)
        libnspr4.so => ./libnspr4.so (0x40140000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x40170000)
        libraptorwebwidget.so => ./libraptorwebwidget.so (0x40181000)
        libdocshell.so => ./libdocshell.so (0x4019d000)
        libjsdom.so => ./libjsdom.so (0x401b0000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x40270000)
        libutil.so.1 => /lib/libutil.so.1 (0x40286000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x40289000)
        libdl.so.2 => /lib/libdl.so.2 (0x40298000)
        libstdc++-libc6.1-1.so.2 => /usr/lib/libstdc++-libc6.1-1.so.2 (0x4029b000)
        libm.so.6 => /lib/libm.so.6 (0x402dd000)
        libc.so.6 => /lib/libc.so.6 (0x402fa000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

Comment 1

[tylerv]

Attachment: Screenshot of www.espn.com on my system

Comment 2

[troy]

Linux specific problem

Comment 3

[tylerv]

M 15 update: This problem disappears if I select the "Use ViewManager2" option
in the Debug section of the preferences screen.  However if this option is
unchecked, the problem remains.

Comment 4

[Gervase Markham [:gerv]]

[e-mail] - are you still seeing this problem with recent builds of 
Mozilla?

Gerv

Comment 5

[tylerv]

In the later builds this problem is fixed, with UseViewManager2 option checked 
and unchecked.