Installing Steam makes two xdg start menu desktop launchers pointlessly

I don’t have any problems, but just this UX annoyance for new Steam installation. :smiling_face:


Steam installed through yay steam.

Why when Steam are installed and logged in, I see multiple steam launchers. And the second one doesn’t even work, seems like it is for internal backend use only.

Also why Steam are named Steam (Runtime), if I don’t have any other steam. (Runtime) suffix seems pointless in this case.

It really rings with freaking why!? in LTT Linus voice. :sweat_smile:

I think the sniper one is something to do with proton (may be wrong) but this is how it has always shown on my system but I have it set to a shortcut so rarely see this

Some more information if you want to try make sense of it

2 Likes

In case someone looks for a fix:

Ran

$ rm /home/$USER/.local/share/applications/Steam\ Linux\ Runtime\ 3.0\ \(sniper\).desktop

and then (if you use KDE Plasma)

$ dolphin /home/$USER/.local/share/applications/

right click on steam.desktop → Properties → Application tab → Name: Steam (Runtime) → OK

1 Like

I don’t have this on my system. You might check and see what package owns that second one.

It is because there is also a “Steam (Native)”.

1 Like


It’s Steam proton backend (something like that), which are not supposed to be ran by itself anyways. Installed automatically by Steam, when needed.

Then it would probably make more sense to install steam-native? However, this is not offered for installation with either pacman or yay.

Not unless you need it which most people don’t.

It is called steam-native-runtime

2 Likes

Main sell point of Steam (Native), I heard, are to reduce total system size. But like, cmon, if you preparing to install games, you must have enough space to not worry about few megabibytes.

Steam (Native) are like Steam Beta, but instead of beta version, you get to use libraries which are sometimes newer than Steam program uses and expects (by Valve). And that can introduce bugs (this happens more often) or sometimes fixes bug earlier (which you maybe have in Runtime version overwise), before time that it arrives to more stable - Steam(Runtime). If you don’t have problem, then don’t look for one by starting to use Steam (Native).

Hmm… Maybe it makes sense to run Steam (Native) if you as well run Steam Beta enabled (through settings inside steam).



IMO it never makes sense to install Steam (Native). And Steam (Runtime) should be called Steam, because it’s “the real one”, even pacman package name implies so. Overwise this package would be called steam-runtime-bin.

image

1 Like

I haven’t used it in a long time. However, there was a time when it had advantages when used in a hybrid/optimus laptops and that was the main use case for it.

1 Like

thx for the explanation, that helps to understand :+1:

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.