Steam released an update around the 3rd of December, which prevented Wine from launching it once applied. Fortunately, the Wine devs have released a patch and resolved the bug report in record time to address the issues, and this should be included in the next 1.7.8 release hopefully out this weekend.
More discussion surrounding the issue is available on the Steam appdb entry, as well as this forum thread.
More discussion surrounding the issue is available on the Steam appdb entry, as well as this forum thread.
Some you may have missed, popular articles from the last month:
All posts need to follow our rules. For users logged in: please hit the Report Flag icon on any post that breaks the rules or contains illegal / harmful content. Guest readers can email us for any issues.
Actually, it broke 64-bit wine environments. My 32-bit wine environment still works fine. Unfortunately I have games that only work in one or the other.
0 Likes
If you can't wait for 1.7.8, you can of course compile wine yourself. It isn't actually that hard to do, simply follow these [steps](http://wiki.winehq.org/WineOn64bit).
You can have steam running again in half an hour or less, depending on how fast your machine can compile the code.
You can have steam running again in half an hour or less, depending on how fast your machine can compile the code.
0 Likes
yaourt -S wine-git
0 Likes
This is why i want Native games only for Linux Wine is broken form the start
0 Likes
Wouldn't be the first time I've compiled wine from source if I did. But really I'm not sweating it. I've spent too much time playing RAGE lately and been neglecting my native games. Besides, I have Batman: Arkham City installed in my 32-bit environment and that still works.
0 Likes