Hi, I just wanted to add that the upstream fixes now also have been
backported to the 1.0 branch in
https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/2145
and should be released in 1.0.9 - that should allow to drop the
downstream patches again, which I guess would be nice in the lon
So the MR fixing the particular glitch I'm seeing on my Thinkpad T400 /
GM45 is https://github.com/intel/intel-vaapi-driver/pull/514 . Including
that would be enough to close this bug - it's pretty small and straight
forward.
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
Ubuntu 24.04 will ship with Gstreamer 1.24, which finally promoted many
"va*" plugins to primary, i.e. enabled them by default and will thus be
used by more apps than in the past.
I tested this on an old Thinkpad T400 / Intel GM45 and ran into a
glitch. Fortunately there's pe
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930485
Title:
Can't Start Firefox 88 on W
(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 t
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 ar
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 corner)
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 Ub
Jan, this might be important for you as well (archlinux).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917191
Title:
firefox will not start after it crashed unexpectedly
To manage notifications a
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 alread
Ouch, sorry and thanks for that!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893021
Title:
Flash plugin symbol lookup error with firefox 80.0+build2 on xenial
(gtk_window_set_titlebar)
To mana
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889784
Title:
Hardware-accelerated video decoding (VA-API) broken in Firefox 79
(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 yo
(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 yo
That should be bug 1572697 for Wayland.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688592
Title:
Missing VA-API hardware decoding support drains battery
To manage notifications about this bug g
That should be bug 1572697 for Wayland.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1424201
Title:
Web browsers lacking hardware-accelerated video decoding
To manage notifications about this bug
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 surfa
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 surfa
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 Ubuntu
Bugs, which is subscribed
Hej Kenneth, thanks for the answer. I agree that this is a sufficient
workaround, but for an LTS version of Ubuntu, I think it would be
worthwhile considering backporting this fix.
People will use Ubuntu 18.04 for many years to come and many will hit
this issue, especially people using it on serve
Here's the link to the upstream fix:
https://github.com/paramiko/paramiko/pull/979/commits/fdc09c9f93fd189a6398d5b350a3c91011d9b4cb
I'd like to kindly request a backport (actually simply applying) it.
It's a fairly trivial and I just tested it on my server (18.04) without issues.
** Also affects:
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
I'd really appreciate a backport of the fix. Some other distributions
shipping with paramiko 2.0 ship it already, for example mageia
(https://advisories.mageia.org/MGAA-2018-0077.html)
It affects everyone doing backups with duplicity over ssh, most notably
when using cronjobs. Probably quite a big
23 matches
Mail list logo
