Jump to content

  • Log in with Facebook Log in with Twitter Log In with Google      Sign In   
  • Create Account

Steam's Recent Update Problem


  • Please log in to reply
13 replies to this topic

#1 HyperTsunaz

HyperTsunaz

    Professional Member

  • Members
  • PipPipPipPip
  • 172 posts
  • LocationSingapore
  • Graphics Card:Intel HD Graphics 3000 384 MB
  • Operating System:OS X 10.9 (Mavericks)
  • I like to play:FPS, adventure, action and strategy games.
    I'm on Steam, Origin and UPlay.

Posted 16 February 2013 - 02:12 AM

I've had reports of an update loop with steam with my Dota 2 wrapper so i decided to make an entirely plain wrapper and test steam. The problem occurred again in the new plain wrapper. Did the newest Steam update break something or what?


Port Link in the Port Database:

My Mac OS X Version:

OS X 10.8.2 (12C60)

My Mac Model, GPU & CPU:
MacBook Pro 13-inch, Late 2011

2.4 GHz Intel Core i5

4 GB 1333 MHz DDR3

Intel HD Graphics 3000 384 MB

Error Log(s):

Last run wine
Spoiler


#2 GameGuy

GameGuy

    Legendary Member

  • Members
  • 2,127 posts
  • LocationCanada...Eh
  • Graphics Card:nVidia 9400m 256mb
    ATI Radeon HD 6950 2GB
    MSI N670GTX PW/OCE 2GB SLI
  • Operating System:Mac OS X 10.7 (Lion)
  • I like to play:RPG, Racing, and of course FPS

Posted 16 February 2013 - 04:16 AM

Which update there has been one everyday for the past 3 days.

Posted Image
Macbook Pro: Intel C2D 2.53ghz, 4GB Ram, Nvidia 9400m 256MB

Hackintosh: Intel i5-3570k, 16GB Ram, Asus Z77 Sabertooth, MSI GTX 670 Power Edition SLI
If my post helped you hit the like button :)


#3 zoroaster

zoroaster

    Professional Member

  • Members
  • PipPipPipPip
  • 143 posts

Posted 16 February 2013 - 11:12 PM

A simple and clean solution for the latest Steam update bug in Wine(skin) should be the following. But be aware that if you do it wrong then you will destroy more than you repair!

Run your wrapper at least until the installation completes with the "Failed" error once (to download all needed zip files). Then open Terminal.app and type:

cd Applications/Wineskin/<your wrapper>/drive_c/Program\ Files/Steam/package/tmp/
for I in ../*.zip.*; do unzip $I; done # This will unzip installation files in tmp folder
# When asked if you want to override always select "A(ll)"
# Now you are prepared and you can overwrite the old Steam installation with:
rsync -Hav . ../../

When you start your wrapper the first time it will repeat the installation and will "fail" again, but it should not loop anymore because you had already installed the latest Steam version manually.

#4 HyperTsunaz

HyperTsunaz

    Professional Member

  • Members
  • PipPipPipPip
  • 172 posts
  • LocationSingapore
  • Graphics Card:Intel HD Graphics 3000 384 MB
  • Operating System:OS X 10.9 (Mavericks)
  • I like to play:FPS, adventure, action and strategy games.
    I'm on Steam, Origin and UPlay.

Posted 17 February 2013 - 12:19 AM

So this must be done for every new wrapper made in the future?

#5 zoroaster

zoroaster

    Professional Member

  • Members
  • PipPipPipPip
  • 143 posts

Posted 17 February 2013 - 12:42 AM

 HyperTsunaz, on 17 February 2013 - 12:19 AM, said:

So this must be done for every new wrapper made in the future?

For now until the problem is fixed.

#6 ValkTuna

ValkTuna

    Imitator, Intimidator, Stimulator, Simulator of Data, Eliminator

  • Members
  • 770 posts
  • LocationIn the deep dark depths of the earth... :P
  • Graphics Card:nVidia GeForce 320M 256MB.
  • Operating System:OS X 10.9 (Mavericks)
  • I like to play:SMITE, LoL, and other games that catch my attention. Usually a wide range of genres.

Posted 23 February 2013 - 04:01 PM

 zoroaster, on 16 February 2013 - 11:12 PM, said:

A simple and clean solution for the latest Steam update bug in Wine(skin) should be the following. But be aware that if you do it wrong then you will destroy more than you repair!

Run your wrapper at least until the installation completes with the "Failed" error once (to download all needed zip files). Then open Terminal.app and type:

cd Applications/Wineskin/<your wrapper>/drive_c/Program\ Files/Steam/package/tmp/
for I in ../*.zip.*; do unzip $I; done # This will unzip installation files in tmp folder
# When asked if you want to override always select "A(ll)"
# Now you are prepared and you can overwrite the old Steam installation with:
rsync -Hav . ../../
So I just copy and paste the code into Terminal?
I don't get how to type the second line.
And the third.
Posted Image
Main banner thanks to RazorPro
Avatar thanks to adini

I don't have anything else to say, I guess.

#7 HyperTsunaz

HyperTsunaz

    Professional Member

  • Members
  • PipPipPipPip
  • 172 posts
  • LocationSingapore
  • Graphics Card:Intel HD Graphics 3000 384 MB
  • Operating System:OS X 10.9 (Mavericks)
  • I like to play:FPS, adventure, action and strategy games.
    I'm on Steam, Origin and UPlay.

Posted 24 February 2013 - 12:41 AM

Just press enter after typing every line and do not copy # and the words after it on the same line.

#8 ValkTuna

ValkTuna

    Imitator, Intimidator, Stimulator, Simulator of Data, Eliminator

  • Members
  • 770 posts
  • LocationIn the deep dark depths of the earth... :P
  • Graphics Card:nVidia GeForce 320M 256MB.
  • Operating System:OS X 10.9 (Mavericks)
  • I like to play:SMITE, LoL, and other games that catch my attention. Usually a wide range of genres.

Posted 24 February 2013 - 05:13 AM

Alright, awesome, it works. :D
Posted Image
Main banner thanks to RazorPro
Avatar thanks to adini

I don't have anything else to say, I guess.

#9 zoroaster

zoroaster

    Professional Member

  • Members
  • PipPipPipPip
  • 143 posts

Posted 26 February 2013 - 06:54 PM

 SouthTuna, on 23 February 2013 - 04:01 PM, said:

So I just copy and paste the code into Terminal?
I don't get how to type the second line.
And the third.

You can copy the code 1:1 into Terminal.app (except "<your wrapper>" must be changed).
The only important thing is to make sure that at the end of each line is a line break or you must copy each line separately.
If you type # in the Terminal.app it will do nothing because the shell recognises everything after # on the same line as comment.

#10 zoroaster

zoroaster

    Professional Member

  • Members
  • PipPipPipPip
  • 143 posts

Posted 02 March 2013 - 12:22 AM

If it is true the above mentioned Steam bug 33014 is fixed in Wine 1.5.25.

#11 Topsy Cret

Topsy Cret

    Lurker

  • Members
  • 2 posts
  • Graphics Card:NVIDIA GeForce 320M 256MB
  • Operating System:Mac OS X 10.7 (Lion)

Posted 05 March 2013 - 09:32 AM

It looks like it might be a while before they release the engine download for 1.5.25. Is there another way to obtain it?

#12 ValkTuna

ValkTuna

    Imitator, Intimidator, Stimulator, Simulator of Data, Eliminator

  • Members
  • 770 posts
  • LocationIn the deep dark depths of the earth... :P
  • Graphics Card:nVidia GeForce 320M 256MB.
  • Operating System:OS X 10.9 (Mavericks)
  • I like to play:SMITE, LoL, and other games that catch my attention. Usually a wide range of genres.

Posted 05 March 2013 - 11:25 AM

 Topsy Cret, on 05 March 2013 - 09:32 AM, said:

It looks like it might be a while before they release the engine download for 1.5.25. Is there another way to obtain it?

Download the source, extract it and build it using Wineskin.
Posted Image
Main banner thanks to RazorPro
Avatar thanks to adini

I don't have anything else to say, I guess.

#13 saSHguitAR

saSHguitAR

    Lurker

  • Members
  • 1 posts
  • Graphics Card:Nvidia 320M
  • Operating System:Mac OS X 10.6 (Snow Leopard)

Posted 13 March 2013 - 03:45 PM

Hi, i have the same problem but when  I type in your command line(s) it says " -bash: syntax error near unexpected token `do' "

Can someone pls help me ?

thx

#14 HyperTsunaz

HyperTsunaz

    Professional Member

  • Members
  • PipPipPipPip
  • 172 posts
  • LocationSingapore
  • Graphics Card:Intel HD Graphics 3000 384 MB
  • Operating System:OS X 10.9 (Mavericks)
  • I like to play:FPS, adventure, action and strategy games.
    I'm on Steam, Origin and UPlay.

Posted 21 March 2013 - 05:33 AM

Some say the new WS9Wine1.5.25 engines have this fixed. Is it true?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users