Steam fails to launch on unstable #238101
Comments
|
Related to ValveSoftware/steam-for-linux#9321 it seems. |
|
If it's like the previous time, the JS errors were red herrings, and symptoms of the earlier failure. I would hazard a guess that this is the actual cause? But I don't know for sure. |
|
Same version of Steam starts fine here. |
|
So unlike the previous issue, it seems much less universal. As configured in Jovian NixOS, the same version of steam launches fine. I wonder if this would be caused by "impurities" coming from your current desktop environment. Can you share details about your configuration, if not the whole system configuration outright? E.g. the desktop environment in use, the session in use (important for desktops with X11 and wayland support), features enabled like portals and such. |
|
I had xdg-desktop-portal-gnome enabled on my machine and leftover from some testing. I don't actually even use it for anything. I disabled it per suggestions here and in the upstream thread, now steam opens and works fine... |
|
Unsure if its the same issue, but I don't have that gnome portal enabled. Here's my logs: LogYou can find my config here: https://github.com/ashe/dotfiles. When I try opening steam, it just endlessly sits on the 'log in screen' and no further output displays as shown below
|
|
I don't have xdg-desktop-portal-gnome and never had. It doesn't start... update: and Steam started fine - with the new UI, and with the error message about dconf still there! Then I killed Steam, restarted the portals, and it starts fine... |
|
I'm experiencing the same issue on a new install of my NixOS config. Both are on the same rev, yet the old install still works fine while having the same exact configuration. Only the |
|
Short term fix: start steam with |
|
While steam launches perfectly for me, using Proton 8.0+ will lead to various issues like a set of dependencies refusing to install, (e.g. DirectX), and when launching the EA game launcher for NFS Heat, will lead to the same error of: Full CLI output of steam using Proton Experimental launching NFS Heat and getting into the EA launcherI cannot figure out if this is a NixOS issue or a Steam issue. As it seems very irregular and shows up differently for similar installs of Steam. |
FliegendeWurst
added
the
6.topic: steam
|
It's broken for me on Hyprland, getting stuck at "Loading user data", but it's working on KDE Wayland. |
|
I am experiencing a similar issue just after the "loading user data" screen I am greeted with a black box that does nothing. My log shows the same thing. I am also using the hyprland flake.
edit: after killing my xdg portals mine just sits on the "loading user data" seemingly forever |
|
Steam doesn't start for me either since the new client was available, I also use the hyprland flake. The loading screen hangs at "loading user data...". |
|
It seems this also happens in Arch, Fedora, OpenSUSE and KDE Neon: https://github.com/ValveSoftware/steam-for-linux/issues?q=is%3Aissue+-vgui+created%3A%3E%3D2023-06-22 EDIT: For most accurate logs, check |
|
Things are working for me now:
I hope this helps people |
|
@Ashe this solution doesn't work for me, unfortunately |
Following issue NixOS#238101 latest Steam and Proton (8.0+) will frequently crash with a generic "GLib-GObject-CRITICAL". This error message ended up being been a red-herring, and the actual issue lies within the dependency on libnm inside Steam. Fix for now is to use our own system libnm directly for the FHS. Solution originally found in this Arch Linux issue: https://bugs.archlinux.org/task/79006
|
I have a possible fix, and i would love to hear if it helps anyone else. Try the following in your NixOS configuration wherever your steam is set up: programs.steam = {
enable = true;
package = pkgs.steam.override {
extraLibraries = p: with p; [
(lib.getLib networkmanager)
];
};
}; |
|
If you are running an Nvidia graphics card, you can try one of the following workarounds.
|
This worked for me to get steam launched. Currently testing the beta client |
This has no effect for me? Seems like there's nothing to be fetched w/ nix-repl> pkgs = nixosConfigurations.home-desktop.pkgs
nix-repl> lib = inputs.nixpkgs.lib
nix-repl> pkgs.networkmanager
«derivation /nix/store/5cijg04a6ndsh3240ikimbl6fb8bx5yr-networkmanager-1.42.6.drv»
lib.getLib pkgs.networkmanager
«derivation /nix/store/5cijg04a6ndsh3240ikimbl6fb8bx5yr-networkmanager-1.42.6.drv»Edit: Nor can I see any |
Seems to start Steam for me, but no games are launchable, even w/graphics card offloading. |
|
Yeah the But nixpkgs is currently on |
|
For reference, there is an update to |
|
@x10an14 That didn't work for me, is there something I'm missing here? |
@samueldr This seems to be an impurity. It vanishes on my system if I use For me the root cause seems to be in So this might be a duplicate of #234839, so please check your coredumpctl database if in doubt. |
Not AFAIK, but I guess there are more variables to this than I'm aware/this thread has managed to "lock down"? |
|
I ran into this issue a few weeks ago, and at the time, running After reboot today, I'm experience the exact same problem again, and nothing seams to get steam working, not the -vgui, not the -no-cef-sandbox, not deleting nvidia cache, not deleting steam packages |
|
I just got steam working again. I had to |
Steam permanently stuck on "Loading user data" screen |
|
I rebooted and ran |
I'm having the exact same problem but only while in Wayland. If I open Steam on X11 it works fine. |
|
Indications are the nvidia bug is fixed with 535.95... whenever it shows up. 535.98 was merged into master three days ago, so hopefully soon? |
|
I’m having the same issue, on wayland (sway) and a AMD GPU. None of the workarounds listed in this thread are working for me, and if I run steam in a X11 session, it works without problem. |
|
@vegaelle what desktop environment, and do you know if you have XDG portals working? And can you confirm if you've tried (I'm running Sway and have been finding Steam pretty seamless other than needing to do |
|
I'm running sway with xdg-desktop-portal-wlr and xdg-desktop-portal-gtk (working fine), have an nvidia card with 535.104, on linux 6.5.1. I tried all of the above solutions (deleting nvidia cache, trying I would try steam beta to check if this is a steam issue, but I can't actually get into steam to change over unfortunately. |
|
Now, after running I'm running latest unstable, using the official hyprland flake and most wayland related derivations are being pulled from But when finished loading Steam appeared as an unresponsive transparent window. |
Are you able to open it from a terminal? This is currently how I am launching steam from hyprland. If I do that it works. edit: this no longer works for me either |
@justinrubek sadly that makes no difference. :/ Il fact this time I don't even get pass the "Loading user data..." screen. |
|
Launching steam in latest hyprland, using nixpkgs-wayland and steam beta I've got this far:
I can even open games by right-clicking the steam applet on the top right corner... I also have to launch steam with the |
|
Don't know if this is a potential fix, but disabling the steam gamescope session had fixed this issue for me |
|
How do you do it? As far as i understand it, gamescope is a compositor made for steamdeck |
You can actually disable it via options with I've tried this and so far got no luck with it. |
|
I also get stuck on "loading user data" when using the Flatpak version but only under wayland (Hyprland). |
|
I ran into this today and I'm not really sure that what I found is related to what other people were seeing. Here's my troubleshooting steps and what I did to fix it. How I Fixed ItI ran Steam from the terminal and saw that nothing appeared besides these lines repeating: Saw the following in one of the Steam logs that @PedroHLC mentioned: Ending up pondering the orb for a bit and then decided to check Got me thinking what package provides Seeing this line in the rebuilding of my Realized that I was using chaotic = {
mesa-git = {
enable = true;
fallbackSpecialisation = false;
method = "replaceRuntimeDependencies";
};
};Rebuilt my system with Now steam runs fine from the terminal and I'm able to log in. RamblingIt kind of got me thinking: since it started working once I forced (I guess that's what the I tried to use Anyways, searching for One could force usage of the This would cause quite a number of packages to be rebuilt though. I did try and set the following, but it didn't end up fixing Steam not launching. I would say, if you are running into the above problems, try and see if you are pulling multiple versions of |
Sorry about that, most apps work flawlessly with my libgbm-rename approach, but Firefox wrapper and all the DMs adds mesa to either LD_PRELOAD or LD_LIBRARY_PATH, even though both works without this at all, and breaks my hack. @K900 has a good solution for this though, one day we won't need my hack at all for all mesa versions to seamlessly talk with each other. FFx wrapper is absurd, it adds a bunch of stuff when only dbus and gstreamer stuff are required for our built-in-house browser. Probably some approach to use pre-compiled browsers and code-sharing between chrome and firefox. Meanwhile, DMs do the best they can to guarantee X11 will start in all distros, even though that's not the best approach for Nix. Steam will work flawlessly with the mesaa-git pure approach when running directly from a tty (with gamescope), and if you start your DE directly from tty too. Watch out for gamescope's capSysNice option, that breaks randomly. |
I might be mistaken but doesn't |
|
I fixed Steam being transparent for me in Hyprland by disabling hw accel as listed here hyprwm/Hyprland#4173 (comment) |
|
I'm running into a similar problem, for me of the workarounds suggested here they sometimes work, but it is so inconsistent I can't be certain. Workarounds I tried:
Log: |
|
This issue has become a complete mess because I'm pretty sure there's like twenty different issues combined here. I'm going to close this, and please file new issues for anything you still experience. |
and others
Describe the bug
Steam takes a long time to start and ends up crashing after 30-45 seconds. I initially thought this was related to #236561 but I upgraded to latest unstable (this fix is merged into it) and the issue persists. I'm thinking it may have to do with the new UI redesign since there are JS engine errors?
Additional context
Log:
Notify maintainers
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"and paste the result.The text was updated successfully, but these errors were encountered: