Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Colonel Panic]

Hi. I've been using both Swiftfox and Seamonkey 2.0 in Vector Light 6.0, and I've noticed that on certain sites in particular the screen refresh doesn't work properly; the window gets overlaid with strips of text to the point where it becomes unreadable and has to be closed. (Reload Tab works sometimes, but not always). Has anyone else had this problem?

[Daniel]

I think I had that problem with swiftfox once and maybe seamonkey. It could be that the site is optimized for IE. (maybe) You could try changing the browser identification. (I know there is a firefox addon to do this but I don't know about for seamonkey.)

[roarde]

I'm having a similar problem with firefox. It's not always text: it's bits of the screen that exist elsewhere.

Don't know if our problems are related, but I'm starting to wonder about background settings.

[Colonel Panic]

Thanks for the replies, I'll try that next time I'm in Vector. Where do you change the settings to make the browser resemble Internet Explorer?

[GrannyGeek]

This has been experienced by several users, including me. The problem seems to be that we're using the xorg driver for NVIDIA or ATI graphics. If people switch to the proprietary drivers, the problem goes away. However, the proprietary drivers don't work with some NVIDIA and ATI graphics cards/chips, so if this junk rendering is really bothersome, we'd have to change to the xorg vesa driver.

The problem does not happen with Opera. If your problem is the same as mine, it has nothing to do with being optimized for IE. It's a problem with the xorg driver for NVIDIA and ATI.

SeaMonkey now uses the same base as Firefox, so both of them display the problem.
--GrannyGeek

[Colonel Panic]

@GrannyGeek;you may be right, but my graphics card is an onboard 4MB one rather than a separate one and as far as I know isn't either NVIDIA or ATI in design. I still might compare my xorg.conf file against the one I use in Puppy (which doesn't have the same problem) to see what the difference is.

[GrannyGeek]

Many onboard graphics chips are ATI or NVIDIA. Of course, yours may be something else.

Let us know what you find when comparing xorg.conf.
--GrannyGeek

[roarde]

The problem GrannyGeek mentions is the same one I was having, but with the Openchrome driver on a chrome9. Still not sure this is your problem. Can you post a screenshot?

That I had the same problem suggests that it's not just nvidia/ati, but a little more generalized, maybe some common code?

The solutions suggested for my problem were either use the vesa driver or (I did this one and it works):
http://forum.vectorlinux.com/index.php?topic=11396.0