Summary: | Display corruption when scrolling applications (coincides with underlying Plasma widgets) | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | alan.michael.bowman |
Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | alan.michael.bowman, aseigo |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Screenshot of fragmented display
Screenshot showing location of plasma widgets |
Description
alan.michael.bowman
2011-02-01 22:28:00 UTC
i've seen the same thing with firefox, but not with plasma widgets but video played by vlc or mplayer. it seems to be an issue with firefox repainting, and it isn't something we control. before i close it as "not our bug", can you provide screenshots of the problem? I don't think that this is necessarily a Firefox issue - I have noticed it with other applications. It seems more noticeable on browsers, because I scroll the contents, causing the entire window to update. I noticed a couple of other related(?) things after filing this bug: - when the problem occurs, using alt+tab to trigger the window switch (Carousel-style, not sure of the name of the effect) I can see that the miniature version of the window has fixed itself. - sometimes when I type into Konsole, it looks like it has ignored the letter I've just pressed. Typing another letter, or using alt+tab causes the missing character to appear as the window contents are updated. These all seem to be related to windows not updating themselves as I'd expect, and all seem to have occurred (and gotten worse) at the same time. I will try to provide screenshots when I get back to the afflicted laptop. Created attachment 56797 [details]
Screenshot of fragmented display
Created attachment 56798 [details]
Screenshot showing location of plasma widgets
Screenshots attached - I tried to capture the same issue when I noticed it with KSystemLog, but it seems less frequent (or less obvious). It did occur, though! It appears when comparing the two screenshots that I was wrong earlier - it looks like the area over the widgets is the only bit that *has* updated correctly. Bringing the plasma desktop to the fore caused the screen to update, and shows it how it should be. does it also happen if desktop effects are turned off? I spent several minutes scrolling pages with desktop effects disabled without error. I re-enabled effects and the error promptly re-appeared. ok, so it's either a kwin bug or a driver bug being triggered by the effect. i'll let the kwinsters decide :) thanks for the prompt and useful follow ups to your report. always nice when the reporter is responsive like that! possibly bug #264259, the last comments there hint a workaround and a(n experimental) solution - if you compile yourself it would be helpful if you could test this. Looking at the symptoms from bug #264259, I could believe that they're the same thing. I'm not sure why I'm getting interaction with the underlying plasma widgets, though. It all got a bit beyond my understanding... :-) I'm not really in a position to compile things at the moment, so I may have to leave that line of investigation to others for a while. I'm happy to see if there's anything else I can do, particularly to confirm/disprove that these are the same issue if you've any suggestions. damage region update interference. you actually don't have to compile things, setting that environment variable could give a good hint (in doubt call "LIBGL_ALWAYS_INDIRECT=1 kwin --replace &" in konsole) I tried the command you suggested. Having given it the 10-minute test, I have not seen a single instance of screen corruption in that time. I've tried scrolling several applications, and not had a problem at all. i'll mark it as dupe then (similar symptoms, same workaround, you're both on ubuntu and have similar GPUs/drivers) in case your issue does /not/ get fixed with the other (if it's not upstream only anyway), feel free to reopen this one. *** This bug has been marked as a duplicate of bug 264259 *** |