Also with Ubuntu 16.04 and nvidia-358, steam-launcher 1.0.0.51.
When Steam is launched an xterm is opened with that message about the package being out of date. If you quit Steam before closing the xterm window, Steam will restart after the xterm window is closed.

I'm experiencing the same on Debian Testing.

apt-cache policy steam-launcher                      hackedbellini@slayer
steam-launcher:
  Installed: 1.0.0.51
  Candidate: 1.0.0.51
  Version table:
 *** 1.0.0.51 500
        500 http://repo.steampowered.com/steam precise/steam amd64 Packages
        500 http://repo.steampowered.com/steam precise/steam i386 Packages
        100 /var/lib/dpkg/status

Yeah, same on Ubuntu 16.04 thought I was going mad :P

Hey guys,

same message for me on Ubuntu 16.04 but on stable Ubuntu the message went away after update

dpkg -l | grep steam ii steam-launcher 1.0.0.51

Same here. Ubuntu 16.04 and nvidia-358, steam-launcher 1.0.0.51.

Same here. Ubuntu 16.04 64-bit. Nvidia 358.16. steam-launcher 1.0.0.51

Same here.

steam-launcher 1.0.0.51
Ubuntu 16.04
Kernel: 4.4.0-8-generic
Nvidia 361.28

Confirmed on Kubuntu 16.04
Plasma 5.5.5
Frameworks 5.18
QT 5.5.1
Kernel 4.4.0-11
64bit

So I guess it is somehow related to the "new-ness" of Ubuntu 16.04. I have the same problem with Xubuntu 16.04 and kernel 4.4.0-11.

Could a developer look into this?

Also affected on 16.04: http://paste.ubuntu.com/15394943/

Seeing same issue - Xubuntu 16.04 Final Beta.

Likewise on my machine, which I recently installed the latest build of 16.04. I'm assuming that it's due to the new release of Ubuntu. Being that it's not officially released / stable maybe Steam doesn't recognize the distribution which prompts this error? It seems to work find otherwise.

$ uname -a
Linux link-lxub1604 4.4.0-15-generic [#31](/issue/ValveSoftware/steam-for-linux/31)-Ubuntu SMP Fri Mar 18 19:08:31 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -r
Release:    16.04

Yep https://github.com/ValveSoftware/steam-for-linux/issues/747

Same error, even after the Steam Package Update last night.

Ubuntu Mate 16.04 Beta 2
Lastest Nvidia 361.42 Driver

Same here.
Ubuntu 16.04 Beta2
Nvidia 361.42

Just upgrade to 16.04. Same for me with nvidia-364

Same here
xubuntu 16.04 (amd64)
Graphics: Intel Graphics Drivers 1.4.0
Kernel: 4.6.0-040600rc2-generic

Confirming
Kubuntu 16.04
Nvidia 361.42

Same here, Ubuntu 16.04 Beta 2 - GTX 950 with nvidia 361.42 drivers.

I'm also affected by this issue and at least two other people reported it on Ubuntu Forums.

http://ubuntuforums.org/showthread.php?t=2313587

Ubuntu 16.04 64-bit Final release still same issue

Same here with 16.04 final.

On 16.04 final, I installed the latest steam from steam's repo (1.0.0.52). However, Ubuntu thinks that it's repo has a newer version (1:1.0.0.48-1ubuntu3) and keeps trying to get me to "upgrade." Steam itself is still showing the popup, too.

Update: Scratch that, I didn't realize steam no longer uses a package called steam, and only needs steam-launcher, which isn't in any Ubuntu repository, so no more apt conflict after I uninstalled steam and left steam-launcher. Still getting the popup from Steam itself though.

I was able to 'fix' this by uninstalling steam and removing the steampowered.com repo and then reinstalling from ubuntu's multiverse repo (deb http://us.archive.ubuntu.com/ubuntu/ xenial multiverse)

Thanks a bunch! That worked for me.

On Thu, Apr 21, 2016 at 8:12 PM Tyler Schrock [email protected]
wrote:

I was able to 'fix' this by uninstalling steam and removing the
steampowered.com repo and then reinstalling from ubuntu's multiverse repo
(deb http://us.archive.ubuntu.com/ubuntu/ xenial multiverse)

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/4321#issuecomment-213225201

Just upgraded, seems like this is going to be an issue for anyone who upgrades to 16.04. Hope there will be an easy fix that doesn't involve reinstalling Steam.

Kubuntu 16.04, updated from 14.04, seeing this problem. Each time at startup, steam warns about
"Your steam package is out of date. Please get an updated version from your package provider or directly from http://repo.steampowered.com/steam for supported distributions."

Already removed and reinstalled from main steam site.

@ridowan007 Like @Tschrock suggested, the fix seems to be to uninstall Steam's steam and steam-launcher, remove Steam's repo, and finally install just steam from Ubuntu's multiverse repository. For whatever reason, the version in Steam's repo is actually borked on 16.04, but Ubuntu's official package works.

I just updated from 14.04 to 16.04 and there are no steam packages in my multiverse repo. Anyone have a clue about this?!

I couldn't see the steam package in synaptic for some reason, but if I ran
"sudo apt-get install steam" it would install steam.

On Fri, Apr 22, 2016, 2:32 PM ghephardo [email protected] wrote:

I just updated from 14.04 to 16.04 and there are no steam packages in my
multiverse repo. Anyone have a clue about this?!

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/4321#issuecomment-213594754

It's a steam:i386 package, so if you do
apt install steam it will install. If you look in Software or Synaptic it won't show up :/

This is (AFAICT) an older version of the steam-launcher in multiverse. Somewhat funny, but it did work for me, although have to redownload games...

Yes, you might want to backup save files from ~/.steam since not all games
save to the cloud.

On Fri, Apr 22, 2016 at 2:34 PM BryanQuigley [email protected]
wrote:

It's a steam:i386 package, so if you do
apt install steam it will install. If you look in Software or Synaptic it
won't show up :/

This is (AFAICT) an older version of the steam-launcher in multiverse.
Somewhat funny, but it did work for me, although have to redownload games...

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/4321#issuecomment-213595332

You could just move your games from ~/.local/share/Steam/steamapps to ~/.steam/steamapps

Oh, and you can move any local folders at ~/.local/share/Steam/userdata///local to ~/.steam/userdata///local to restore your local saves! Guess they weren't lost either ^^

I had the same issue, and solved as follows:

1. Got to Ubuntu Software and find steam.
2. Uninstall it.
3. Install it again from the same location.
4. Run steam to update (there may be no steam in the application list, so just type in terminal "steam")
5. Copy games and configuration of Your profile:
   5a. games:
   ~/.local/share/Steam/steamapps to ~/.steam/steamapps
   5b. profile settings:
   ~/.local/share/Steam/userdata to ~/.steam/userdata

Given that Steam updates itself and shouldn't care about the original installation version/method, it's a bit weird that this shows up. I wonder what it checks to decide that it's out of date. Is the term window with the message displayed by the Steam client itself or from outside (e.g. a shell script that launches the client, checks some version number and displays the term window)?

I traced through to where the message is coming from.

In ~/.steam/root/steam.sh, find MINIMUM_VERSION
In /usr/bin/steam, find STEAMSCRIPT_VERSION
MINIMUM_VERSION must be less than STEAMSCRIPT_VERSION (uses Bash's "if [[ A -lt B ]]" )
If it is not, then the message in steam.sh is displayed in that xterm window:
Warning: Your steam package is out of date. Please get an updated version from your package provider or directly from http://repo.steampowered.com/steam for supported distributions.

Strangely, for me, MINIMUM_VERSION is 100020, and STEAMSCRIPT_VERSION is 100052. And in my testing, the versions are compared successfully. I've tried altering steam.sh, but it gets repaired every time Steam is run. I don't know how the version comparison is failing when I run Steam.

Same here.
Ubuntu 16.04 LTS (64 bit)
kernel 4.4.0-21-generic
steam-runtime-release_2016-02-23
nvidia 361.42
steam-launcher 1.0.0.51

im install steam -> https://steamcdn-a.akamaihd.net/client/installer/steam.deb

See Tyler Schrock's comment previously in this thread. You should not have
steam-launcher installed at all, you should remove the steam repository,
and make sure the version of steam you have installed is steam:i386 from
Ububntu's multiverse repository.

On Sun, Apr 24, 2016 at 3:49 AM Tuomas Lähteenmäki [email protected]
wrote:

Same here.
Ubuntu 16.04 LTS (64 bit)
kernel 4.4.0-21-generic
steam-runtime-release_2016-02-23
nvidia 361.42
steam-launcher 1.0.0.51

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/4321#issuecomment-213935359

I can confirm that doing what @cyberwitch explained in the previous post worked for me. Thanks!

this help
sudo add-apt-repository "deb http://us.archive.ubuntu.com/ubuntu/ xenial multiverse"
sudo apt-get update && sudo apt-get install steam

I need a lot of convincing before I mess with my steam install... I'd rather this was just fixed.

as for "I was able to 'fix' this by uninstalling steam and removing the steampowered.com repo and then reinstalling from ubuntu's multiverse repo (deb http://us.archive.ubuntu.com/ubuntu/ xenial multiverse)" I'm not even sure what that means.

Linux distributions usually install software through repositories ("repos"), i.e. places where packages are stored and installed/updated on demand. Each distribution has its own repositories organization; on Ubuntu, the principal repos are named main, universe, multiverse and restricted, depending on the type of packages you find in them (e.g. free vs proprietary software, or software managed by Canonical vs by the community).

When you install Steam through the deb package downloaded on its official website, it adds a repo from Valve to your system, so it can update the package easily if needed. But Steam is also available on Ubuntu through the multiverse repo, withouth having to install it from the official deb package. There's a small issue, though: both version seem to install Steam files in different places; the one from Valve's deb uses ~/.local/share/Steam while the one from the Ubuntu repo uses ~/.steam.

So, if you installed Steam from Valve's deb, you have the issue mentioned in this bug report (window with version mismatch error message); if you installed it from the Ubuntu's repo, you dont. Thus, the solution is simple:

1. remove the Steam package that was installed by the deb (it's called "steam-launcher"); you can do it from the terminal with sudo apt-get remove steam-launcher

2. remove the Steam repository that was added by the deb; you can do it through the "Software & Updates" (not sure of the proper english name, my system is in french) option in the system prefs. There, you'll have a first tab that lists the Ubuntu repos, multiverse should be checked by default (and the others too, don't uncheck anything). Then, you'll have a tab for other software: find the two lines that begin with "http://repo.steampowered.com" and uncheck/delete them. When you close Software & Updates after this, it'll ask you if you want to reload the sources; do it.

3. now that Valve's repo and Steam have been removed, you can reinstall it from the Ubuntu multiverse repo. In a terminal: sudo apt-get install steam

4. I said above that the two versions of Steam don't use the same places for the files, so don't launch Steam now or it won't find you installed games because it doesn't search for them in the right place. Instead, open a Nautilus (file manager) window and show hidden files (ctrl + H), you'll see (among others) two folders that begin with a dot: ".steam" and ".local". Go into ".local", then "share", then "Steam". You'll see two folders of interest: "steamapps" (your games) and "userdata" (your personal data, like games config files or screenshots and such). Move these two folders into the ".steam" one you saw previously in your home folder.

5. launch Steam and you should have your installed games as before and you should get rid of the annoying terminal windows that appeared previously.

Why steam has its own repository or why steam pages has a steam.deb package? If it does not work. Why then the site is not updated. This problem would not have if the valve should be updated pages.

Confirmed on Ubuntu 16.04

i7-2760QM, Intel HD3000/Quadro 1000M

Seems to be resolved by @terzag's solution

$HOME/.steam/steam/steam.sh or $HOME/.local/share/Steam/steam.sh is getting run twice. The first time around, check_scriptversion() and detect_scriptversion() return the correct Steam version, 100052, and STEAMSCRIPT_OUTOFDATE gets set to 0. However, steam.sh gets run a second time, and this time, for whatever reason, detect_scriptversion() returns a 0, which is obviously less than the 100020 that it's checking against.

In steam.sh, line 576 reads:
if [ "$INITIAL_LAUNCH" ]; then

Just before that, INITIAL_LAUNCH is set to either true or false (the strings, not the values).

Unless $INITIAL_LAUNCH is empty, the [ "$INITIAL_LAUNCH" ] will always return true. [ "" ] will always return false. I'd suggest the if statement on line 576 be changed to if $INITIAL_LAUNCH; then, so it will actually run the true and false commands in the path, get their respective returns, and skip that buggy second version evaluation.

I'd test this directly in the steam.sh, myself, but whenever I make any changes there, it fails the hash check, and is replaced.

edit: I take that back. While this would work for this instance, there is still the issue of the INITIAL_LAUNCH check in function reset_steam(). It checks whether or not INITIAL_LAUNCH is an empty string, using that as the flag. If it's empty, INITIAL_LAUNCH is equivalent to false. Otherwise it's true. Which means line 576 could be the way it was, if [ "$INITIAL_LAUNCH" ]; then, but up a few lines, 568, INITIAL_LAUNCH=false should probably be INITIAL_LAUNCH='' or INITIAL_LAUNCH="". This way, it fixes the secondary launching of steam.sh, and still allows function reset_steam() to work as-written.

@Angsereg
Nice work, man!

@johndrinkwater @johnv-valve
VALVe plz... FIX IT

The problem is actually that the "libpcre" library used by debian's grep is no longer 100% compatible with the version shipping inside the steam "mini-distro".

rm ~/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/lib/x86_64-linux-gnu/libpcre.so.3
rm ~/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/lib/x86_64-linux-gnu/libpcre.so.3.12.1

Will fix the problem, by forcing the steam mini-distro to use the libpcre from the system (3.13.1). The annoying popup will no longer happen (but if you re-install steam because of an update, you'll have to do this again)

@cpw Thanks, that worked!

Wouldn't it be possible to create a symlink (owned by root) to the system version of libpcre, so Steam can't recreate these outdated version?

@CreamyCookie, no, steam moves the entire steam runtime folder out of the way and unpacks a new steam runtime on any steam client update that changes the steam runtime.

(Edited for clarity)

@Tele42 But when Steam is doing normal updates it isn't running as root, so it can't overwrite or move files / symlinks created by root, or do I misunderstand how Linux file access rights work?

@CreamyCookie you can test the claim yourself:

1. create a folder with your regular non-root user
2. in that folder, as root, create a symlink to something
3. as your regular user rename the folder
4. create the folder again as your regular user

There should be no permission violations in that sequence.

May be just update libpcre?

Em sex, 13 de mai de 2016 10:51, CreamyCookie [email protected]
escreveu:

@Tele42 https://github.com/Tele42 But when Steam is doing normal
updates it isn't running as root, so it can't overwrite files / symlinks
created by root, or do I misunderstand how Linux file access rights work?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/4321#issuecomment-219048666

Sent from my Android

@Tele42 Oops. Well, I probably should have RTFM.

@mhalano That would get overwritten by Steam as well though.

@CreamyCookie I'm thinking for ways to fix the bug. Not just to do a
workaround. You got it?

Em sex, 13 de mai de 2016 às 12:49, CreamyCookie [email protected]
escreveu:

@Tele42 https://github.com/Tele42 Oops. Well, I probably should have
RTFM.

@mhalano https://github.com/mhalano That would get overwritten by Steam
as well though.

—
You are receiving this because you were mentioned.

Reply to this email directly or view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/4321#issuecomment-219082749

Sent from my Android

@mhalano I didn't know you work at Valve.

Of course the package should be updated if it's causing the issue.

@CreamCookie I don't work at Valve (I wish :), but I think we should help
who works there to fix this bug fastest as possible. Probably all the
workarounds we can think will become useless after a Steam update because
the integrity checks.

Em sex, 13 de mai de 2016 às 14:10, CreamyCookie [email protected]
escreveu:

@mhalano https://github.com/mhalano I didn't know you work at Valve.

Of course the package should be updated if it's causing the issue.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/4321#issuecomment-219103035

Sent from my Android

@terzag I used your comment and it work but you said "Move these two folders into the ".steam" one you saw previously in your home folder." when for me I needed to move the folders to .steam/steam/.

That's possible, I haven't checked (I use the package from Valve, not the one from the Ubuntu repos). I only detailed what people explained above. That's a bit odd, though, as @rgiyf, @cyberwitch and @inadril all talked about putting them directly in .steam...

@terzag because package from Ubuntu repo installs steam to ~/.steam and from valve to ~/.local/share/Steam

That's what I thought but @PhoenixS seems to say that it's ~/.steam/steam on his/her system instead.

Yes, it's what I said. First I copied them to ~/.steam but weren't detected, moved it to ~/.steam/steam and steam recognizes them. So if other people have the same problem can try it.

I have Ubuntu 16.04.

Its funny, the entire time from the daily's till today, I didn't think of just removing xterm which is popping up the message. If your not using xterm (you don't open it ever, then your not using it):

sudo apt-get remove --purge xterm

...and goodbye silly popup in just a few seconds :-)

Sure, but it's only hiding the problem rather than fixing it...

Nothing here fixes it. Only Valve can do that, but at least I won't ever see it again and I don't use xterm anyway. So don't care if its just hidden - its better and that was the problem imo.

Do what you will, I'm just throwing that out there AND I'd rather remove xterm then jump through all this stuff. Download this and remove that... blah :-)

Removing libpcre from the Steam Runtime fixes the problem. See @cpw message above (11 days ago).

The Steam Runtime is a mess anyway, you already have to remove libs in some cases (like when using the Mesa graphic driver). It's only one more lib to remove than usual until Valve fixes the issue properly.

Yet, you have to keep doing it after every update. Give me a break man.

https://github.com/ValveSoftware/steam-for-linux/issues/4321#issuecomment-215679452 was the only solution here that actually resulted in the Steam client's update installing.

Removing libpcre is not working for me.
I'm Using Gentoo x64.

@cpw how did you figure out to remove libpcre? Did you use strace, ldd, grep and other wizardry? I'm curious what your process was.

@cpw What kind of magic you used to figure that out? Genius!

@magicmyth Thank you for the custom steam wrapper script!

@cpw
Thanks man! I owe u one.

I have found an easier way that doesn't require you to do any hard work.
It's very simple - just switch to the Steam Beta release channel. After that the messages will stop.
After that you can simply revert to the normal builds to get the latest non-beta build.

EDIT: Reverting to the official build brings the problem back!

@DoNotSpamPls lol not.

Edited my comment after a test

I really liked @DoNotSpamPls solution. It was really quick and easy.

I got a Steam update this morning that finally seems to have fixed this issue with Ubuntu 16.04.

After testing, it's confirmed that this issue is fixed. You can fix it for yourself by updating your Steam client.
Please close the issue.

Yes is fixing now. Thanks.

I just tried to install steam on an ubuntu 14.04 based system. I tried the software center version and the deb package of the website but both do not work. It searches for updates, tries to download but it will not download a single byte from the server. Any ideas how to solve this?

Edit: waiting a looong time solved it. (With the .deb from the website)

@NicoHood your question seems completely unrelated to this issue. I recommend finding a relevant open issue or opening a new issue.