Elementary 8.0 - some runtimes won't update

[R-st25]

I just installed Elementary 8.0, and after a lot of work, it runs generally fine. Except that in the update screen for the app center, some of the runtimes that the system tells me should be updated won't update. I get the error message "Aborted due to failure (While trying to apply extra data: apply_extra script failed, exit status 256)". Any ideas?

Thank you in advance!

[teamcons]

try in a terminal

flatpak repair

then

flatpak update

[R-st25]

Thank you, that solved it!

[imp667]

This did not resolve my issue.

[teamcons]

did you try both commands and what is their output ?

[Giio]

I'm having the same problem and after flatpak repair and update getting the same error msg.

[nstrud]

same here...

[nstrud]

..I had 16 updates finally ended with 2 updates one being 2 runtime updates. Each of 4 times some updates were installed but it was very slow and still gives me that error msg. I have turned off automatic updates and i will try again tomorrow.

[CarlSeiler]

I have the same issue. When I run flatpak repair it appears to go through everything succesfully. When I do flatpak update it says "Nothing to do." Then I still get Aborted due to failure (While trying to apply extra data: apply_extra script failed, exit status 256) This is on a fresh install of EOS8 downloaded earlier this week and installed this morning.

[UncleTallest]

Regarding the flatpak update error: Aborted due to failure (While trying to apply extra data: apply_extra script failed, exit status 256)

So, I have done some thorough research into the upstream parts of this issue and it seems to me that the numerous flatpaks that throw this issue are failing while trying to access things outside of their sandbox. While the flatpak maintainers are hemming and hawing over whether this is technically a "permission" or something else entirely, it is not something that we should override on our end.

All of that being said this is very annoying for our users. I will continue monitoring and commenting upstream while they try to find the root cause of this bug.

For now, the basic work-around is the same as mentioned by teamcons above:

In a terminal window:

flatpak repair
flatpak update

If you still run into issues after performing the two steps above, you can remove the installed version of what's causing this (in numerous cases it seems to be the openh264 flatpak) and reinstall it thusly:

flatpak remove --unused 
flatpak update

Yes, you will have to do this "fix" in the terminal each time a flatpak update fails until upstream can fix the underlying issue. This could take some time as it affects so many obliquely related applications that it is hard to trace the underlying cause.