The patch got accepted upstream for gnome-shell 3.30. And hopefully for
some 3.28.3 version.
For Fedora users who end up here because it's the top entry on a common
search engine, the corresponding bug entry is here:
https://bugzilla.redhat.com/show_bug.cgi?id=1489554
** Bug watch added: Red Hat
The dependency of this bug could probably changed from ogl-linux-beta to
bug 1491303, as webrender will replace all the old rendering
architecture and is already enabled on linux + intel in nightly.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Although this bug is only about decoding support, I'd like to leave a note
about the rendering: AFAIK rendering without any slow copies requires DMABUF
support, so processes can share resources on the GPU.
For the Wayland backend this about to land, see bug 1552590, quote:
> Wayland dmabuf
Although this bug is only about decoding support, I'd like to leave a note
about the rendering: AFAIK rendering without any slow copies requires DMABUF
support, so processes can share resources on the GPU.
For the Wayland backend this about to land, see bug 1552590, quote:
> Wayland dmabuf
That should be bug 1572697 for Wayland.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1688592
Title:
Missing VA-API hardware decoding support drains battery
Status in Mozilla
That should be bug 1572697 for Wayland.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web browsers lacking hardware-accelerated video decoding
Status in Chromium
Ouch, sorry and thanks for that!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1893021
Title:
Flash plugin symbol lookup error with firefox 80.0+build2 on xenial
It's likely that you see bug 1658035 - should be fixed by next nightly.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1889784
Title:
Hardware-accelerated video decoding (VA-API)
(In reply to eric.riese from comment #34)
>
> In my opinion the bounty was already earned when this issue was resolved but
> I don't know who gets to be the arbiter.
That would certainly be Martin Stránský :)
Martin, do you want to claim the bounty? If you don't care about it / don't
need it
(In reply to eric.riese from comment #34)
>
> In my opinion the bounty was already earned when this issue was resolved but
> I don't know who gets to be the arbiter.
That would certainly be Martin Stránský :)
Martin, do you want to claim the bounty? If you don't care about it / don't
need it
Public bug reported:
The Firefox testing infrastructure is based on Ubuntu 18.04. In order to
enable the Wayland backend by default, we need to also run test on that.
There is one particular bug in Mutter 3.28 that I'd like to see fixed
for that, thus requesting a backport of a patch. It's
Just got crash reports at Firefox about this - apparently
visiting/closing any website with WebGL is enough to trigger this on
affected drivers.
https://crash-
stats.mozilla.org/report/index/318626ed-3353-4bf4-8df2-75ccb0210403
--
You received this bug notification because you are a member of
Jan, this might be important for you as well (archlinux).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1917191
Title:
firefox will not start after it crashed unexpectedly
Status
(In reply to Emilio Cobos Álvarez (:emilio) from comment #30)
> So given there's no way to access the other border corners, and that this
> works for our purposes, I think we should probably just roll with it,
> thoughts?
I'd agree - should work well for almost everyone.
One question I had to
Thanks emilio, that's a good hint. The comment says
> It may cause performance issues so let's put it under a preference and enable
> it for desktop environment which do that by default.
This is clearly outdated and from a pre Webrender time.
--
You received this bug notification because you
This just became even more prominent in 95 with colorways. We need a way
to support this with alpha visuals as XShape is neither available on
Wayland nor on X11 with HW Webrender - i.e. it's only available in
legacy fallback paths. As the default theme supports this (even though
with a grey
This should have been fixed a while ago and it works for me -
jhwilliams, can you still reproduce this issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1930485
Title:
Can't
IIUC there are now several runners using Ubuntu 22.04, notably for bug
1813588, so I guess this can be closed and most dependent bugs can
depend on that bug instead?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Closing as unresponsive (and likely fixed).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1930485
Title:
Can't Start Firefox 88 on Weston/Wayland, Ubuntu 18.0.4.
Status in Mozilla
Another interesting point would be if setting `gfx.x11-egl.force-
disabled` (in `about:config`) to `true` helps with the issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1987976
Also, I suppose `gfx.webrender.software:true` works around the issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1987976
Title:
firefox black window
Status in Mozilla Firefox:
(In reply to Alan Jenkins from comment #35)
> Weird!
Indeed :( But thanks for testing!
> I can run glxgears, xeyes, and xvidtune ok :-). (Didn't bother trying
those immediately after login).
I think these are all apps with server side decorations (SSD). Could you
try `GDK_BACKEND=x11 cheese` or
Oh, that's really interesting...so does launching with
`MOZ_GTK_TITLEBAR_DECORATION=system` also solve the issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1987976
Title:
Hm, this pretty much sounds like Gnome-Shell bug around Xwayland-on-
demand to me - so maybe a better place for that would be
https://gitlab.gnome.org/GNOME/mutter/-/issues (or a Ubuntu bug, in case
they ship some custom patches).
--
You received this bug notification because you are a member of
So the fact that even software rendering (`gfx.webrender.software:true`)
is broken strongly suggest that something with the affected setup is
deeply broken - disabling hardware acceleration is usually our last
resort for such issues.
Alan, have you tested a few other Xwayland apps and do they all
Since this was reported for a device running the Crocus Mesa driver in
situations where implicit drm modifiers are most likely used (Xwayland,
X11 compositor), there's certain chance that it will be fixed by
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21209
Michelet/Alan, any chance
Oh wow, I think I just managed to reproduce this on my Iris laptop - in
a fresh session with Xwayland on demand. That and comment 45 points to a
race condition in the FF code regarding switching between composited and
non-composited X11.
--
You received this bug notification because you are a
27 matches
Mail list logo
