search

fedora-silverblue / issue-tracker

Fedora Silverblue issue tracker
https://fedoraproject.org/atomic-desktops/silverblue/
123 stars 3 forks source link

I cannot install Chromium (due to dependency issues) #583

Closed marystern closed 3 months ago

marystern commented 3 months ago

I cannot install Chromium (due to unresolvable dependency issues, possibly with rpm-fusion). Please tell me how to get out of this conundrum, thanks!

BUG: I needed to install Chromium web browser, so I tried:

$ rpm-ostree install chromium
Checking out tree 7aa8642... done
Enabled rpm-md repositories: fedora-cisco-openh264 updates fedora rpmfusion-free-updates rpmfusion-free rpmfusion-nonfree-updates rpmfusion-nonfree rpmfusion-nonfree-nvidia-driver updates-archive
Importing rpm-md... done
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2024-03-12T11:45:42Z solvables: 3
rpm-md repo 'updates' (cached); generated: 2024-07-29T02:23:18Z solvables: 22716
rpm-md repo 'fedora' (cached); generated: 2024-04-14T18:51:11Z solvables: 74881
rpm-md repo 'rpmfusion-free-updates' (cached); generated: 2024-07-25T21:24:40Z solvables: 136
rpm-md repo 'rpmfusion-free' (cached); generated: 2024-04-20T12:11:51Z solvables: 422
rpm-md repo 'rpmfusion-nonfree-updates' (cached); generated: 2024-07-25T21:44:20Z solvables: 68
rpm-md repo 'rpmfusion-nonfree' (cached); generated: 2024-04-20T12:18:23Z solvables: 194
rpm-md repo 'rpmfusion-nonfree-nvidia-driver' (cached); generated: 2024-07-25T21:08:16Z solvables: 29
rpm-md repo 'updates-archive' (cached); generated: 2024-06-30T05:31:17Z solvables: 22869
Resolving dependencies... done
error: Could not depsolve transaction; 1 problem detected:
 Problem: conflicting requests
  - package mesa-va-drivers-freeworld-24.1.4-2.fc40.i686 from rpmfusion-free-updates requires libm.so.6, but none of the providers can be installed
  - package mesa-va-drivers-freeworld-24.1.4-2.fc40.i686 from rpmfusion-free-updates requires libc.so.6(GLIBC_2.38), but none of the providers can be installed
  - package mesa-va-drivers-freeworld-24.1.4-2.fc40.i686 from rpmfusion-free-updates requires libm.so.6(GLIBC_2.0), but none of the providers can be installed
  - package mesa-va-drivers-freeworld-24.1.4-2.fc40.i686 from rpmfusion-free-updates requires libm.so.6(GLIBC_2.29), but none of the providers can be installed
  - package mesa-va-drivers-freeworld-24.1.4-2.fc40.i686 from rpmfusion-free-updates requires libm.so.6(GLIBC_2.1), but none of the providers can be installed
  - package mesa-va-drivers-freeworld-24.1.4-2.fc40.i686 from rpmfusion-free-updates requires libm.so.6(GLIBC_2.27), but none of the providers can be installed
  - package mesa-va-drivers-freeworld-24.0.5-1.fc40.i686 from rpmfusion-free requires libm.so.6, but none of the providers can be installed
  - package mesa-va-drivers-freeworld-24.0.5-1.fc40.i686 from rpmfusion-free requires libc.so.6(GLIBC_2.38), but none of the providers can be installed
  - package mesa-va-drivers-freeworld-24.0.5-1.fc40.i686 from rpmfusion-free requires libm.so.6(GLIBC_2.0), but none of the providers can be installed
  - package mesa-va-drivers-freeworld-24.0.5-1.fc40.i686 from rpmfusion-free requires libm.so.6(GLIBC_2.29), but none of the providers can be installed
  - package mesa-va-drivers-freeworld-24.0.5-1.fc40.i686 from rpmfusion-free requires libm.so.6(GLIBC_2.1), but none of the providers can be installed
  - package mesa-va-drivers-freeworld-24.0.5-1.fc40.i686 from rpmfusion-free requires libm.so.6(GLIBC_2.27), but none of the providers can be installed
  - package mesa-va-drivers-freeworld-24.1.4-2.fc40.x86_64 from rpmfusion-free-updates requires mesa-filesystem(x86-64) = 24.1.4, but none of the providers can be installed
  - package mesa-va-drivers-freeworld-24.0.5-1.fc40.x86_64 from rpmfusion-free requires mesa-filesystem(x86-64) = 24.0.5, but none of the providers can be installed
  - glibc-2.39-17.fc40.i686 from updates  does not belong to a distupgrade repository
  - glibc-2.39-6.fc40.i686 from fedora  does not belong to a distupgrade repository
  - cannot install both mesa-filesystem-24.1.4-3.fc40.x86_64 from updates and mesa-filesystem-24.0.6-2.fc40.x86_64 from @System
  - cannot install both mesa-filesystem-24.0.5-1.fc40.x86_64 from fedora and mesa-filesystem-24.0.6-2.fc40.x86_64 from @System
  - cannot install both glibc-2.39-17.fc40.x86_64 from updates and glibc-2.39-8.fc40.x86_64 from @System
  - cannot install both glibc-2.39-6.fc40.x86_64 from fedora and glibc-2.39-8.fc40.x86_64 from @System

.. so, then I tried this:

$ rpm-ostree update \
  --uninstall rpmfusion-free-release \
  --uninstall rpmfusion-nonfree-release \
  --install rpmfusion-free-release \
  --install rpmfusion-nonfree-release
2 metadata, 0 content objects fetched; 788 B transferred in 1 seconds; 0 bytes content written
Checking out tree 9252e31... done
Enabled rpm-md repositories: fedora-cisco-openh264 updates fedora rpmfusion-free-updates rpmfusion-free rpmfusion-nonfree-updates rpmfusion-nonfree rpmfusion-nonfree-nvidia-driver updates-archive
Importing rpm-md... done
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2024-03-12T11:45:42Z solvables: 3
rpm-md repo 'updates' (cached); generated: 2024-07-29T02:23:18Z solvables: 22716
rpm-md repo 'fedora' (cached); generated: 2024-04-14T18:51:11Z solvables: 74881
rpm-md repo 'rpmfusion-free-updates' (cached); generated: 2024-07-25T21:24:40Z solvables: 136
rpm-md repo 'rpmfusion-free' (cached); generated: 2024-04-20T12:11:51Z solvables: 422
rpm-md repo 'rpmfusion-nonfree-updates' (cached); generated: 2024-07-25T21:44:20Z solvables: 68
rpm-md repo 'rpmfusion-nonfree' (cached); generated: 2024-04-20T12:18:23Z solvables: 194
rpm-md repo 'rpmfusion-nonfree-nvidia-driver' (cached); generated: 2024-07-25T21:08:16Z solvables: 29
rpm-md repo 'updates-archive' (cached); generated: 2024-06-30T05:31:17Z solvables: 22869
Resolving dependencies... done
error: Could not depsolve transaction; 2 problems detected:
 Problem 1: package libavdevice-free-6.1.1-19.fc40.x86_64 from @System requires libavcodec-free(x86-64) = 6.1.1-19.fc40, but none of the providers can be installed
  - conflicting requests
 Problem 2: package ffmpeg-free-6.1.1-19.fc40.x86_64 from @System requires libavfilter-free(x86-64) = 6.1.1-19.fc40, but none of the providers can be installed
  - conflicting requests

.. and then this (i cannot UNinstall!!)

$ rpm-ostree update   --uninstall rpmfusion-free-release   --uninstall rpmfusion-nonfree-release
2 metadata, 0 content objects fetched; 788 B transferred in 1 seconds; 0 bytes content written
Checking out tree 9252e31... done
Enabled rpm-md repositories: fedora-cisco-openh264 updates fedora rpmfusion-free-updates rpmfusion-free rpmfusion-nonfree-updates rpmfusion-nonfree rpmfusion-nonfree-nvidia-driver updates-archive
Importing rpm-md... done
rpm-md repo 'fedora-cisco-openh264' (cached); generated: 2024-03-12T11:45:42Z solvables: 3
rpm-md repo 'updates' (cached); generated: 2024-07-29T02:23:18Z solvables: 22716
rpm-md repo 'fedora' (cached); generated: 2024-04-14T18:51:11Z solvables: 74881
rpm-md repo 'rpmfusion-free-updates' (cached); generated: 2024-07-25T21:24:40Z solvables: 136
rpm-md repo 'rpmfusion-free' (cached); generated: 2024-04-20T12:11:51Z solvables: 422
rpm-md repo 'rpmfusion-nonfree-updates' (cached); generated: 2024-07-25T21:44:20Z solvables: 68
rpm-md repo 'rpmfusion-nonfree' (cached); generated: 2024-04-20T12:18:23Z solvables: 194
rpm-md repo 'rpmfusion-nonfree-nvidia-driver' (cached); generated: 2024-07-25T21:08:16Z solvables: 29
rpm-md repo 'updates-archive' (cached); generated: 2024-06-30T05:31:17Z solvables: 22869
Resolving dependencies... done
error: Could not depsolve transaction; 2 problems detected:
 Problem 1: package libavdevice-free-6.1.1-19.fc40.x86_64 from @System requires libavcodec-free(x86-64) = 6.1.1-19.fc40, but none of the providers can be installed
  - conflicting requests
 Problem 2: package ffmpeg-free-6.1.1-19.fc40.x86_64 from @System requires libavfilter-free(x86-64) = 6.1.1-19.fc40, but none of the providers can be installed
  - conflicting requests

.. I have no idea what this is trying to do and why it doesn't work!! PLEASE HELP! I seem to be stuck in some kind of "doom loop" :(

OS version:

 rpm-ostree status -b
State: idle
BootedDeployment:
● fedora:fedora/40/x86_64/silverblue
                  Version: 40.20240504.0 (2024-05-04T00:40:29Z)
               BaseCommit: 7aa864256ece01f4eae82fa739ad3ea3412e024f5c8905760dd16b644f9e6257
             GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC
      RemovedBasePackages: libavfilter-free libavformat-free libpostproc-free libswresample-free libavutil-free libswscale-free libavcodec-free 6.1.1-8.fc40 mesa-va-drivers 24.0.6-2.fc40
                           noopenh264 0.1.0~openh264_2.4.0-1.fc40
          LayeredPackages: android-tools dconf-editor ffmpeg gnome-boxes go gphoto2 gstreamer1-plugin-openh264 gvim kubernetes langpacks-en_GB libX11-devel mesa-va-drivers-freeworld
                           mozilla-openh264 rpmfusion-free-release rpmfusion-nonfree-release shotwell virt-manager vulkan-headers vulkan-tools
                   Pinned: yes

Additional context Add any other context about the problem here.

travier commented 3 months ago

You system is relatively out of date (40.20240504.0), so I would start with a full reset, then update, then re-layer what you need.

Watch out for https://fedoramagazine.org/manual-action-needed-to-resolve-boot-failure-for-fedora-atomic-desktops-and-fedora-iot/

I'll close this issue as there is nothing for us to fix here.

marystern commented 3 months ago

You system is relatively out of date (40.20240504.0), so I would start with a full reset, then update, then re-layer what you need.

Sorry, I'm a noob, so could you please give me the commands for what you're suggesting (I have no idea what exactly you mean)? thanks.

(I would have liked to have understood how to get out of the problem without going "backwards", and also why the system got into this weird state in the first place from May to July, not long in my mind! ;) )

(Did you have incorrect dependencies in your released packages?)

travier commented 3 months ago
  1. Start with rpm-ostree status and record your layered packages somewhere.
  2. Reset everything to default with rpm-ostree reset and reboot
  3. Follow the instructions from https://fedoramagazine.org/manual-action-needed-to-resolve-boot-failure-for-fedora-atomic-desktops-and-fedora-iot/
  4. Update to the latest version with rpm-ostree update and reboot
  5. Re-layer everything that you need.