Description of problem: I am unable to install the Steam client using the Software Management tool with only 64-bit repositories available. The popup says it can't be installed due to unsatisifed libcurl4. lib64curl4 is installed. If I enable 32-bit repositories, selecting steam adds a bunch of dependencies, but still says it can't be selected without giving a reason. I have to manually select libcurl4 32-bit to be able to select steam. It then will install. Version-Release number of selected component (if applicable): steam-1.0.0.61-1.mga7.nonfree How reproducible: Always Steps to Reproduce: 1. Open Software Management using only 64-bit repositories 2. Select steam package 3. Get error message
Thanks you for reporting this. I cannot see another similar open bug, so assigning to akien.
Summary: Unable to install steam client due to unsatisfied libcurl4 => Unable to install steam client due to unsatisfied (32-bitt) libcurl4Assignee: bugsquad => rverscheldeSource RPM: steam-1.0.0.61-1.mga7.nonfree => steam-1.0.0.61-1.mga7.nonfree.src.rpm
Steam has 32-bit dependencies, so it's normal that it can't be installed if you disable the 32-bit repositories. You need to enable them (and make sure the package lists are updated) to install steam. > If I enable 32-bit repositories, selecting steam adds a bunch of dependencies, but still says it can't be selected without giving a reason. I would need to know what the exact output was to help debug it.
Before I enabled the 32-bit repositories, the message Software Management gave when selecting steam to install was ------ Sorry, the following package cannot be selected: - steam-1.0.0.61-1.mga7.nonfree.x86_64 (due to unsatisfied libcurl4) ------ When I enabled the 32-bit respositories, and selected steam to install, about 10 additional packages were identified as necessary. I don't remember the list, but libcurl4 was not among them. When I clicked OK, I got the message: ------ Sorry, the following package cannot be selected: - steam-1.0.0.61-1.mga7.nonfree.x86_64 ------ No reason for being unable to select the steam package was given. When I manually selected libcurl4, it also autoselected several packages. I was then able to install steam. I figured steam depends on 32-bit libraries, and only having the 64-bit libraries installed and 64-bit repositories available causes the steam installation to fail. However, this doesn't explain why it didn't automatically select libcurl4 when I enabled the 32-bit repositories.
To try to recreate this I uninstalled steam, steam-udevrules, and libcurl4. I then disabled the 32-bit repositories and cleaned out unused packages with ------- urpme --auto-orphans ------- Many more packages were removed than just those that were installed during this session. After rebooting, when I went back into Software Management to install the steam client, it produced the following message: ------- Sorry, the following package cannot be selected: - steam-1.0.0.61-1.mga7.nonfree.x86_64 (due to unsatisfied libudev1) ------- I then enabled the 32-bit Core and Core Updates repositories and selected the steam client again. This time it identified the following packages to be installed: - libbrotlicommon1-1.0.7-2.mga7.i586 - libbrotlidec1-1.0.7-2.mga7.i586 - libcurl4-7.66.0-1.mga7.i586 - libdbus-glib1_2-0.110-2.mga7.i586 - libdbus1_3-1.13.8-4.1.mga7.i586 - liblz4_1-1.9.2-1.mga7.i586 - libmesaglu1-9.0.0-8.mga7.i586 - libnghttp2_14-1.38.0-1.1.mga7.i586 - libsystemd0-241-8.5.mga7.i586 - libudev1-241-8.5.mga7.i586 - steam-udevrules-1.0.0.61-1.mga7.noarch This list is much shorter than the list of packages I needed to install the first time, so evidently some of the packages I previously needed remained from the first installation. Note that libcurl4 is included in this list. This time the installation was successful without manually selecting any additional packages. I'll probably be doing a new install in the next few weeks. I'll let you know if I can reproduce this bug.
I'll close this bug report for now. Please reopen if you can recreate it. Most likely cause of the reported behavior would be if the in the first try the 32 bit core updates was enabled, but not the 32 bit core release, or possibly the reverse, though that doesn't explain it not having libcurl in the list of required packages, nor the lack of a reason being given.
Resolution: (none) => WORKSFORMEStatus: NEW => RESOLVEDCC: (none) => davidwhodgins