Hi, I'm pretty up to date on Unstable, and believe I have the latest qt library stuff. Interestingly both Konqueror and Opera exhibit the same problem. Even more interestingly Opera exhibits the problem with both the statically linked and dynamically linked qt versions. This makes it real confusing to me.
Both browsers will run fine for a while. At some point they get into a mode where scrolling exposes black regions rather than the newly-exposed rendered content. I've found no way to get out of that mode, other than rebooting the sick browser. Selecting with the mouse and auto-scrolling will force the black-out regions to render. But that's more of an interesting fact than a useful solution. It's easier to use a different browser. Google web and group searches found a few other people experiencing this. The only fix mentioned was to change QT versions. I don't believe that the statically-linked Opera uses the same QT version as Debian Unstable. Also I would expect other Debian Unstable users to be experiencing this. Are they? I'd like to make Opera usable, since I actually paid for it. I reported a defect to Opera, but they don't seem responsive. TIA for any hints. Cheers, Steve -- \_O< \_O< \_O< ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Steve Cooper Redmond, WA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]