Fedora OBS Drama Resolved
Fedora OBS Drama Resolved
The unofficial OBS Studio Flatpak on Fedora Flatpaks is, seemingly, poorly packaged and broken, leading to users complaining upstream thinking they are...
As an update to everyone following, I had a meeting today with the Flatpak SIG and Fedora Project Leader, which was a very good conversation. We discussed the issues, how we got here, and what next steps are. For anyone not interested in the specific details, the OBS Project is no longer requesting a removal of IP or rebrand of the OBS Studio application provided by Fedora Flatpaks. This issue should be used for tracking of the other specific, technical issues, that the Fedora Flatpak does still have, which I will address below. From our perspective, there were two key points that we feel are the most important to address:
- The issue with the Qt runtime having regression
- The issue of not knowing where to report bugs for what is a downstream package
For the first bullet, this should be resolved with the update to the latest runtime, which includes Qt 6.8.2 that has the fixes for those regressions in it. For the second, this is obviously a much larger issue to tackle, especially for a project as large as Fedora. We had some very good discussion on how this might be accomplished in the medium-long term, but don't consider it a blocker at this point. We plan to stay engaged and offer our perspective as an upstream project. In addition to those two previously blocking issues, we discussed a handful of other problems with the Fedora Flatpak. I'll keep the details high level in the interest of brevity on this update:
- OBS Studio running on Mesa LLLVM pipe instead of with hardware acceleration (i.e. the GPU)
- X11 Fallback leading to OBS crashing
- VLC Plugin not behaving as expected in the sandbox, needs testing
- Shipping of third-party plugins in the Fedora Flatpak
The discussion was positive and they are actively working to resolve those issues as well, which should hopefully only affect a small number of users. I would like to give a final thank you to Yaakov and the FPL for taking the time to talk to us today.
You're viewing part of a thread.
Has a software update ever changed something in a way you dislike? When it's proprietary software your choices are to:
- tolerate the anti-feature
- downgrade and keep using an older version instead (if feasible also has demerits)
- hope someone reverse engineers a work-around
- stop using the software
When the software is free (libre) then a communities can change it (e.g. removing an anti-feature) via the source code.
Sadly it's not enough to simply "then don't use it" - proprietary software proliferates society (interacting socially, with the government, with banks, etc). Since it's better to be in control of your own computing anyway then might as well promote the values of software freedom.
Yes, yes, we get it. Proprietary software bad. Don't use it. Again I ask: what is the problem?
Sadly it's not enough to simply "then don't use it"
...why not?
proprietary software proliferates society (interacting socially, with the government, with banks, etc).
So don't use it?
might as well promote the values of software freedom.
Once again, making it available is not "promoting" it.
Listen, I wish all software was FOSS, but it's not, and it never will be. It's not feasible. Even when it is, it's often terrible and the proprietary ones are way better, because they can actually afford to develop it properly.
Communication is difficult. I felt like I gave a useful answer but evidentially it was not an answer for you. I hope someone else can answer your questions.
You ignored the question that I asked in favor of one that I did not.