Big error when rebased Silverblue from F40 to F39 (core-dump)

Hi all,

I rebased from 40 to 39, and all went well, but then when trying to update, reset, rebase or anything with ostree. I get this core error.

Job for rpm-ostreed.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status rpm-ostreed.service" and "journalctl -xeu rpm-ostreed.service" for details.
× rpm-ostreed.service - rpm-ostree System Management Daemon
     Loaded: loaded (/usr/lib/systemd/system/rpm-ostreed.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: failed (Result: core-dump) since Tue 2024-09-03 18:35:36 CEST; 18ms ago
       Docs: man:rpm-ostree(1)
    Process: 3343 ExecStart=rpm-ostree start-daemon (code=dumped, signal=ABRT)
   Main PID: 3343 (code=dumped, signal=ABRT)
        CPU: 43ms

I guess its more I can post as logs, but I start as this.

I have my F40 still left as a backup option, without being pined. So thats good, And all I want is either to save this F39 boot, or get rid of it.

What is going on there?

Ok, so i solved the critical part myself. And that was to rebase from my older F40 to F40. And the corrupted F39 disappeared.

So system back to normal. However. How do I step back from F40 to F39 without getting this problem?

Major version downgrades (going to an older Fedora Atomic Desktop major release) are completely unsupported and not tested.

Fedora 39 will be EOL in a few months. Anything preventing you from staying on Fedora 40?

Thanks for the answer.

So the rebase is more towards same version, or forward?

I do have a problem with F40, and on my other computer I pinned a version of F39. That is performing better. But on this computer, I installed F40 directly. And wanted to try out F39 after the install.

So I guess I have to solve the problem the real way. And is concerning wineasio and realtime. Something is chopping the low latency sound in F40.

Thanks again

Added upgrades