Steam issues after latest update

Questions about Wine on macOS.
Locked
paulthetall
Level 2
Level 2
Posts: 41
Joined: Wed Oct 20, 2010 5:36 am

Steam issues after latest update

Post by paulthetall »

Steam was always working well, untill the latest update. It crashes instantly. When you do a new wineprefix of latest wine and or winetrick it or do the latest download when you start it it will try updating but will fail. Can some people look into this? Check it out yourself. I heard many people about it, but I am stunned there was still no forumpost about it.
gypsyotoko
Newbie
Newbie
Posts: 4
Joined: Mon Feb 18, 2013 7:46 am

Re: Steam issues after latest update

Post by gypsyotoko »

I can confirm that Steam does not work using the following hardware/OS combinations:

Symptoms:
Running Steam from wine results in an endless update loop where the Steam update is downloaded, extracted, installed and then the updater crashes with an error message reading; "Failed to remove temporary unzip folder, conti".

However, by pressing Cancel at the proper time, or by running the Steam.exe.old executable that exists in the /Program Files/Steam folder upon failure to update, Steam will bring up the initial login/sign up window, however none of its contents will be drawn. (A black background window only shows.) Tabbing through allows the user to operate the window, but I've been unsuccessful in figuring out where I would need to send focus in order to login.

Tested Using
OS: OS X 10.8.2
Hardware: MacBook 5,1 (late 2008)
CPU: Intel Core 2 Duo 2.4 Ghz
Graphics: NVIDIA GeForce 9400M

Wine Version: both 1.4.1 and 1.5.24 using default wine prefix
gypsyotoko
Newbie
Newbie
Posts: 4
Joined: Mon Feb 18, 2013 7:46 am

Re: Steam issues after latest update

Post by gypsyotoko »

I've filed a bug for this (infinite update loop): 33014
Nekto
Newbie
Newbie
Posts: 1
Joined: Thu Feb 28, 2013 3:43 am

Re: Steam issues after latest update

Post by Nekto »

gypsyotoko
Newbie
Newbie
Posts: 4
Joined: Mon Feb 18, 2013 7:46 am

Re: Steam issues after latest update

Post by gypsyotoko »

Yep, fixed in the latest dev build.

Thanks!
Locked