Is anyone else having issues with the 4/22 Steam update? I could launch games fine this morning (with the overlay disabled), updated to the 4/22 update, and now when I launch a game through the client, it doesn't launch.
I updated WINE to 1.7.17 (32 bit) in case my older version was causing problems. Same issue.
Here's the console dump: http://pastebin.com/d3g3i3hu
I switched the default from XP to Windows 7, no change.
I tried launching a game I know works without Steam (AI War), so it isn't the game. (It's happening with all games, as well.)
ETA: I found I can launch any game successfully if I'm in offline mode. If I'm online, it won't launch anything but the Steam client. I minimized the Steam client, and now I'm unable to launch anything again.
It seems to work only if I start the steam client in online mode, restart in offline mode, then launch a game. As soon as I close or minimize the steam client, it stops launching games. If I try to launch a game via the taskbar, it'll also fail, and I won't be able to launch a game via the client either. (Until I log in online, restart the client in offline mode.)
(Slackware 14-64 bit (multilib enabled), 3.2.39 kernel, 4.7.1 gcc)
4/22 Steam update
Re: 4/22 Steam update
And with today's update, it loaded games once, then same behaviour as yesterday.
ETA: I tried a clean wine prefix, no change.
Anyone have any ideas?
ETA: I tried a clean wine prefix, no change.
Anyone have any ideas?
Re: 4/22 Steam update
And as a further update, it sometimes loads games and sometimes doesn't.
Bug report it?
Bug report it?
Re: 4/22 Steam update
I just updated to 1.7.17 and don't seem to have any problems other than a vrserver.exe process that spawns and usually crashes. Running 32 bit though, and there was another steam update today.
edit: tried to play a game and got a crash after 5 or 10 minutes. maybe spoke too soon. :-/
e2: scratch that, I think this crash is the same as the overlay bug but it worked before. who knows.
edit: tried to play a game and got a crash after 5 or 10 minutes. maybe spoke too soon. :-/
e2: scratch that, I think this crash is the same as the overlay bug but it worked before. who knows.