Change:
then [ package ] ++ extraPackages else [ package32 ] ++ extraPackages32; in prevLibs ++ additionalLibs; <ins> extraPkgs = p: (cfg.extraPackages ++ lib.optionals (prev ? extraPkgs) (prev.extraPkgs p)); </ins> } // lib.optionalAttrs (cfg.gamescopeSession.enable && gamescopeCfg.capSysNice) { buildFHSEnv = pkgs.buildFHSEnv.override {

Discussion:
gamescope crashes with this error when run from within steam's fhsenv: This check in wlroots causes that error because inside steam's fhsenv the /tmp/.X11-unix directory is owned by nobody:nogroup. I have tried simply removing the check from wlroots but in that case gamescope simply hangs. (Note that it's gamescope that depends on wlroots so this bug happens under x11 window managers too.) Steps to reproduce the behavior: steam to the launch options of any game the game
This seems to be a very old issue with NixOS
would allow to run with without having to manually chown /tmp/.X11-unix but running from within steam as described above is still broken. gamescope dies with this error: However : So that symbol is actually defined but Xwayland thinks it's not for some reason.
I've encountered this issue too! I know got gamescope to run on NixOS - maybe we're missing something? See my comment here: Related:
Hi, I just wanted to real quickly add some context with my knowledge of how Steam works. this part is not the issue and is an ""issue"" about the steam overlay, it happens because there is both a 32 bit and 64 bit version of the overlay both of which are loaded when you launch a 32bit or 64bit game, so this is not related. It happens every time you launch a game on any distro without fail since a game cannot both be 32 and 64 bit. ERROR: object '' from LDPRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored. Everything else in this log seems normal, outside of this part: which could point to a missing library. the mentioned "" might be what we need to look at here. Also, thank you so much to for posting the workaround too, I was getting a headache dealing with this.
Hi, i wanted to ask if someone is working on this issue?
It's an open-source project, so unless someone with the necessary knowledge is interested in the issue (could be yourself), then you'll probably have to wait.
I ran into this same issue before. The only thing that let me run gamescope through steam so far has been the solution from , but I am not sure why it works.

I'm trying to add the patch in in , eagering for testing from you.
There seem to be multiple issues conflated here. The original issue with X11 socket ownership has been addressed. If there's another issue that prevents running gamescope in Steam, please report it separately.

Asian characters are all rendered as squares in client(not in games). Looks like steam client is not picking up system font configs? ! !
Note that Arch's wiki contains some useful information on that ().
Thanks, After a bit of testing, I realized steam client need font to display Asian characters. Adding to would resolve this. Maybe we could include that as a config option for Another thing I'm not so sure is about the font-config. My font configuration originally has some default config setting like: With that setting enabled, even adding to , Steam client still won't able to display Asian fonts. I have to disable the defaultFonts config to make Steam happy. I'd expect if not fount, it'd fall back to installed in the system this case. Maybe I misunderstood the purpose of defaultFonts config. My previous full font config: Below one makes steam happy (without defaultFonts):
Steam seems to have issues with variable fonts (noto-fonts-cjk-sans is packaged as a vf in nixpkgs). I am able to make it display CJK characters correctly after applying this PR:
Just came here to say I'm also having this problem with the Flatpak version of Steam on NixOS. seems to be the upstream issue.
Over time, this problem has had multiple different and complex causes on different Steam versions. This includes historical inability to load variable fonts, and font specification for Arial. For the author of this post, a detailed explanation and solution to this problem is here:
Non of the solutions mentioned here worked for me... I even cleared the fonts cached of steam and the system. What did work was adding this to my Yes I know that's not how you install steam and it seems superfluous, but it is the only thing that worked. Proof: !
I have already fixed this issue in , now steam will use the system fonts, and the font config in your home dir. You can also use if you won't want to introduce japanese fonts into your system.