View Single Post
Old Yesterday, 02:51 PM   #45
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,724
Karma: 205159604
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by KevinH View Post
Manjaro stable has not moved to Qt 6.9.2, yet so I built a Qt 6.9.2 version for testing on my older Mac machine and I can confirm the Qt 6.9.2 also fixes the issue with using svg filter urls within style attributes.

So both Qt 6.9.1 and Qt 6.9.2 have a QtWebEngine new enough to handle that.

*After* our upcoming release (hopefully in a week or two), we will move to test Qt 6.9.2 for the release after that (assuming it will get that Linux QtWebEngine fix to work with the latest mesa library). Otherwise we will wait for Qt 6.9.3 in the hopes that the fix is in place.
So far as I can, 6.9.2 contains a commit that can actually break gpu rendering with the latest mesa (and possibly an amd/wayland connection). Arch has "fixed" this by releasing qt6-webengine 6.9.2-2 that reverts the commit.

https://gitlab.archlinux.org/archlin...a4ae91324a1f0a

So I don't think the fix you were waiting on (that was accidentally left out of 6.9.1) made it into 6.9.2 either. Not according to the last comment by Jan Palus here: https://bugreports.qt.io/browse/QTBUG-139424

Last edited by DiapDealer; Yesterday at 02:57 PM.
DiapDealer is online now   Reply With Quote