Abrowser Trisquel 8 not rendering well
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
Just updated to Trisquel 8 and all packages with it, including Abrowser.
When scrolling down on any webpage, crappy ones like Facebook, or just a DuckDuckGo search results page, as you scroll down rendering the page cleanly fails. If you stop, and then scroll slowly up, the rendering clears up.
Any ideas? ? ?
| Pièce jointe | Taille |
|---|---|
| linux_abrowser_not_painting_right_when_scrolling_down.png | 378.91 Ko |
I don't have this problem.
> When scrolling down on any webpage, crappy ones like Facebook, or just a
> DuckDuckGo search results page, as you scroll down rendering the page
> cleanly fails. If you stop, and then scroll slowly up, the rendering clears
> up.
Sounds like this bug.
https://trisquel.info/en/issues/23853
I'm not sure what the cause is or why it only affects some users. The
problem doesn't happen for me with regular Firefox, only Abrowser. I
don't see any difference between the default settings for these browsers
that could be causing the problem.
My latest thought was that since Firefox comes bundled with its
dependencies, the problem might not be with Abrowser itself but with one
of its dependencies as packaged in Trisquel. That might explain why you
did not have this problem with Trisquel 7, since I'm pretty sure that
Trisquel 7 and 8 have the same version of Abrowser. Can you confirm that
I understand correctly that you did not have this problem with Abrowser
until you upgraded to Trisquel 8?
Its true, I did not have this problem with Trisquel 7, at all. Only after upgrade.
Anyone figure out this issue . . . seems like a significant one with Abrowser upgrade that others are having, even if its small group of us having it.
I'm running Trisquel on my Lenovo laptop 3000 c200 from 2007.
It's unusable on most websites with lots of scrolling now.
The computer on which I have this issue currently does not work, so
until the part I need to fix it arrives I can't test any further. Here,
however, are some ideas that come to mind. Maybe someone else can look
into them for now.
- Does the same issue happen with Ubuntu's Firefox? If not, then that
narrows down the possible causes of the problem to things that are
different between Ubuntu and Trisquel. Else, the bug is from upstream
and should be reported and fixed there. Someone can check on this by
booting into a live Ubuntu session and running Firefox.
- I have already tried downloading Firefox from Mozilla and running
that. The problem does not occur. Since Mozilla's distribution of
Firefox for GNU/Linux comes with its dependencies bundled rather than
using packages from the Trisquel repo, it's possible that the problem
is not with Abrowser but with one of its dependencies.
- However, I have never had this problem with Icecat, even though it
does use packages from the repo. A difference between Icecat and
Abrowser is that Icecat is based on ESR52. It will be interesting to
see if Icecat starts having this problem when it moves to ESR60. I
have never run into the problem with Tor Browser, which has moved to
ESR60 but like Firefox comes with its dependencies bundled.
- Since this only affects some users, the problem might be related to
hardware. I suggest that anyone who has this problem share hardware
information here[1] to help determine what the machines on which users
this bug have in common.
As far as I know, the issue comes from the Intel driver.See this: https://forum.palemoon.org/viewtopic.php?f=37&t=19941&hilit=counter&start=40#p149123
I have Intel GPU too and I also have problems with both browsers
- Vous devez vous identifier ou créer un compte pour écrire des commentaires