Created attachment 73893 [details] corruption shown I have noticed a lot of corruption using qt applications in gnome with last few versions of intel and even more using the Opera browser. I posted a screenshot of Minitube (qt app) showing some corruption.
Created attachment 73894 [details] corruption shown in picture Picture attached as plain text accidentally.
Can you please attach your Xorg.0.log?
Sorry for the sloppiness. Here are some more details. Archlinux x64 first gen intel i5, gateway nv79c xf86-video-intel 2.20.19 mesa 9.0.2 xorg-server 1.13.2 qt 4.8. linux 3.7.5 20-intel.conf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "sna" Option "Backlight" "intel_backlight" Option "TearFree" "true" EndSection
Created attachment 73895 [details] xorg.0.log
Can you please test without TearFree? Just in case that is affecting the damage tracking.
Out of curiosity, which backlight does SNA detect by default for you?
Doesn't immediately reproduce here, perhaps a few details on the qt version and themes?
This is what I get without intel_backlight specified: found backlight control interface acer-wmi (type 'platform') UXA detects intel_backlight correctly. To get either sna or uxa to work with the backlight I have to use acpi_backlight=vendor regardless and even more strangely is that adding i915 to mkinitcpio (initramfs creation) causes the backlight not to work. To reproduce the corruption in minitube, use gnome and play a video. I don't get corruption if I don't play a video. To reproduce the corruption in opera, use gnome and open the preferences (ctrl-f12) window in opera and click the tabs in the windows.
Still get same corruption with tearfree disabled.
(In reply to comment #8) > This is what I get without intel_backlight specified: > found backlight control interface acer-wmi (type 'platform') > > UXA detects intel_backlight correctly. I think you mean "incorrectly". :-p Your system is specified to use the acer-wmi *platform* backlight interface. The intel_backlight is one of last resort that is often not hooked up to anything at all. So you need to file a bug with the acer-wmi acpi guys for the broken backlight controller. Let's see what happens in the opera's preference window...
Hmm, do you have an example handy of the opera corruption? Haven't seen anything amiss, the suggestion from an earlier bug I fixed with Opera suggests that I check for missing migrations... Anyway seeing the style of corruption should help me pinpoint the likely cause.
Created attachment 73960 [details] corruption in opera The same colourful corruption on minitube shows up on the cancel button in the opera preferences' window but that corruption disappears with gnome-screenshot.
The error does look like corruption inside the temporary buffers used for trapezoids. Can you please build from xf86-video-intel.git and ./configure with --enable-debug?
Yeah, I built xf86-video-intel with debug from git but was unable to start x (probably my error in building). Anyway, I instead built 2.21.0 with debug.
Ok... Is the error still reproducible? Have you tried different compiler flags (thinking back to earlier similar bugs)?
No longer reproducible in 2.21.2. What did you do to fix it?
Nothing explicitly targeting this bug, but plenty of candidates for accidental fixes. If it stays fixed in the next release, I'm just going to pretend it never happens and hope it never repeats.
I've tagged new release. Can you double check that the bug hasn't resurfaced?
It is still reproducible in qt apps and opera. It's hard to get a screenshot but the corruption for example is minitube slider is milder and doesn't flicker when watching videos and the corruption in the opera preferences window is limited to very small grey boxes in the tabs of the preferences window. I am using 2.21.3. The situation is definitely improved.
Your description still reminds me of earlier compiler artifacts.
Might as well check with 2.21.4 in case this turns out to be a read-read bug instead.
Still reproducible. What do you mean by read-read bug?
read-read: bug 61628
It still appears that you are the only person encountering this issue. Can you try enabling a few debug options and changing compiler options to identify the cause?
Been a while, hopefully things are better. Or at least not worse.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.