Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing library: libc.so.6 #3730
Missing library: libc.so.6 #3730
Comments
Ubuntu 14.04.2 desktop 64-bit (clean fresh install)
default AMD radeon open source drivers
Steam client 1.0.0.49
Steam needs to install these additional packages:
libgl1-mesa-dri:i386, libgl1-mesa-glx:i386, libc6:i386
[sudo] password for *****:
.
Reading package lists. Done
Building dependency tree
Reading state information. Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libgl1-mesa-glx:i386 : Depends: libglapi-mesa:i386 (= 10.1.3-0ubuntu0.3)
unity-control-center : Depends: libcheese-gtk23 (>= 3.4.0) but it is not going to be installed
Depends: libcheese7 (>= 3.0.1) but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
You are missing the following 32-bit libraries, and Steam may not run:
libc.so.6
Note: Everything was working fine on 14.04.1
The text was updated successfully, but these errors were encountered:
Assigning separately just in case these are separate issues.
Confirming, I have this issue on Arch Linux 64-bit. Appeared after the latest Steam update.
Running Steam on arch 64-bit
STEAM_RUNTIME has been set by the user to: /home/fincer/.local/share/Steam/ubuntu12_32/steam-runtime
Error: You are missing the following 32-bit libraries, and Steam may not run:
libc.so.6
/home/fincer/.steam/root/steam.sh: line 756: /home/fincer/.steam/root/ubuntu12_32/steam: Too many levels of symbolic links
I can also confirm this, Ubuntu 15.04. It wants, exactly as dsx75 says, to install these packages: libgl1-mesa-dri:i386, libgl1-mesa-glx:i386, libc6:i386
But when I try to apt-get them, it can’t even find them.
Try echo $HOME and see if your $HOME ends in a slash. That was the problem with my installation — that made the check
if [ «$STEAMROOT» != «$STEAMROOTLINK» -a «$STEAMROOT» != «$STEAMDATALINK» ]; then
fail since /my/homedir//.steam. != /my/homedir/.steam.
After removing the / in /etc/passwd Steam found its libraries again and the looping root link fixed itself.
I installed these dependencies as prerequisites to building servo and it seems to have fixed this (on Ubuntu 14.04.2 LTS which I think was a new install):
sudo apt-get install curl freeglut3-dev \ libfreetype6-dev libgl1-mesa-dri libglib2.0-dev xorg-dev \ msttcorefonts gperf g++ cmake python-virtualenv \ libssl-dev libbz2-dev libosmesa6-dev libxmu6 libxmu-dev
My guess is the fix was libgl1-mesa-dri or libosmesa6-dev but I’m not really sure as I didn’t track it down.
I was having this problem on newly installed 64-Bit Ubuntu 14.04.2 LTS.
Steam was having problem with these 3 packages:
libgl1-mesa-dri:i386, libgl1-mesa-glx:i386, libc6:i386
I tried this command:
sudo apt-get install libc6:i386 libgl1-mesa-dri-lts-utopic:i386 libgl1-mesa-glx-lts-utopic:i386
This removed the problem regarding missing library libc.so.6 on my machine.
@voyager2102 This solution works for me! Thanks!
For the people who may have problems understanding the solution:
1. navigate to /etc/ and edit the text-file «passwd» as root
2. search for your username and you will find the path to your home directory in that line
3. change the path from . /path to your home directory**/** to . /path to your home directory (without the «/» at the end)
4. restart your computer
Alternatively, you could you the very old, very reliable utility usermod -m -d /home/username username which protects you, the sysadmin, from typos and other forms of chaos that could render your system inaccessible.
I can confirm @takeeast ‘s claim. My home directory was set to «/home/user/» and after I had fixed that to «/home/user» Steam started to work again. Conclusion: The problem is not a bug in steam but a wrong home directory string.
@pilotforhire: Your conclusion is wrong. The bug is in steam as the field you’re talking about is defined as «Path to the user’s home directory.» or in longer form: «The home directory field provides the name of the initial working directory.» In this context it does not matter if you specify a trailing slash or not and any program parsing this has to be aware of that.
The author of the script might have e.g. used readlink -f or a similar tool to canonicalize the path before using it.
Same problem with a fresh install of Ubuntu 14.04.2 64bits.
I install steam.deb package from this location : https://github.com/ValveSoftware/steam-for-linux.
Result :
You are missing the following 32-bit libraries, and Steam may not run: libc.so.6.
Nota :
I successfully installed Steam via synaptic.
I am getting this after an update today. I have installed all of these packages, and I have a /lib32/libc.so.6 , so it’s certainly there, I just don’t know why steam can’t find it :/
Furthermore, running ldd on the contents of ~/.steam/bin shows no entries for it being missing, and several where it’s properly linked.
and rebooting the computer fixed the issue for me. At last!
Same problem with a fresh install of Ubuntu 14.04.1 64-bit. $HOME does not end in / so voyager’s fix won’t work. Trying to install libgl1-mesa-dri gives the same error about a dependency that cannot be resolved, so narenlegha and mdinger’s fix doesn’t work.
- This tells you what to put instead of «lts-vivid» for your machine dpkg -l | grep xserver-xorg-core
- Run the following with your substitution for lts-vivid (two places) sudo apt-get install xserver-xorg-lts-vivid libgl1-mesa-glx-lts-vivid:i386
So, for example, if dpkg -l | grep xserver-xorg-core gives you:
ii xserver-xorg-core-lts-trusty 2:1.17.1-0ubuntu3~trusty1 amd64 Xorg X server - core server sudo apt-get install xserver-xorg-lts-trusty libgl1-mesa-glx-lts-trusty:i386 Just tried to install Steam using the deb package. Same problem as everyone.
I use Linux Debian Jessie 8, kernel version 3.16.0-4 (64 bits) and my desktop is KDE4.
I tried literally everything stated in this page. Nothing works. The program still reports unmet dependencies:
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
libgl1-mesa-dri:i386 : Depends: libllvm3.5:i386 but it is not going to be installed
Recommends: libtxc-dxtn-s2tc0:i386 but it is not going to be installed or
libtxc-dxtn0:i386
E: Unable to correct problems, you have held broken packages.
Press return to continue:
When trying to install: libgl1-mesa-dri:i386, libgl1-mesa-glx:i386, libc6:i386
Steam will not continue without these libraries.
I tried using steamcmd.sh, it says «./steamcmd.sh: line 29: /home/[user]/steamcmd2/linux32/steamcmd: No such file or directory».
I tried installing the libraries manually. Same issue as above (unmet dependencies).
I tried the symbolic links. It didn’t work.
My passwd user entry does not end with a slash (/). It makes no difference.
Why is /lib/libc.so.6 missing?
reveals that it’s in /lib/i386-linux-gnu/libc.so.6 , but a script I was running expected it to be directly under /lib , so why isn’t there at least a symlink? Would I risk breaking anything if I put a symlink there?
3 Answers 3
libc.so was moved as part of the multiarch work in Ubuntu 11.04. The reason that there can’t be a symlink there is that the purpose of multiarch is to make it possible to install both the i386 and amd64 versions of libc at the same time so that you can run 32-bit binaries more easily on 64-bit systems and vice versa (and other similar situations). If the libc6 package contained a symlink to the new location, then the versions of that package for different architectures wouldn’t both be installable at the same time (which version of the symlink would dpkg pick?), defeating the entire point of the exercise.
Anything that hardcodes the path to libc.so must be updated to work properly from Ubuntu 11.04 onwards. If the script you’re talking about is part of Ubuntu, please report a bug on it and add the multiarch tag.
The processor I’m using doesn’t even support 64 bit instructions. Would you say there’s any risk associated with manually adding a symlink? Not sure I need to do that, but if. Anyway, this seems to be the correct answer. Thanks.
@Erik B: what? Are you telling me you’re trying to use a 64 app on a 32 bits processor? That’s definitely not going to work. 32 bits apps work fine on a 64 bits processor, but not vice versa.
@Lekensteyn that’s definitely not what I’m saying. What I’m saying is that I have no use for the 64 bit library. So on my particular system there’s not going to be any confusion about whether /lib/libc.so.6 is the 32 or 64 bit library.
If you’re never going to use 64-bit packages, I doubt there’s any significant risk in adding a symlink, no.