Runtime updates fail to install on a fresh installation citing "exit status 256"

[truefakts]

What Happened?

Full disclosure, I'm running this in a VM. But I doubt that is related to this issue

I encountered a persistent issue with system updates on a fresh installation of the early access 8.0 build. During the initial out-of-the-box experience, I enabled automatic updates and allowed the machine to idle for approximately 10 minutes. Subsequently, I received a notification to restart the machine to complete the updates, which I did.
Upon reboot and login, the update notification reappeared. I repeated the process, restarting the machine two more times. However, every time I log in, I am immediately presented with a notification asking for a restart to finalize the system updates.
Next I attempted to apply the updates manually through the App Center. During the manual update attempt, I encountered the following error:

Error Code: Aborted due to failure (While trying to apply extra data: apply_extra script failed, exit status 256)

Clicking the “Repair” button initiated a loading icon for approximately 1 minute, after which the repair animation disappeared. Subsequently, I was prompted to apply updates again, but the same error persisted.
To aide in debugging, I will refrain from applying updates manually via the terminal, in case additional information is needed. Please review the attached screenshot of what the user sees.
Thanks for reading!

Log output:
journalctl.txt

Steps to Reproduce

NOTE: This was tested in a VM using the flatpak of Gnome Boxes. Should be irrelevant, but I wanted to point that out

1. Install a fresh copy of elementaryos-8.0-daily.20240217.iso
2. Login and follow the instructions in the greeter to enable automatic system updates
3. Allow the automated system updates to do their thing
4. When prompted, reboot the machine
5. Note that you will be prompted to reboot the machine on every reboot
6. Forcing updates via the app center will fail resulting in this error code. There is no way to recover from this using the graphical application, including the "Repair" button

Error Code: Aborted due to failure (While trying to apply extra data: apply_extra script failed, exit status 256)

Expected Behavior

Unless I'm mistaken, the latest blog post leads me to believe that operating system updates should work the same way it works on Fedora KDE spin. Ie. operating system updates should be applied using the new "offline updates" feature:

1. The user is prompted to restart the machine to apply updates
2. The machine reboots, POSTs and Grub loads
3. Updates apply with a progress bar and some kind of "don't restart your computer" type message appears on the screen
4. After updates apply, the machine reboots and the next startup is normal.
5. Similarly, users can shutdown the machine instead of rebooting when prompted. This process repeats on the next boot

OS Version

Early Access

Software Version

Latest release (I have run all updates)

Log Output

See attached file

Hardware Info

This was tested in a VM using Gnome Boxes in a flatpak

Host machine: (probably irrelevant)

• Linux Mint 21.3 Cinnamon Edition
• Linux drew-desktop 6.7.3-060703-generic #202401311935 SMP PREEMPT_DYNAMIC Thu Feb 1 00:46:47 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
• Ryzen 5 5600X
• RX 6600 XT
• 16GB of RAM

VM running elementary OS

• OS: elementary OS 8 Early Access x86_64
• Host: KVM/QEMU (Standard PC (Q35 + ICH9, 2009) pc-q35-7.2)
• Kernel: 6.6.0-14-generic
• Uptime: 1 min
• Packages: 1736 (dpkg), 17 (flatpak)
• Shell: bash 5.2.21
• Resolution: 2560x1440
• DE: Pantheon
• WM: Mutter(Gala)
• Theme: io.elementary.stylesheet.mint [GTK3]
• cons: elementary [GTK3]
• Terminal: io.elementary.t
• GPU: 00:01.0 Red Hat, Inc. QXL paravirtual graphic card
• Memory: 981MiB / 3896MiB

[lenemter]

System updates are now managed by System Settings, not AppCenter. I can confirm the reappearing notification though

[truefakts]

Was there a recent change? I retested this again using the latest early access build and I can no longer reproduce. If someone can confirm my new findings, I'll be happy to close this bug report

[danirabbit]

The Ubuntu repos themselves are moving a lot, so it's possible this was a temporary Ubuntu packaging bug. It still might be worth seeing if we can more elegantly handle this kind of package managing error so it's probably worth waiting for a maintainer to check it out

[danirabbit]

Ah you know after looking at this screenshot this is a Flatpak runtime update thing so this is still handled in AppCenter. Gonna transfer back there