![]() Version prior this bug is closed as described in the policy above.Īlthough we aim to fix as many bugs as possible during every release's Of Fedora, you are encouraged change the 'version' to a later Fedora To see this bug fixed and are able to reproduce it against a later version Thank you for reporting this issue and we are sorry that we were notĪble to fix it before Fedora 31 is end of life. Plan to fix it in a currently maintained version, simply change the 'version' Package Maintainer: If you wish for this bug to remain open because you At that time this bug will be closed as EOL if it remains open with a It is Fedora's policy to close all bug reports from releases that are no longer ![]() ![]() This message is a reminder that Fedora 31 is nearing its end of life.įedora will stop maintaining and issuing updates for Fedora 31 on. Hardware: i7-4720HQ, running Firfox on my GTX 960m via Primusrun is also pretty slow) another note is that Firefox on Wayland was pretty smooth at the early stages for me, back when enabling acceleration would cause it to crash, so not sure if a regression) (also probably not related but Wayland is generally pretty slow for me, and keeps getting slower each version, in contrast with people people noticing huge improvements, so not sure if this is something about my particular hardware. I have Webrender enabled here, but turning it off doesn't make the situation any better. Also on websites such as Pinterest you can noticeably see that images are rendered as white when scrolling at speed. This has gotten a lot more visible (somewhat unusable) with the new kinetic scrolling. The lags/stutters are pretty noticeable when scrolling or when there are CSS animations. (this stands for the Nightly version too, in addition to the package provided by fedora) *This bug is created upon a request on Fedora Mag.įirefox seems much slower on Wayland than X whether ran natively or through Xwayland.
0 Comments
Leave a Reply. |