You are not logged in.
I got "screen tearing" on Firefox (probably on some other applications as
well) after my recent, daily system upgrade (pacman -Syu).
I highly suspect this happened because of
"upgraded intel-tbb (2020.1-1 -> 2020.2-1)".
I cannot reinstall the old (good) 'intel-tbb'
I tried the following operations (in various orders)
[~]$ pacman -R intel-tbb
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing intel-tbb breaks dependency 'intel-tbb' required by suitesparse
[~]$ pacman -S intel-tbb-2020.1-1
error: target not found: intel-tbb-2020.1-1
[~]$ pacman -S intel-tbb-2020.1
error: target not found: intel-tbb-2020.1
REFERENCES
5.5.13-arch2-1 x86_64 GNU/Linux
Mozilla Firefox 74.0
intel-tbb 2020.2-1
libva-intel-driver 2.4.0-1
xf86-video-intel 1:2.99.917+899+gf66d3954-1
...
xorg-server 1.20.8-1
fluxbox 1.3.7-5
Last edited by Alexarch (2020-04-03 02:28:14)
Offline
I observe the same problems basically with everything related to KDE Plasma.
And indeed, going back to intel-tbb 2020.1.1 seems to improve the situation. You may build it yourself after checking out the PKGBUILD:
asp checkout intel-tbb
cd intel-tbb
git checkout 860e921a4d1f6c227e772216f7ca4892cbd15205 # go back to 2020.1
cd trunk
# edit PKGBUILD:
# - change the sha256 sum to 7c96a150ed22bc3c6628bc3fef9ed475c00887b26d37bca61518d76a56510971
# - change "cd tbb-$pkgver" to "cd oneTBB-$pkgver" (twice)
makepkgOffline
Offline
I observe the same problems basically with everything related to KDE Plasma.
And indeed, going back to intel-tbb 2020.1.1 seems to improve the situation. You may build it yourself after checking out the PKGBUILD:
Why build it yourself? Just reinstall from the pacman cache or use the archive.
Offline
Why build it yourself? Just reinstall from the pacman cache or use the archive.
Good to know, never had to roll back before, so I didn't know about the archive.
Concerning the actual issue: A better workaround is described in the bug report (going back to mesa-19.3.4). intel-tbb most likely is not the problem. My observation was rather a coincidence: While testing, a video was playing on another seat, during which the tearing went away.
Offline
All replies were spot-on.
I had blamed the innocent (intel-tbb) all along!
The real culprit seems to be
"upgraded mesa (19.3.4-2 -> 20.0.2-1)"
at the recent, fateful system upgrade.
I've chosen the easier solution
by adding "MESA_LOADER_DRIVER_OVERRIDE=i965" to '/etc/environment'
(while sticking with mesa-20.0.2-1).
A-OK.
Many thanks to jasonwryan.
PS Slithery, I'd appreciate if you could provide a few more details to
"Just reinstall from the pacman cache or use the archive".
Thanks. I might use the pointers if needing an older version some day.
Offline
INFORMATIONAL
Today (04/02/2020), on the daily system upgrade 'mesa' has been upgraded too:
upgraded mesa (20.0.2-1 -> 20.0.3-1).
_Without_ jasonwryan's suggested fix ("MESA_LOADER_DRIVER_OVERRIDE=i965") I get
the same screen-tear mess (i.e., problem still persists in 20.0.3-1).
Jason, again many thanks.
Please somebody show me how I can prepend "[SOLVED]" to the title of this topic and
maybe change "(intel-tbb?)" to "(mesa?)".
Last edited by Alexarch (2020-04-02 16:49:05)
Offline
You can adjust the title by editing your first post.
Offline
INFORMATIONAL
The problem is fixed as of mesa upgrade to 20.0.6-2 - i.e., (20.0.5-3 -> 20.0.6-2).
You no longer need "MESA_LOADER_DRIVER_OVERRIDE=i965" in '/etc/environment'
to eliminate the tear.
Offline