What happened to my Steam?

Support Software & Applications
1

I just wanted to start Steam when I noticed it’s not installed anymore. I never uninstalled it.

Further more when I try to install it again I just get a bunch of 404s:

Preparing...
Resolving dependencies...
Checking inter-conflicts...
Download of lsof (4.98.0-2) started
http://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
Download of lib32-nss (3.94-1) started
Download of lsof (4.98.0-2) finished
Download of lib32-libxss (1.2.4-1) started
Download of lib32-libxss (1.2.4-1) finished
https://mirror.easyname.at/manjaro/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
Download of steam (1.0.0.78-4) started
https://mirrors.dotsrc.org/manjaro/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
Download of lib32-nss (3.94-1) finished
https://manjaro.kyberorg.fi/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
https://ftp.psnc.pl/linux/manjaro/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
https://mirror.telepoint.bg/manjaro/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
https://fosszone.csd.auth.gr/manjaro/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
Download of steam (1.0.0.78-4) finished
http://mirror.terrahost.no/linux/manjaro/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
http://ftp.free.org/mirrors/repo.manjaro.org/repos/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
https://mirror.easyname.at/manjaro/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
https://mirrors.dotsrc.org/manjaro/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
https://manjaro.kyberorg.fi/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
https://ftp.psnc.pl/linux/manjaro/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
https://mirror.telepoint.bg/manjaro/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
https://fosszone.csd.auth.gr/manjaro/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
http://mirror.terrahost.no/linux/manjaro/stable/multilib/x86_64/lib32-sqlite-3.43.1-1-x86_64.pkg.tar.zst: Error 404
Failed to commit transaction:
failed to retrieve some files

Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

2

For the package manager in general …
Does your internet work?
First things would be sort mirrors and update:

sudo pacman-mirrors -f && sudo pacman -Syu

For steam …
How was it installed?
We can check for the package:

pacman -Qs steam

We can also look at the logs:

grep -i steam /var/log/pacman.log

PS.
Most of the mirrors you are trying to use are out of date.
https://repo.manjaro.org/

3

Your database is not in sync with the mirror.

Update the database

sudo pacman -Syyu
3 Likes
4

The 404 (file not found) errors are because the package doesn’t exist on the mirror.

It usually means the package has been updated (the filename has the version in it), and your local database has the old version. I suppose it could also be that the mirrors are in the middle of updating, or that your local database has a newer version than the mirror.

Which is the long version of what @linux-aarhus said.

1 Like
5

Who wants to take bets the 2 'y’s are unnecessary … OP simply didnt do sync along with install ?
(just pacman -S on an old sync when should be -Syu … see post #2)

6

I never use pacman, I just use the pamac GUI. Does that not automatically update its database? I mean it must, how else would it offer me updates.

I guess I haven’t done updates for too long. I’m trying a system update now.

e: now it worked

7

It is expected that you should perform updates regularly on a rolling release distribution such as Manjaro. If this isn’t done, you should expect all kinds of inconsistencies and potential problems. A standard point release model is generally more forgiving, especially for users who habitually ignore the need to update.

It will be worth your time to research the differences between pacman, pamac and pamac-manager (GUI).

  • pacman – installs/updates only from the official Manjaro repositories. It is often recommended to use pacman to update your system before using any other method.

  • pamac / pamac-manager – installs/updates from official repositories and the AUR, plus Flatpak and other containerized app systems, if these are configured. Pamac is often criticized for allowing alternate versions of a given application to be installed, when a preferred version already exists in the official repositories. This can often lead to unexpected results.

Perhaps you should. Of course it’s your system, and you’re free to break it any way you see fit. :slight_smile:

I’m glad you could safely resolve your issue this time.

Cheers.

1 Like
8

Im actually think that pamac (GUI) is doing a much better job as pacman (CLI) when it comes to unexperienced users.

Confusion newcomer with a info that pamac would break your system is not really true.

Depends how you use it… but not automatically.

You can click on the Top right dropdown menu in pamac and select there Refresh Databases… this will also trigger to update everything else (included new Updates).

I also recommend to update mirrors with the following command before you download newest updates:

sudo pacman-mirrors --fasttrack

9

It was a lighthearted comment to add a little humour to the situation. I suppose it was the language difference that let you see it another way. Otherwise, my comments were accurate. Cheers. :wink:

10

you are correct - the doubled yy is a precautionary action - to ensure the databases is pulled from the primary mirror - ideally you use only pacman -Syu.

The long explanation goes as follows:

pacman get the filename to download from the local database

pacman -S firefox

Without the -y argument - technically - pacman loops to next mirror in the list, when the requested package is not available with the first mirror, and in theory the loop continues, until the file is found, or all mirrors has returned 404, in which case the transaction was not succesful.

When pacman is provided the -y argument - it uses a header request to query for the databases Last-Modified timestamp before actually fetching the database.

If/When the timestamp of the local database is newer or equal to the header retrieved the database is deemed up-to-date and therfore not downloaded.

If however the opposite - then the database is downloaded to the system - thus replacing the existing database.

As you can deduct - depending on the timestamps - it may be necessary to force downloading by doubling the -yy.

Technically it should be enough with a a single -y.

The reason the author of pacman-mirrors recommend a doubled -yy, when you rebuild your mirror list - is to be on the safe side to ensure the system operates on the same database as the primary mirror.

The following has been explained 100’s of times over the years both Arch and Manjaro wiki

Warning: When installing packages in Arch, avoid refreshing the package list without upgrading the system (for example, when a package is no longer found in the official repositories). In practice, do not run pacman -Sy package_name instead of pacman -Syu package_name , as this could lead to dependency issues. See System maintenance#Partial upgrades are unsupported and BBS#89328.

– pacman - ArchWiki

At the end of the day - when you have a stable mirror list - all you need to do on a regular base is sync updated packages

sudo pacman -Syu

And when you want to sync new package

sudo pacman -Syu <pkgname>

How often - is a matter of choice - you are the system admin of your system - it is your decision.

6 Likes
11

Thank you for that detailed explanation of what ‘y’ and ‘yy’ does.