Skip to content
New issue

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

Your steam package is out of date. It's not though. #4321

Closed
BryanQuigley opened this issue Feb 16, 2016 · 83 comments
Closed

Your steam package is out of date. It's not though. #4321

BryanQuigley opened this issue Feb 16, 2016 · 83 comments
Assignees
Labels

Comments

@BryanQuigley
Copy link

@BryanQuigley BryanQuigley commented Feb 16, 2016

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.
Press enter to continue:

dpkg -l | grep steam
ii steam-launcher 1.0.0.51

I'm on Ubuntu 16.04 (dev) with latest updates and the nvidia 361.xx series driver.

@bp0
Copy link

@bp0 bp0 commented Feb 19, 2016

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.

@bellini666
Copy link

@bellini666 bellini666 commented Feb 19, 2016

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
@LiamDawe
Copy link
Contributor

@LiamDawe LiamDawe commented Feb 19, 2016

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

@ZeeZeeEff
Copy link

@ZeeZeeEff ZeeZeeEff commented Feb 25, 2016

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

@leinardi
Copy link

@leinardi leinardi commented Feb 27, 2016

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

@luisalvarado
Copy link

@luisalvarado luisalvarado commented Mar 1, 2016

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

@glesima
Copy link

@glesima glesima commented Mar 2, 2016

Same here.

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

@soee
Copy link

@soee soee commented Mar 11, 2016

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

@der-eismann
Copy link

@der-eismann der-eismann commented Mar 11, 2016

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?

@dietrmat
Copy link

@dietrmat dietrmat commented Mar 15, 2016

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

@drohm
Copy link

@drohm drohm commented Mar 27, 2016

Seeing same issue - Xubuntu 16.04 Final Beta.

@rkarolak
Copy link

@rkarolak rkarolak commented Mar 29, 2016

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-Ubuntu SMP Fri Mar 18 19:08:31 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -r
Release:    16.04
@licaon-kter
Copy link

@licaon-kter licaon-kter commented Mar 30, 2016

Yep #747

@Erazor84
Copy link

@Erazor84 Erazor84 commented Mar 31, 2016

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

Ubuntu Mate 16.04 Beta 2
Lastest Nvidia 361.42 Driver

@elbuglione
Copy link

@elbuglione elbuglione commented Apr 1, 2016

Same here.
Ubuntu 16.04 Beta2
Nvidia 361.42

@admshao
Copy link

@admshao admshao commented Apr 8, 2016

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

@swetoast
Copy link

@swetoast swetoast commented Apr 12, 2016

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

@erichoglander
Copy link

@erichoglander erichoglander commented Apr 12, 2016

Confirming
Kubuntu 16.04
Nvidia 361.42

@helicida
Copy link

@helicida helicida commented Apr 13, 2016

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

@Recydywa
Copy link

@Recydywa Recydywa commented Apr 14, 2016

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

@robertgorbul
Copy link

@robertgorbul robertgorbul commented Apr 21, 2016

Ubuntu 16.04 64-bit Final release still same issue

@ghost
Copy link

@ghost ghost commented Apr 21, 2016

Same here with 16.04 final.

@cyberwitch
Copy link

@cyberwitch cyberwitch commented Apr 22, 2016

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.

@Tschrock
Copy link

@Tschrock Tschrock commented Apr 22, 2016

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)

@cyberwitch
Copy link

@cyberwitch cyberwitch commented Apr 22, 2016

Thanks a bunch! That worked for me.

On Thu, Apr 21, 2016 at 8:12 PM Tyler Schrock notifications@github.com
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
#4321 (comment)

@dnlbaines
Copy link

@dnlbaines dnlbaines commented Apr 22, 2016

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.

@ridowan007
Copy link

@ridowan007 ridowan007 commented Apr 22, 2016

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.

@PhoneixS
Copy link

@PhoneixS PhoneixS commented May 15, 2016

@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/.

@terzag
Copy link

@terzag terzag commented May 15, 2016

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...

@robertgorbul
Copy link

@robertgorbul robertgorbul commented May 15, 2016

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

@terzag
Copy link

@terzag terzag commented May 15, 2016

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

@PhoneixS
Copy link

@PhoneixS PhoneixS commented May 15, 2016

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.

@Xavron
Copy link

@Xavron Xavron commented May 20, 2016

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 :-)

@terzag
Copy link

@terzag terzag commented May 20, 2016

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

@Xavron
Copy link

@Xavron Xavron commented May 20, 2016

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 :-)

@terzag
Copy link

@terzag terzag commented May 20, 2016

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.

@Xavron
Copy link

@Xavron Xavron commented May 20, 2016

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

@riking
Copy link

@riking riking commented May 26, 2016

#4321 (comment) was the only solution here that actually resulted in the Steam client's update installing.

@johnv-valve johnv-valve assigned johnv-valve and unassigned Plagman May 26, 2016
@suprovsky
Copy link

@suprovsky suprovsky commented May 28, 2016

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

@samrocketman
Copy link

@samrocketman samrocketman commented May 28, 2016

@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.

@falbani
Copy link

@falbani falbani commented May 30, 2016

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

@magicmyth
Copy link

@magicmyth magicmyth commented Jun 9, 2016

@cpw Thanks for discovering that the issue was with libpcre. I never would have realised that.

Another more elegant (because it will be unaffected by steam updates) method to workaround the libpcre issue is to use:
export LD_PRELOAD="$LD_PRELOAD /lib/x86_64-linux-gnu/libpcre.so.3 /lib/x86_64-linux-gnu/libpcre.so.3.13.2"

You can add that in a couple of places. The simplest is to make a copy of steam.desktop into the /usr/local area so it overrides the package version:

cp /usr/share/applications/steam.desktop /usr/local/share/applications/ sudo editor /usr/local/share/applications/steam.desktop

And under [Desktop Entry] change:
Exec=/usr/bin/steam %U
to
Exec=LD_PRELOAD='/lib/x86_64-linux-gnu/libpcre.so.3 /lib/x86_64-linux-gnu/libpcre.so.3.13.2 '${LD_PRELOAD} /usr/bin/steam %U

You may need to log out then back in for your desktop to start using your own steam.desktop.

Another method which I myself actual use now is to create a shell script at:
/usr/local/bin/steam

With contents like:

#!/bin/bash

# This is a custom steam wrapper to prevent library conflicts

if [[ $EUID -eq 0 ]]; then
   echo "This script must not be run as root" 1>&2
   exit 1
fi

# If you find LD_PRELOAD is not enough to get all games working uncomment below:
#find ~/.steam/root/ \( -name "libgcc_s.so*" -o -name "libstdc++.so*" -o -name "libxcb.so*" \) -print -delete
export LD_PRELOAD='/usr/$LIB/libstdc++.so.6 /lib/x86_64-linux-gnu/libgcc_s.so.1 /lib/i386-linux-gnu/libgcc_s.so.1 /usr/$LIB/libxcb.so.1 /usr/$LIB/libgpg-error.so /usr/$LIB/libasound.so.2 '
# This fixes the "Your system is out of date" message which is caused by
# grep using the library provided by Steam.
# @see https://github.com/ValveSoftware/steam-for-linux/issues/4321#issuecomment-217769283
export LD_PRELOAD="$LD_PRELOAD /lib/x86_64-linux-gnu/libpcre.so.3 /lib/x86_64-linux-gnu/libpcre.so.3.13.2"

exec /usr/bin/steam "$@"

You will still need to make the /usr/local/share/applications/steam.desktop copy and edit its line:
Exec=/usr/bin/steam %U
to
Exec=/usr/local/bin/steam %U
But from that point on any command calls to "steam" will use the custom wrapper.

NOTE: If you are on 32bit you will need to change the libpcre path from /lib/x86_64-linux-gnu/libpcre to /lib/i386-linux-gnu/libpcre

@dennisheitmann
Copy link

@dennisheitmann dennisheitmann commented Jun 12, 2016

@magicmyth Thank you for the custom steam wrapper script!

@BeyondLimitation
Copy link

@BeyondLimitation BeyondLimitation commented Jun 23, 2016

@cpw
Thanks man! I owe u one.

@DoNotSpamPls
Copy link

@DoNotSpamPls DoNotSpamPls commented Jun 28, 2016

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!

@ViBE-HU
Copy link

@ViBE-HU ViBE-HU commented Jun 28, 2016

@DoNotSpamPls lol not.

@DoNotSpamPls
Copy link

@DoNotSpamPls DoNotSpamPls commented Jun 29, 2016

Edited my comment after a test

@pickledMind
Copy link

@pickledMind pickledMind commented Jul 5, 2016

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

@holtrop
Copy link

@holtrop holtrop commented Jul 9, 2016

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

@DoNotSpamPls
Copy link

@DoNotSpamPls DoNotSpamPls commented Jul 11, 2016

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.

@AngryPenguinPL
Copy link

@AngryPenguinPL AngryPenguinPL commented Jul 15, 2016

Yes is fixing now. Thanks.

@NicoHood
Copy link

@NicoHood NicoHood commented Aug 2, 2016

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)

@samrocketman
Copy link

@samrocketman samrocketman commented Aug 2, 2016

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet