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

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

Comments

Projects
None yet
@BryanQuigley

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

This comment has been minimized.

Show comment
Hide comment
@bp0

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

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.

@hackedbellini

This comment has been minimized.

Show comment
Hide comment
@hackedbellini

hackedbellini 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

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

This comment has been minimized.

Show comment
Hide comment
@LiamDawe

LiamDawe Feb 19, 2016

Contributor

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

Contributor

LiamDawe commented Feb 19, 2016

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

@ZeeZeeEff

This comment has been minimized.

Show comment
Hide comment
@ZeeZeeEff

ZeeZeeEff 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

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

This comment has been minimized.

Show comment
Hide comment
@leinardi

leinardi Feb 27, 2016

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

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

@luisalvarado

This comment has been minimized.

Show comment
Hide comment
@luisalvarado

luisalvarado Mar 1, 2016

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

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

@glesima

This comment has been minimized.

Show comment
Hide comment
@glesima

glesima Mar 2, 2016

Same here.

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

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

This comment has been minimized.

Show comment
Hide comment
@soee

soee 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

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

This comment has been minimized.

Show comment
Hide comment
@der-eismann

der-eismann 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?

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

This comment has been minimized.

Show comment
Hide comment

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

@drohm

This comment has been minimized.

Show comment
Hide comment
@drohm

drohm Mar 27, 2016

Seeing same issue - Xubuntu 16.04 Final Beta.

drohm commented Mar 27, 2016

Seeing same issue - Xubuntu 16.04 Final Beta.

@rkarolak

This comment has been minimized.

Show comment
Hide comment
@rkarolak

rkarolak 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

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

This comment has been minimized.

Show comment
Hide comment

Yep #747

@Erazor84

This comment has been minimized.

Show comment
Hide comment
@Erazor84

Erazor84 Mar 31, 2016

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

Ubuntu Mate 16.04 Beta 2
Lastest Nvidia 361.42 Driver

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

Ubuntu Mate 16.04 Beta 2
Lastest Nvidia 361.42 Driver

@elbuglione

This comment has been minimized.

Show comment
Hide comment
@elbuglione

elbuglione Apr 1, 2016

Same here.
Ubuntu 16.04 Beta2
Nvidia 361.42

Same here.
Ubuntu 16.04 Beta2
Nvidia 361.42

@admshao

This comment has been minimized.

Show comment
Hide comment
@admshao

admshao Apr 8, 2016

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

admshao commented Apr 8, 2016

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

@swetoast

This comment has been minimized.

Show comment
Hide comment
@swetoast

swetoast Apr 12, 2016

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

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

@erichoglander

This comment has been minimized.

Show comment
Hide comment
@erichoglander

erichoglander Apr 12, 2016

Confirming
Kubuntu 16.04
Nvidia 361.42

Confirming
Kubuntu 16.04
Nvidia 361.42

@helicida

This comment has been minimized.

Show comment
Hide comment
@helicida

helicida Apr 13, 2016

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

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

@Recydywa

This comment has been minimized.

Show comment
Hide comment
@Recydywa

Recydywa 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

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

@rgiyf

This comment has been minimized.

Show comment
Hide comment
@rgiyf

rgiyf Apr 21, 2016

Ubuntu 16.04 64-bit Final release still same issue

rgiyf commented Apr 21, 2016

Ubuntu 16.04 64-bit Final release still same issue

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Apr 21, 2016

Same here with 16.04 final.

ghost commented Apr 21, 2016

Same here with 16.04 final.

@cyberwitch

This comment has been minimized.

Show comment
Hide comment
@cyberwitch

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

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

This comment has been minimized.

Show comment
Hide comment
@Tschrock

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

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

This comment has been minimized.

Show comment
Hide comment
@cyberwitch

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

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

This comment has been minimized.

Show comment
Hide comment
@dnlbaines

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

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

This comment has been minimized.

Show comment
Hide comment
@ridowan007

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

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.

@cyberwitch

This comment has been minimized.

Show comment
Hide comment
@cyberwitch

cyberwitch Apr 22, 2016

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

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

@ghephardo

This comment has been minimized.

Show comment
Hide comment
@ghephardo

ghephardo Apr 22, 2016

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 just updated from 14.04 to 16.04 and there are no steam packages in my multiverse repo. Anyone have a clue about this?!

@cyberwitch

This comment has been minimized.

Show comment
Hide comment
@cyberwitch

cyberwitch Apr 22, 2016

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 notifications@github.com 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
#4321 (comment)

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 notifications@github.com 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
#4321 (comment)

@BryanQuigley

This comment has been minimized.

Show comment
Hide comment
@BryanQuigley

BryanQuigley Apr 22, 2016

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

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

@cyberwitch

This comment has been minimized.

Show comment
Hide comment
@cyberwitch

cyberwitch Apr 22, 2016

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 notifications@github.com
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
#4321 (comment)

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 notifications@github.com
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
#4321 (comment)

@rgiyf

This comment has been minimized.

Show comment
Hide comment
@rgiyf

rgiyf Apr 22, 2016

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

rgiyf commented Apr 22, 2016

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

@cyberwitch

This comment has been minimized.

Show comment
Hide comment
@cyberwitch

cyberwitch Apr 22, 2016

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

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

@inadril

This comment has been minimized.

Show comment
Hide comment
@inadril

inadril Apr 23, 2016

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

inadril commented Apr 23, 2016

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

This comment has been minimized.

Show comment
Hide comment
@terzag

terzag Apr 23, 2016

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

terzag commented Apr 23, 2016

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

@pgn674

This comment has been minimized.

Show comment
Hide comment
@pgn674

pgn674 Apr 24, 2016

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.

pgn674 commented Apr 24, 2016

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.

@cpw

This comment has been minimized.

Show comment
Hide comment
@cpw

cpw May 9, 2016

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 commented May 9, 2016

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)

@CreamyCookie

This comment has been minimized.

Show comment
Hide comment
@CreamyCookie

CreamyCookie May 13, 2016

@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 commented May 13, 2016

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

@Tele42

This comment has been minimized.

Show comment
Hide comment
@Tele42

Tele42 May 13, 2016

@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 commented May 13, 2016

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

@CreamyCookie

This comment has been minimized.

Show comment
Hide comment
@CreamyCookie

CreamyCookie May 13, 2016

@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 commented May 13, 2016

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

@Tele42

This comment has been minimized.

Show comment
Hide comment
@Tele42

Tele42 May 13, 2016

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

Tele42 commented May 13, 2016

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

@mhalano

This comment has been minimized.

Show comment
Hide comment
@mhalano

mhalano May 13, 2016

May be just update libpcre?

Em sex, 13 de mai de 2016 10:51, CreamyCookie notifications@github.com
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
#4321 (comment)

Sent from my Android

mhalano commented May 13, 2016

May be just update libpcre?

Em sex, 13 de mai de 2016 10:51, CreamyCookie notifications@github.com
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
#4321 (comment)

Sent from my Android

@CreamyCookie

This comment has been minimized.

Show comment
Hide comment
@CreamyCookie

CreamyCookie May 13, 2016

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

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

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

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

@mhalano

This comment has been minimized.

Show comment
Hide comment
@mhalano

mhalano May 13, 2016

@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 notifications@github.com
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
#4321 (comment)

Sent from my Android

mhalano commented May 13, 2016

@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 notifications@github.com
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
#4321 (comment)

Sent from my Android

@CreamyCookie

This comment has been minimized.

Show comment
Hide comment
@CreamyCookie

CreamyCookie May 13, 2016

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

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

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

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

@mhalano

This comment has been minimized.

Show comment
Hide comment
@mhalano

mhalano May 13, 2016

@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 notifications@github.com
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
#4321 (comment)

Sent from my Android

mhalano commented May 13, 2016

@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 notifications@github.com
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
#4321 (comment)

Sent from my Android

@PhoneixS

This comment has been minimized.

Show comment
Hide comment
@PhoneixS

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

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

This comment has been minimized.

Show comment
Hide comment
@terzag

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

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

@rgiyf

This comment has been minimized.

Show comment
Hide comment
@rgiyf

rgiyf May 15, 2016

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

rgiyf commented May 15, 2016

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

@terzag

This comment has been minimized.

Show comment
Hide comment
@terzag

terzag May 15, 2016

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

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

This comment has been minimized.

Show comment
Hide comment
@PhoneixS

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

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

This comment has been minimized.

Show comment
Hide comment
@Xavron

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

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

This comment has been minimized.

Show comment
Hide comment
@terzag

terzag May 20, 2016

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

terzag commented May 20, 2016

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

@Xavron

This comment has been minimized.

Show comment
Hide comment
@Xavron

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

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

This comment has been minimized.

Show comment
Hide comment
@terzag

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

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

This comment has been minimized.

Show comment
Hide comment
@Xavron

Xavron May 20, 2016

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

Xavron commented May 20, 2016

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

@riking

This comment has been minimized.

Show comment
Hide comment
@riking

riking May 26, 2016

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

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

This comment has been minimized.

Show comment
Hide comment
@suprovsky

suprovsky May 28, 2016

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

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

@samrocketman

This comment has been minimized.

Show comment
Hide comment
@samrocketman

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

@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

This comment has been minimized.

Show comment
Hide comment
@falbani

falbani May 30, 2016

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

falbani commented May 30, 2016

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

@magicmyth

This comment has been minimized.

Show comment
Hide comment
@magicmyth

magicmyth 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

@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

This comment has been minimized.

Show comment
Hide comment
@dennisheitmann

dennisheitmann Jun 12, 2016

@magicmyth Thank you for the custom steam wrapper script!

dennisheitmann commented Jun 12, 2016

@magicmyth Thank you for the custom steam wrapper script!

@BeyondLimitation

This comment has been minimized.

Show comment
Hide comment
@BeyondLimitation

BeyondLimitation Jun 23, 2016

@cpw
Thanks man! I owe u one.

@cpw
Thanks man! I owe u one.

@DoNotSpamPls

This comment has been minimized.

Show comment
Hide comment
@DoNotSpamPls

DoNotSpamPls 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!

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

This comment has been minimized.

Show comment
Hide comment

ViBE-HU commented Jun 28, 2016

@DoNotSpamPls lol not.

@DoNotSpamPls

This comment has been minimized.

Show comment
Hide comment
@DoNotSpamPls

DoNotSpamPls Jun 29, 2016

Edited my comment after a test

Edited my comment after a test

@pickledMind

This comment has been minimized.

Show comment
Hide comment
@pickledMind

pickledMind Jul 5, 2016

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

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

@holtrop

This comment has been minimized.

Show comment
Hide comment
@holtrop

holtrop Jul 9, 2016

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

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

This comment has been minimized.

Show comment
Hide comment
@DoNotSpamPls

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

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

This comment has been minimized.

Show comment
Hide comment
@AngryPenguinPL

AngryPenguinPL Jul 15, 2016

Yes is fixing now. Thanks.

Yes is fixing now. Thanks.

@NicoHood

This comment has been minimized.

Show comment
Hide comment
@NicoHood

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

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

This comment has been minimized.

Show comment
Hide comment
@samrocketman

samrocketman Aug 2, 2016

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

@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