You are not logged in.
I updated today and now Steam doesn't launch:
# steam
Running Steam on arch rolling 64-bit
STEAM_RUNTIME is enabled automatically
Pins up-to-date!
Error: You are missing the following 32-bit libraries, and Steam may not run:
libc.so.6
# steam-native
Running Steam on arch rolling 64-bit
STEAM_RUNTIME is disabled by the user
Error: You are missing the following 32-bit libraries, and Steam may not run:
libc.so.6Strangely, I've updated several times since the latest release of steam, lib32-glibc, and glibc, so I don't think those packages were changed on my computer today. I reinstalled all three in case of storage corruption. I installed steam-native-runtime to see if it would work and it gives the same error.
Last edited by bicyclingrevolution (2019-09-28 01:34:04)
Offline
Please paste the full pacman log for the update.
Moving to NC...
Offline
Thank you for your prompt reply!
Upon reviewing the log, I realized the problem began before updating today. I had rebooted into Windows and when I booted back into Arch I saw the dialog box with the error (Steam runs in the background at all times). I then reinstalled glibc and lib32-glibc [2019-09-19 09:16], and when that didn't solve the problem, I did a full update. Still no luck, so installed steam-native-runtime (not previously installed) [2019-09-19 17:44], then reinstalled steam [2019-09-19 19:15]. The last update before the issue began was [2019-09-02 21:57] so I started the paste there, but I've been using steam with no issues from then until today.
Offline
Your pacman log is a litany of partial updates.
Don't -Sy $package: it breaks things.
Offline
Yes, all those -Sy are from Octopi automatically checking for updates. I realize now that if there are updates available and I want to install a package, I need to update as well. However, am I wrong in thinking that any problems from partial updates are solved by simply running pacman -Syu? I did that just now, rebooted, and steam still can't find libc.so.6.
Offline
Yes, all those -Sy are from Octopi automatically checking for updates.
If that is how Octopi is suposed to work, it has no place on an Arch system.
I did that just now, rebooted, and steam still can't find libc.so.6.
Paste the output of `pacman -Qm` and `pacman -Qkk`, and `pacman -Syu --debug`.
Offline
pacman -Qm: http://codepad.org/Rrzdu4VM
pacman -Qkk: http://www.rafb.me/results/fq1aIG77.html
I don't know if the "permission denied" errors are a problem or if I'm supposed to run that with sudo, so...
sudo pacman -Qkk: http://www.rafb.me/results/wrybdo92.html
pacman -Syu --debug: http://www.rafb.me/results/HZ8zFz76.html
Offline
I created a new user account and Steam launched successfully. The problem must exist somewhere in my ~/, so I renamed all the Steam config files I could find (to make Steam recreate them):
~/.steampath
~/.steampid
~/.steam/
~/.local/share/Steam
And no more libc error. Restoring my original .local/Steam folder made the error reappear. Now I can drill down to the source of the issue!
There are no libc files in the functioning Steam folder, nor even a link to /usr/lib/, so I don't know what went wrong, but it looks like most of the libraries are contained in ~/.local/share/Steam/ubuntu12_[32,64]. I replaced those two folders in my original Steam folder with the ones from the reinstalled Steam folder. Steam launched, downloaded a 50 MB "update," and got me right back to my game library with nothing amiss. Problem solved!
Offline
However, am I wrong in thinking that any problems from partial updates are solved by simply running pacman -Syu?
Whether that is enough entirely depends on the things the partial updates messed up.
It seems octopi devs have stopped doing partial upgrades in v 0.10.0 development code.
BugFix: Notifier now uses "checkupdates" instead "pacman -Sy[y]". This means Octopi no longer can lead
the OS to a "partial updates" state and works gracefully with other package tools.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline