[Bug]: Steam Login Problems - Tracking Issue #41
Labels
bug
Something isn't working
Comments
|
The |
|
I've been trying many different conditions for a whole day: game-porting-toolkit from both brew and Whisky, with or without E-sync, Windows 7 or Windows 10, with or without I also tried launching a pre-login steam from my old CrossOver bottle, this time I can login, of course, but all pages - store, library, etc. are empty. From the logs, I also got all those errors above. Chromium just won't work on my computer with wine-7.7. Additionally, the same errors also appear on CrossOver 22.1.1 (with wine-7.7), when I tested it last month. However, it was fixed in the nightly builds of CrossOver 23, which bundles wine-8.0.1. Full log |
IsaacMarovitz
changed the title
IsaacMarovitz
changed the title
|
Yeah, this is the issue I was having. I’ll report here if I find any workarounds, other than using my older CrossOver prefix. |
|
Aha, well this explains that then. |
|
I am able to execute steam with command |
|
I somehow get it to work using the wine binary from the game-porting-toolkit. I execute it many time, and suddenly the login window has everything rendered correctly. This the debug log of wine, if it helps? |
|
New workaround... I copied from and now I'm logged in |
|
Nice, that lets me log in, but all the steam pages are blank (so I cant see my games list/download anything). The Steam logs (steamui_html.txt) are full of |
|
Nice workaround, the remaining issues stem from config differences between CrossOver and Whisky's bottles which is next on my list to address. CrossOver makes several registry modifications and installs the CoreFonts dependency. List of CrossOver's Registry Changes:
|
|
If you just want to download and play games but steam is blank, going to view -> small mode will make games installable and playable through steam. |
|
How do you select "small mode", there's no "view" menu option for me only "Steam, Edit, Window" and the blank login window with an exit "x" as the only thing. |
The "view" menu option is in Steam, and only appeared after you successfully entered the library. 
|
|
Steam seem working perfectly fine until got upgrade to |
|
@Naozumi520 Ah makes sense, i don't even get that much content, my window is just completely empty: |
|
Yeah I can see you're encountering the login issue, not the library issue. In this case, I would recommend you follow @playfulpigeon's solution:
from This worked for me. |
|
@Naozumi520 this worked for me, i now get the steam windows to show up, but then it's still dying on me |
|
|
|
|
Whisky itself generates pretty strange logs. On first run of Steam it can not find multiple .plist files. On second run it prints only @Naozumi520's both solutions works for me |
Here to confirm that a combination of both of @playfulpigeon's config files copy workaround plus @ajkolstad's "small view" workaround fixes the "Blank Screen" when opening steam.exe from Whiskey release pre-0.2.3 |
|
any news about a solution instead of this workarounds? |
Working on it |
|
For what it's worth, I had Steam running using the above workarounds, but unfortunately, since yesterday's big update, it now crashes at boot with a "program error" in 
|
Shit, I didn't expect the beta to become the default so quickly. Yeah, in my experience, the new UI is even worse in Wine than the current. We might end up having to wait for CodeWeavers to update their Steam CrossTie before we can get this properly working then. |
|
Curious - what is whisky doing differently to the vanilla Game Porting Toolkit (which seems to work fine)? |
The latest master /w Steam installed via CrossOver and then imported into Whisky is working fine so I think I should be able to get it working by next release. |
|
Fix being pushed as we speak |
|
thank you! |
|
I'm stuck on the steamwebhelper crash with Whiskey and direct with the Gaming Toolkit. I wonder if something there changed? |
|
The Steam UI works now, but none of my games actually work - they try and open and get killed a split second later. Latest everything/sonoma. Is there some way to know the games are definitely loading with GPT and not the vanilla version of wine (e.g. are they maybe starting without the graphics/DX support?). It "feels" like the games can't see a graphics card. |
|
Just wondering if I'm missing some steps:
Does the copy paste trick work with the new Steam? |
|
The whisky readme explicitly says not to manually install GPT 🤔 |
|
That’s interesting because the FAQ says to sarcastically use the GPTK Readme. |
|
On second thought, maybe it really meant it. It would be helpful for new folks to be pointed to the Wiki. That’s the same process I did anyways. The issue seems to stem from the recent steam update. |
|
Also facing the same issue. On a fresh bottle and install of steam, steam keeps crashing with the same error as @JeanMertz (#41 (comment)). It could definitely be due to the new Steam update. |
|
@rdevathu - are you on Sonoma by any chance? I'm on latest Ventura. |
|
@blisstik I'm also on the latest Ventura. |
|
Facing the same issue, steamwebhelper.exe is now keep crashing |
|
UPD: Found the list of compatible games |
|
|
|
@U5KUN I encountered the same issue, but I managed to resolve it by accident, following these steps: Close all Wine-related processes from the Activity Monitor. This solved my problem with Steamwebhelper constantly crashing. I'm not sure which step is essential, but this worked for me.😀 |
|
@UnpxreTW |
|
@U5KUN Basically, I used the above ones listed😅 But feel free to try all the combinations. |
|
I'm getting the error with the constantly crashing |
Running steam with the arguments |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
This is similar, but not the same as #40. In this instance, text does display correctly in installers and bundled apps, but the Steam login view fails to display. This again comes down to a matter of configuration. CrossOver circumvents this using their CrossTie system, which includes a number of dependency and registry fixes to get Steam working as intended. To properly resolve this issue, we will need to implement a similar system.
For now, there are a number of ways to help alleviate this problem. Some people have found success with the
-noreactloginor-gamepaduilaunch arguments. Sometimes with enough luck and trial and error, you can get it working.The text was updated successfully, but these errors were encountered: