starcraft66
commented
1 year ago Related to https://github.com/ValveSoftware/steam-for-linux/issues/9321 it seems.
Closed starcraft66 closed 1 month ago
starcraft66
commented
1 year ago Related to https://github.com/ValveSoftware/steam-for-linux/issues/9321 it seems.
samueldr
commented
1 year ago 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?
/nix/store/fac4mci5szyhvjwziqln1c8z4lyzc0z2-dconf-0.40.0-lib/lib/gio/modules/libdconfsettings.so: wrong ELF class: ELFCLASS64
Failed to load module: /nix/store/fac4mci5szyhvjwziqln1c8z4lyzc0z2-dconf-0.40.0-lib/lib/gio/modules/libdconfsettings.soBut I don't know for sure.
K900
commented
1 year ago Same version of Steam starts fine here.
samueldr
commented
1 year ago 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.
starcraft66
commented
1 year ago 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...
Ashe
commented
1 year ago Unsure if its the same issue, but I don't have that gnome portal enabled. Here's my logs:
You 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
n3oney
commented
1 year ago I don't have xdg-desktop-portal-gnome and never had. It doesn't start...
update: I'm using hyprland. I ran:
systemctl --user stop xdg-desktop-portal-hyprland
systemctl --user stop xdg-desktop-portaland 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... Even managed to start it with OBS recording it using a portal.
bddvlpr
commented
1 year ago 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 .local/share/Steam folder is persisted.
Ashe
commented
1 year ago Short term fix: start steam with steam -vgui works for me
soupglasses
commented
1 year ago 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:
(process:57874): GLib-GObject-CRITICAL **: 02:41:10.794: g_object_unref: assertion 'G_IS_OBJECT (object)' failedI 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.
ShaddyDC
commented
1 year ago It's broken for me on Hyprland, getting stuck at "Loading user data", but it's working on KDE Wayland.
I'm using the official Hyprland flake, and I've got pkgs.xdg-desktop-portal-gtk enabled, although removing that doesn't seem to fix it. Some games like Cyberpunk are also currently broken for me on Hyprland, giving only a black screen, while working fine on KDE, which may or may not be related.
LegitCamper
commented
1 year ago 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.
(process:57874): GLib-GObject-CRITICAL **: 02:41:10.794: g_object_unref: assertion 'G_IS_OBJECT (object)' failededit: after killing my xdg portals mine just sits on the "loading user data" seemingly forever
geri1701
commented
1 year ago 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...".
(steam:19686): GLib-GObject-CRITICAL **: 08:51:07.862: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
PedroHLC
commented
1 year ago 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 ~/.local/share/Steam/logs/steamwebhelper.log.
Ashe
commented
1 year ago Things are working for me now:
steam -vgui to open steam with old UII hope this helps people
Tony-Klink
commented
1 year ago @Ashe this solution doesn't work for me, unfortunately
soupglasses
commented
1 year ago 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.
~/.cache/nvidia/GLCache.GPU-accelerated web rendering inside of Steam while using -vgui until next steam update.
GiggleSquid
commented
1 year ago If you are running an Nvidia graphics card, you can try one of the following workarounds.
* Delete Nvidia Cache `~/.cache/nvidia/GLCache`.
This worked for me to get steam launched. Currently testing the beta client
x10an14
commented
1 year ago @soupglasses
programs.steam = { enable = true; package = pkgs.steam.override { extraLibraries = p: with p; [ (lib.getLib networkmanager) ]; }; };
This has no effect for me? Seems like there's nothing to be fetched w/getLib...
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 lib outputs on pkgs.networkmanager inside of nixpkgs source, but I may be missing something.
x10an14
commented
1 year ago Short term fix: start steam with
steam -vguiworks for me
Seems to start Steam for me, but no games are launchable, even w/graphics card offloading.
soupglasses
commented
1 year ago Yeah the networkmanager seems to be a dead end, and was a fix to libgudev 238, by pulling in libnm.so that i found on ArchLinux Bug tracker: https://bugs.archlinux.org/task/79006
But nixpkgs is currently on 237 so it likely doesn't do much.
soupglasses
commented
1 year ago For reference, there is an update to libgudev 238 in nixpkgs here: #241939 but it shouldn't give the issue as seen in Arch, since our FHS does not pull in libgudev anywhere.
x10an14
commented
1 year ago With a nix flake update to nixpkgs df1eee2aa65052a18121ed4971081576b25d6b5c, it works for me today. No other diffs in my nixos config.
fr33zing
commented
1 year ago @x10an14 That didn't work for me, is there something I'm missing here?
nix flake update nixpkgs
sudo nixos-rebuild switch
FlorianFranzen
commented
1 year ago 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?
/nix/store/fac4mci5szyhvjwziqln1c8z4lyzc0z2-dconf-0.40.0-lib/lib/gio/modules/libdconfsettings.so: wrong ELF class: ELFCLASS64 Failed to load module: /nix/store/fac4mci5szyhvjwziqln1c8z4lyzc0z2-dconf-0.40.0-lib/lib/gio/modules/libdconfsettings.so@samueldr This seems to be an impurity. It vanishes on my system if I use
nix-shell --pure -p steam --command steaminstead. And it does not fix the crash.
For me the root cause seems to be in ~/.local/share/Steam/ubuntu12_32/gldriverquery. At least coredumpctl reports a segmentation fault for the time of the steam crash. However the stack is empty or unrecoverable, so I will need to investigate further what causes this crash. But given the name it is not far fetch that this is a library that initializes the OpenGL context.
So this might be a duplicate of #234839, so please check your coredumpctl database if in doubt.
$ coredumpctl debug 64223
PID: 64223 (gldriverquery)
UID: 1000 (florian)
GID: 100 (users)
Signal: 11 (SEGV)
Timestamp: Mon 2023-07-17 16:42:00 CEST (14min ago)
Command Line: /home/florian/.local/share/Steam/ubuntu12_32/../ubuntu12_32/gldriverquery
Executable: /home/florian/.local/share/Steam/ubuntu12_32/gldriverquery
Control Group: /user.slice/user-1000.slice/session-2.scope
Unit: session-2.scope
Slice: user-1000.slice
Session: 2
Owner UID: 1000 (florian)
Boot ID: xxxx
Machine ID: xxx
Hostname: fawkes
Storage: /var/lib/systemd/coredump/core.gldriverquery.1000.xxx.64223.1689604920000000.zst (present)
Size on Disk: 2.0M
Message: Process 64223 (gldriverquery) of user 1000 dumped core.
Module /nix/store/3gxzaxslqa0b8daf6z2n9q5f0syyg2iv-gcc-12.3.0-lib/lib/libstdc++.so.6.0.30 without build-id.
Module /nix/store/rvp2sl6m2i02nnds3d8c6qqxsyb58har-libdrm-2.4.115/lib/libdrm_nouveau.so.2.0.0 without build-id.
Module /nix/store/rvp2sl6m2i02nnds3d8c6qqxsyb58har-libdrm-2.4.115/lib/libdrm_amdgpu.so.1.0.0 without build-id.
Module /nix/store/059cgjv5dn8c26vmzshc67jps6ydjl76-libelf-0.8.13/lib/libelf.so.0.8.13 without build-id.
Module /nix/store/rvp2sl6m2i02nnds3d8c6qqxsyb58har-libdrm-2.4.115/lib/libdrm_radeon.so.1.0.1 without build-id.
Module /nix/store/08wksi9sizlmjsw65qzadc8qfpglv2wk-zlib-1.2.13/lib/libz.so.1.2.13 without build-id.
Module /nix/store/hr3s74sdy5fxccc0i8h11s20mml8l0cv-gcc-12.3.0-libgcc/lib/libgcc_s.so.1 without build-id.
Module /nix/store/mvs1j26yjz15ngh9h94aabj2616br1wi-libxshmfence-1.3/lib/libxshmfence.so.1.0.0 without build-id.
Module /nix/store/a1s3wwl920y782fkzpdbw9lnl47wnypk-libxcb-1.14/lib/libxcb-sync.so.1.0.0 without build-id.
Module /nix/store/a1s3wwl920y782fkzpdbw9lnl47wnypk-libxcb-1.14/lib/libxcb-present.so.0.0.0 without build-id.
Module /nix/store/a1s3wwl920y782fkzpdbw9lnl47wnypk-libxcb-1.14/lib/libxcb-dri3.so.0.0.0 without build-id.
Module /nix/store/rvp2sl6m2i02nnds3d8c6qqxsyb58har-libdrm-2.4.115/lib/libdrm.so.2.4.0 without build-id.
Module /nix/store/a1s3wwl920y782fkzpdbw9lnl47wnypk-libxcb-1.14/lib/libxcb-xfixes.so.0.0.0 without build-id.
Module /nix/store/a1s3wwl920y782fkzpdbw9lnl47wnypk-libxcb-1.14/lib/libxcb-randr.so.0.1.0 without build-id.
Module /nix/store/a1s3wwl920y782fkzpdbw9lnl47wnypk-libxcb-1.14/lib/libxcb-dri2.so.0.0.0 without build-id.
Module /nix/store/3mhb0mx8w8jyjljabywfhwcmnvn20935-libX11-1.8.4/lib/libX11-xcb.so.1.0.0 without build-id.
Module /nix/store/2lbxhcsbz43ywcbdyl47s8aihxds6zpx-expat-2.5.0/lib/libexpat.so.1.8.10 without build-id.
Module /nix/store/k8czbc0b4j3vg1k7pbkbdcb8y7d3hsm1-libglvnd-1.6.0/lib/libEGL.so.1.1.0 without build-id.
Module /nix/store/k8czbc0b4j3vg1k7pbkbdcb8y7d3hsm1-libglvnd-1.6.0/lib/libGLdispatch.so.0.0.0 without build-id.
Module /nix/store/k8czbc0b4j3vg1k7pbkbdcb8y7d3hsm1-libglvnd-1.6.0/lib/libGLX.so.0.0.0 without build-id.
Module /nix/store/k8czbc0b4j3vg1k7pbkbdcb8y7d3hsm1-libglvnd-1.6.0/lib/libGL.so.1.7.0 without build-id.
Module /nix/store/6hd9gsmz5fw48b1ryvqd445z00px666n-libxkbcommon-1.5.0/lib/libxkbcommon.so.0.0.0 without build-id.
Module /nix/store/2j99z7hk0a1p1l8wjs4ll8pwvm3jg2mz-libgpg-error-1.47/lib/libgpg-error.so.0.34.0 without build-id.
Module /nix/store/ykm2814i2ra8jwsblw67qpls66dv2ybm-libgcrypt-1.10.2/lib/libgcrypt.so.20.4.2 without build-id.
Module /nix/store/3b1kvypbar8nfnni4b949y3i6b34698n-libcap-2.69-lib/lib/libcap.so.2.69 without build-id.
Module /nix/store/410cjrblagp3kbzlfwn6qxxn5m663jg5-systemd-253.3/lib/libsystemd.so.0.36.0 without build-id.
Module /nix/store/aggw665npzgcfrnp0srmm7lyy5hya57z-dbus-1.14.6-lib/lib/libdbus-1.so.3.32.2 without build-id.
Module /nix/store/cs1p4byq52xaqvnf912bjlpc4cxmll6m-libXrender-0.9.10/lib/libXrender.so.1.3.0 without build-id.
Module /nix/store/a1s3wwl920y782fkzpdbw9lnl47wnypk-libxcb-1.14/lib/libxcb.so.1.1.0 without build-id.
Module /nix/store/x1pfvif5cxbfxy6mj2lzhr1c2vinb7s7-libXrandr-1.5.2/lib/libXrandr.so.2.2.0 without build-id.
Module /nix/store/vv7g4d53wqh86di4i877n36w8w33y649-libXi-1.8/lib/libXi.so.6.1.0 without build-id.
Module /nix/store/3mhb0mx8w8jyjljabywfhwcmnvn20935-libX11-1.8.4/lib/libX11.so.6.4.0 without build-id.
Module /nix/store/zbsxdxs1zccp2dn3qd11h5bi7y1awhly-SDL2-2.26.5/lib/libSDL2-2.0.so.0.2600.5 without build-id.
Module /nix/store/zr88kdbgs2ldcjvmddqpbb6lc125daci-libXScrnSaver-1.2.3/lib/libXss.so.1.0.0 without build-id.
Module /nix/store/yfjklw2l07rhwjxlk872r8yg14kd1yq0-libXfixes-6.0.0/lib/libXfixes.so.3.1.0 without build-id.
Module /nix/store/102kdpmi4nbrkqkbzvwmr1g42izw2j0c-libXcursor-1.2.0/lib/libXcursor.so.1.0.2 without build-id.
Module /nix/store/k3ddh0qfwzj5rr0kfb1c0041fy5lj5kr-libXext-1.3.4/lib/libXext.so.6.4.0 without build-id.
Module libncursesw.so.6 without build-id.
Module libsensors.so.5 without build-id.
Module libdecor-0.so.0 without build-id.
Module libffi.so.8 without build-id.
Module liblz4.so.1 without build-id.
Module libzstd.so.1 without build-id.
Module liblzma.so.5 without build-id.
Stack trace of thread 64223:
#0 0x0000000000000000 n/a (n/a + 0x0)
ELF object binary architecture: Intel 80386@x10an14 That didn't work for me, is there something I'm missing here?
nix flake update nixpkgs sudo nixos-rebuild switch
Not AFAIK, but I guess there are more variables to this than I'm aware/this thread has managed to "lock down"?
dmayle
commented
1 year ago I ran into this issue a few weeks ago, and at the time, running steam -no-cef-sandbox once caused steam to start, and after that I could just run regular steam.
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
dmayle
commented
1 year ago I just got steam working again. I had to pkill steam, then I was able to run steam --reset, and after rebooting steam would launch again
Tony-Klink
commented
1 year ago I just got steam working again. I had to pkill steam, then I was able to run steam --reset, and after rebooting steam would launch again
Steam permanently stuck on "Loading user data" screen
colemickens
commented
1 year ago I rebooted and ran steam --reset and that fixed me up. Thanks @dmayle for suggesting it.
SrEstegosaurio
commented
1 year ago Unsure if its the same issue, but I don't have that gnome portal enabled. Here's my logs:
Log You 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'm having the exact same problem but only while in Wayland. If I open Steam on X11 it works fine. The funniest part about that is that I'm usign the flatpak version. If trying to launch Steam from nixpkgs I don't get to see a window. Even more, I cannot close it. I can close the terminal from which I've launched it and still not closed.
Baughn
commented
1 year ago 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?
vegaelle
commented
1 year ago 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.
colemickens
commented
1 year ago @vegaelle what desktop environment, and do you know if you have XDG portals working? And can you confirm if you've tried steam --reset?
(I'm running Sway and have been finding Steam pretty seamless other than needing to do steam --reset once. )
dryya
commented
1 year ago 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 -vgui, and get stuck on steam actually opening (so thus far the furthest I've gotten is "loading user data" after steam --reset.)
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.
SrEstegosaurio
commented
1 year ago Now, after running steam --reset I've managed to pass the "loading user data" screen on Hyprland, using xdg-desktop-portal-hyprland and xdg-desktop-portal-gtk.
I'm running latest unstable, using the official hyprland flake and most wayland related derivations are being pulled from nixpkgs-wayland.
But when finished loading Steam appeared as an unresponsive transparent window.
justinrubek
commented
1 year ago Now, after running
steam --resetI've managed to pass the "loading user data" screen on Hyprland, usingxdg-desktop-portal-hyprlandandxdg-desktop-portal-gtk.I'm running latest unstable, using the official hyprland flake and most wayland related derivations are being pulled from
nixpkgs-wayland.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
SrEstegosaurio
commented
1 year ago 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.
@justinrubek sadly that makes no difference. :/
Il fact this time I don't even get pass the "Loading user data..." screen.
SrEstegosaurio
commented
1 year ago 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 --reset flag.
Dekomoro
commented
1 year ago Don't know if this is a potential fix, but disabling the steam gamescope session had fixed this issue for me
vegaelle
commented
1 year ago How do you do it? As far as i understand it, gamescope is a compositor made for steamdeck
SrEstegosaurio
commented
1 year ago 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 programs.steam.gamescopeSession.enable.
I've tried this and so far got no luck with it.
SrEstegosaurio
commented
1 year ago I also get stuck on "loading user data" when using the Flatpak version but only under wayland (Hyprland).
dmizelle
commented
12 months ago 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.
I ran Steam from the terminal and saw that nothing appeared besides these lines repeating:
steamwebhelper.sh[209006]: Runtime for steamwebhelper: defaulting to /home/devon/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
steamwebhelper.sh[209006]: glibc >= 2.34, partially disabling sandbox until CEF supports clone3()
steamwebhelper.sh[209190]: Runtime for steamwebhelper: defaulting to /home/devon/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
steamwebhelper.sh[209190]: glibc >= 2.34, partially disabling sandbox until CEF supports clone3()
steamwebhelper.sh[209376]: Runtime for steamwebhelper: defaulting to /home/devon/.local/share/Steam/ubuntu12_64/steam-runtime-heavy
steamwebhelper.sh[209376]: glibc >= 2.34, partially disabling sandbox until CEF supports clone3()
Saw the following in one of the Steam logs that @PedroHLC mentioned:
$ tail -f ~/.steam/root/logs/steamwebhelper.log
[1111/154330.691524:WARNING:gpu_process_host.cc(1256)] The GPU process has crashed 2 time(s)
[1111/154330.692974:INFO:crash_reporting.cc(271)] Crash reporting enabled for process: gpu-process
Cannot upload crash dump: cannot exec /usr/bin/wget
Unexpected crash report id length
Failed to get crash dump id.
Report Id:
[1111/154330.999616:WARNING:gpu_process_host.cc(1256)] The GPU process has crashed 3 time(s)
[1111/154331.001181:INFO:crash_reporting.cc(271)] Crash reporting enabled for process: gpu-process
[1111/154331.011927:WARNING:gpu_process_host.cc(984)] Reinitialized the GPU process after a crash. The reported initialization time was 10 ms
/home/devon/.local/share/Steam/ubuntu12_64/steamwebhelper: /home/devon/.local/share/Steam/ubuntu12_64/steam-runtime-heavy/lib/x86_64-linux-gnu/libselinux.so.1: no version information available (required by /lib64/libgio-2.0.so.0)
[1111/154331.056497:WARNING:crash_reporting.cc(287)] Failed to set crash key: UserID with value: 0
[1111/154331.056546:WARNING:crash_reporting.cc(287)] Failed to set crash key: BuildID with value: 1698777785
[1111/154331.056549:WARNING:crash_reporting.cc(287)] Failed to set crash key: SteamUniverse with value: Public
[1111/154331.056552:WARNING:crash_reporting.cc(287)] Failed to set crash key: Vendor with value: Valve
[1111/154331.056555:WARNING:crash_reporting.cc(287)] Failed to set crash key: Platform with value: Linux
[1111/154331.057277:INFO:crash_reporting.cc(248)] Crash reporting enabled for process: utility
[1111/154331.212749:INFO:crash_reporting.cc(271)] Crash reporting enabled for process: renderer
Cannot upload crash dump: cannot exec /usr/bin/wget
Unexpected crash report id length
Failed to get crash dump id.
Report Id:Ending up pondering the orb for a bit and then decided to check dmesg to see any reports of segfaulting:
$ sudo dmesg -T | tail -n 5
[Sat Nov 11 15:46:05 2023] traps: steamwebhelper[211571] general protection fault ip:7f6bc2f63582 sp:7ffc3e862030 error:0 in libglapi.so.0.0.0[7f6bc2f56000+e000]
[Sat Nov 11 15:46:15 2023] traps: steamwebhelper[211697] general protection fault ip:7f97e65aa582 sp:7ffeeb88a550 error:0 in libglapi.so.0.0.0[7f97e659d000+e000]
[Sat Nov 11 15:46:15 2023] traps: steamwebhelper[211715] general protection fault ip:7f97e65aa582 sp:7ffeeb88a550 error:0 in libglapi.so.0.0.0[7f97e659d000+e000]
[Sat Nov 11 15:46:15 2023] traps: steamwebhelper[211735] general protection fault ip:7f97e65aa582 sp:7ffeeb88a550 error:0 in libglapi.so.0.0.0[7f97e659d000+e000]
[Sat Nov 11 15:46:17 2023] traps: steamwebhelper[211658] general protection fault ip:7f45a289e582 sp:7ffc9f62cf70 error:0 in libglapi.so.0.0.0[7f45a2891000+e000]Got me thinking what package provides libglapi.so.0.0.0:
$ nix-locate libglapi.so.0.0.0 | grep -v '^('
driversi686Linux.mesa.out 232,836 x /nix/store/kx3dn4gaxz18my9xyj4bpjwzfii3jfws-mesa-22.0.4/lib/libglapi.so.0.0.0
mesa_drivers.out 317,064 x /nix/store/s4v469a3m7076hcjbwgh6vyy4dinba8h-mesa-22.0.4/lib/libglapi.so.0.0.0Seeing this line in the rebuilding of my nixosConfiguration also made me suspect as well:
steam-usr-target> warning: collision between `/nix/store/x17mgkzay4g3p4rv2air688nrnbwfnwh-mesa-2cf031/lib/libglapi.so' and `/nix/store/7wxw1dkd6pn6wd5zidd8096m6fknacrg-mesa-23.1.9/lib/libglapi.so'
steam-run-usr-target> warning: collision between `/nix/store/x17mgkzay4g3p4rv2air688nrnbwfnwh-mesa-2cf031/lib/libglapi.so' and `/nix/store/7wxw1dkd6pn6wd5zidd8096m6fknacrg-mesa-23.1.9/lib/libglapi.so'Realized that I was using chaotic-cx/nyx to give myself mesa-git to fix a very specific issue for a game. Found this comment that recommends changing the method as to which it is patched in as a troubleshooting step. So I set the following:
chaotic = {
mesa-git = {
enable = true;
fallbackSpecialisation = false;
method = "replaceRuntimeDependencies";
};
};Rebuilt my system with --impure (which I want to avoid, but I guess that's what I get for using the bleeding edge):
sudo nixos-rebuild switch --flake '.#dionysus' -L --verbose --impureNow steam runs fine from the terminal and I'm able to log in.
It kind of got me thinking: since it started working once I forced (I guess that's what the method option does) mesa-git to be used, is there some weirdness going on with multiple versions of mesa lying around?
I tried to use nix-tree to do some spelunking and noticed this message:
trace: replace-dependency.nix: Derivation /nix/store/cj5xwz6m6f73hm054dlz30dq5nxfqsc0-nixos-system-dionysus-23.11.20231104.85f1ba3 does not depend on /nix/store/jx2hkgk3ydlvr6qv5d7wwjcahll19vf2-mesa-23.1.9Anyways, searching for mesa with nix-tree gave me the following. Sorry, its messy as its a TUI program so I'm snipping some menu stuff:
mesa|
───────────────────────
mesa-23.1.9-drivers
mesa-23.1.9-osmesa
mesa-23.1.9-drivers.drv
mesa-2cf031.drv
mesa-23.1.9
mesa-2cf031-drivers
mesa-2cf031-drivers
mesa-2cf031
mesa-2cf031
mesa-23.1.9-osmesa.drv One could force usage of the chaotic-cx/nyx packages across the derivation/system by setting something like:
nixpkgs.overlays = [
(
_: prev: {
mesa = prev.mesa_git;
mesa32 = prev.mesa32_git;
}
)
];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.
hardware.opengl = {
package = pkgs.mesa_git.drivers;
package32 = pkgs.mesa32_git.drivers;
};I would say, if you are running into the above problems, try and see if you are pulling multiple versions of mesa and mesa32 in by using something like nix-tree. Maybe you have different versions of nixpkgs for various flake inputs?
PedroHLC
commented
12 months ago Realized that I was using
chaotic-cx/nyxto give myselfmesa-gitto fix a very specific issue for a game
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.
SrEstegosaurio
commented
12 months ago Steam will work flawlessly with the mesaa-git
I might be mistaken but doesn't mesa-git not work when using nvidia on a laptop? Or at least I recall seeing something similar on the chaotic-cx/nyx options description.
SrEstegosaurio
commented
10 months ago I fixed Steam being transparent for me in Hyprland by disabling hw accel as listed here https://github.com/hyprwm/Hyprland/issues/4173#event-11406636025
vendion
commented
1 month ago 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:
steam -vguisteam --reset$HOME/.cache/nvidia/GLCache directory, then launching steam.steam -no-cef-sandboxLog:
K900
commented
1 month ago 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.
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 https://github.com/NixOS/nixpkgs/issues/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.