(In reply to Gian-Carlo Pascutto [:gcp] from comment #61) > >Can you please clarify what does fix-optional status for firefox 100 mean > >for this bug? > > It means that if there is a simple fix for the issue, release management > would've considered taking that fix into Firefox 100. As is hopefully rather > obvious, there isn't going to be a simple fix for this. It needs a ton of > work - that has progressed well, thankfully. > > >I assume this bug will be fixed once video decoding has been moved to a > >utility process (bug 1722051). > > The utility process makes it easier to move things in a separate processes > each with a custom sandbox, but the plan is to fix the current RDD process > for VA-API support before we consider that. The difficulty is adding support > for exactly those features VA-API needs - multiplied by each video driver > having slightly different requirements. Once the sandboxing code supports > that we can look if there'd be a meaningful security benefit in moving things > around.
Is there an official way of working around this in the meantime? Since disabling RDD sandbox isn't enough anymore on Firefox 100? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964547 Title: [upstream] RDD sandbox prevents HW-accelerated video playback To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs