Closed
Bug 148914
Opened 22 years ago
Closed 21 years ago
SVG ouput is horribly corrupt when using nvidia's X11 driver at 24bit depth.
Categories
(Core :: SVG, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: mozillabugs.philipl, Assigned: alex)
References
Details
Attachments
(2 files)
I don't really see why it's possible, but mozilla's svg component combined with nvidia's X11 driver == a horrible mess. See the two attachments for examples. The first example is the good old lion newly opened. The second example is the lion after being repeatedly obscured and revealed by another window. It's very strange that one's choice of X11 driver could have this effect.
Reporter | ||
Comment 1•22 years ago
|
||
Reporter | ||
Comment 2•22 years ago
|
||
Comment 3•22 years ago
|
||
i can't reproduce in latest builds , using a matrox card - note: you have no colors because of the color depth you are using
Reporter | ||
Comment 4•22 years ago
|
||
Fair enough, I dropped back to 16 bit colour and it worked correctly. However, I take it that the horrible output at 24 bit is a bug of some sort?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: SVG ouput is horribly corrupt when using nvidia's X11 driver. → SVG ouput is horribly corrupt when using nvidia's X11 driver at 24bit depth.
Comment 5•21 years ago
|
||
The same problem on NVidia at 24 bpp. Moreover, the problem occurs both with XFree's "nv" driver and NVidia's "nvidia". Mozilla v1.4, Linux 2.4.22.
Comment 6•21 years ago
|
||
This was indeed not a driver specific problem: the same occurs with XFree86 and drivers ati.2 and neomagic, and with the VNC X server. On all test cases, the problem arises with 24 bit depth, and not 16 bit depth (and I am told it is ok with 32 bit depth too). This was true with Mozilla 1.6 from Debian. But the problem has disappeared in the CVS version.
Reporter | ||
Comment 7•21 years ago
|
||
Yes, the problem does indeed not affect the new svg implementation so we can call this fixed now.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•