Ostree update failes because of libstdc++-14.2.1-1

Hello everyone. I been using silverblue for some time now, and I really like it.

But now I have run into this problem that seems to be an error from the developer side? Maybe it will go away after a few days, like many of my update problems. But if not. What is this?

error: Checkout libstdc+±14.2.1-1.fc40.i686: Hardlinking ac/859321dfe787f24d016e20e585da522713d84edbf0f6fb4e021543ece37264.file to init.cpython-312.opt-1.pyc: File exists

I can give any log you might need, I myself dont know what you need. But other than that. I use steam and lutris. And also run some stuff from distrobox. But the latter seem to be unrelated.

Many thanks in forehand.

3 Likes

Please provide the output of the rpm-ostree status command as pre-formatted text.

I have the same issue on Fedora Kinoite. Here is my output from rpm-ostree status

$ rpm-ostree status
State: idle
Deployments:
● fedora:fedora/40/x86_64/kinoite
                  Version: 40.20240819.0 (2024-08-19T01:35:50Z)
               BaseCommit: 2cd6ef602a2425ec788d4c940b9ff9d215e703eb4dd1067d670a894b82aa713f
             GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC
      RemovedBasePackages: mesa-va-drivers 24.1.5-2.fc40
          LayeredPackages: gstreamer1-plugins-bad-free-extras gstreamer1-plugins-bad-freeworld gstreamer1-plugins-ugly
                           gstreamer1-vaapi iperf ksshaskpass libavcodec-freeworld libva-utils lm_sensors
                           mesa-va-drivers-freeworld neofetch powerstat
            LocalPackages: rpmfusion-free-release-40-1.noarch rpmfusion-nonfree-release-40-1.noarch
1 Like

Here is mine

State: idle
Deployments:
● fedora:fedora/40/x86_64/silverblue
                  Version: 40.20240821.0 (2024-08-21T00:59:22Z)
               BaseCommit: 308c5a6f8b0f030457a3e79be3e7f75d960254c8803d0e13b43750391deb5f5f
             GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC
          LayeredPackages: alsa-plugins-jack alsa-plugins-pulseaudio curlftpfs distrobox
                           ftp gcc grub-customizer libappindicator-gtk3 make vpn
                           openssl pavucontrol pcmanfm
                           pipewire-jack-audio-connection-kit-devel.i686
                           pipewire-jack-audio-connection-kit-devel.x86_64
                           python3-pyasyncore qpwgraph realtime-setup wine wine-devel.i686
                           wine-devel.x86_64

  fedora:fedora/40/x86_64/silverblue
                  Version: 40.20240820.0 (2024-08-20T01:01:41Z)
               BaseCommit: e45ee5cb506f6ddc4fbe0d4274635e656c294b6e99e795dadc44c698a1fb6ffe
             GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC
          LayeredPackages: alsa-plugins-jack alsa-plugins-pulseaudio curlftpfs distrobox
                           ftp gcc grub-customizer libappindicator-gtk3 make vpn
                           openssl pavucontrol pcmanfm
                           pipewire-jack-audio-connection-kit-devel.i686
                           pipewire-jack-audio-connection-kit-devel.x86_64
                           python3-pyasyncore qpwgraph realtime-setup wine wine-devel.i686
                           wine-devel.x86_64

yeah, it happens when fedora branches(it happened with me when fedora 40 were branched, and now) the issue is probably with rpmfusion out of sync with fedora, i usually just wait

1 Like

Added atomic-desktops, rpm-ostree

Unfortunately, the RPM fusion problem seems to be occurring more and more frequently.

The problem with Steam now and libavcodec-freeworld or also mesa-va-drivers-freeworld

Especially as the updates have not been able to be installed for days now.

And well you can also solve the problem with sledgehammer with rpm-ostree reset -l -o -r you start again from the beginning but you have installed the updates:==)

Waiting is good, but several days!

3 Likes

Yeah got the same problem…man I hope those rpm fusion guys fix all the problems with silverblue it’s not the first time stuff like this happened to me

IMO they don’t have the manpower of fedora, nor servers enough to keep up with updates, specially with the amount of rebuilding that fedora are doing right now for the next release

It’s clear that it will take longer if there aren’t enough people.
But then you should also communicate this and say that you are still looking for people who can support or help in some way.

And not the way it has been lately, with Mesa Update coming and then waiting again for RPM Fusion.

and now with libstdc+±

The real question for me is, I can wait for updates, not a big thing. As long as I know it will be fixed and not a permanent error. However. How is it to admin this? Installing new packages what ever it might be, and not performed an update.

It happens that I need to do an update before an ostree install. Is that function down or a way around it? Because if it is, the wait is a problem?

you can just wait

I can wait for updates, a long time. I have little need for them really. But nice to be up to date. However, I can not install anything new, now when testing. And that is a big problem.

Hi everyone, I have the same issue.
How to fix this?

Is it an out of sync thing ? Will it fix itself ?
Or does this one require manual intervention from user ? Like what is init.cpython-312.opt-1.pyc: File exists ? Is it a file somewhere in my system I need to delete for the update to go through ?

It’s amazing how people react here when users want to help and point out problems that are obvious.

Shifting the blame from A to B is certainly not helpful. And the communication problems of rpm-fusion and Fedora Team are not relevant for the users, which now reflects that some maintainers are perhaps not suited to tackle problems together.

And if they are complaining because their workload increases when a problem occurs, then perhaps they should work on their communication. Instead of complaining, they should offer to help or solve what looks like internal problems with rpm-fusion and fedora first.

The users are certainly not interested in what does not work internally or does not work properly and is pushed from A to B, but in a prompt solution to the problem

3 Likes

Either way, In my case its not libavcodec-freeworld, but perhaps alsa? I am not even sure what uses this libstdc in my ostree. But I guess I am goint to sit tight, and all tickets fly the way they should.

I have this problem too : (
Updates not installing:
“error: Checkout libstdc+±14.2.1-1.fc40.i686: Hardlinking ac/859321dfe787f24d016e20e585da522713d84edbf0f6fb4e021543ece37264.file to init.cpython-312.opt-1.pyc: File exists”

1 Like

Just after the complaint all the update installed. Is it OK now for you as well, or, I wonder, I did something for the updates to install?