Update Flatpak runtime to 6.8

[AsciiWolf]

Operating System Info

Other

Other OS

No response

OBS Studio Version

31.0.1

OBS Studio Version (Other)

No response

OBS Studio Log URL

n/a

OBS Studio Crash Log URL

No response

Expected Behavior

The Flatpak runtime used by OBS is awfully outdated and using an end-of-life runtime. This is a problem that should ideally be solved as soon as possible. I am aware of the issues that OBS has with newer Qt versions, but shipping an unsupported (and potentially dangerous from a security standpoint) runtime is not a good solution.

The Flatpak should be updated to a latest 6.8 runtime.

Current Behavior

The Flatpak is still using an outdated, unsupported 6.6 runtime.

Steps to Reproduce

$ flatpak info com.obsproject.Studio

Anything else we should know?

No response

[gxalpha]

Duplicate of #11478

[Fenrirthviti]

lol.

[AsciiWolf]

lol.

Is there something funny? Also, what's the point of marking a new ticket as a duplicate of another one that was closed more than three months ago without any real solution? You still ship outdated, insecure software to end-users and you provided no real answer / ETA on when this could get fixed. I really hope this won't take next few months or even more...

edit: I see that you provided the answer I was looking for here. Thanks.

[Fenrirthviti]

Sorry, I found this amusing because of all the ongoing discussion/conflict with Fedora about this specific topic, having explained it a dozen times over, and still seeing people disagree with us and get upset we haven't made a new release in the 2 weeks since a fix was available. As mentioned in the link you provided, it's planned to be updated in the next release, and we are extremely, keenly, acutely, and whatever other qualifiers you can think of, aware of this and do not consider it acceptable long term to ship an EOL runtime, and have never, ever, had plans to do so. It was always a temporary decision.

You just stepped on a previously laid landmine, nothing directed at you.

[AsciiWolf]

Thanks for the reply! I apologize for probably sounding too offensive/aggressive in my previous comment.