-
-
Notifications
You must be signed in to change notification settings - Fork 15.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gamescope: init at 3.11.33-jupiter-3.3-2 #181788
Conversation
Were you able to launch it on DRM using I was able to on the Steam Deck. Untested on any other hardware. (It was how I validated that touch input was broken when running embedded, but not on DRM.) |
Still waiting for my Steam Deck to arrive, but could the touch problem be related to the
|
Nope, touch is because when running embedded (e.g. under X11 or Wayland) it relies on SDL's fallback touch input machinery, which will resolve to click events, but don't work correctly for e.g. Steam's interface. The touch events are broken way earlier than any of the wayland/x11 components that gamescope launches. I have an almost-working bodge that proves all of that. |
Unfortunately not, I've tried a number of different vesions but none launch successfully from a VT console, at least not with my Nvidia card, haven't really tested with the Intel chip. update update 2 |
Added the meta and removed some uneeded buildInputs. Also added a wrapper because of this call, though it's only used for a debug flag it doesn't really increase the closure size so I think it's fine. |
Finally figured out how to launch from a VT, probably useful information for others. Opened an issue to request to make the behavior automatic: ValveSoftware/gamescope#560 Rebased to resolve conflicts and removed the commit on stb since it looks like someone recently fixed that in a nicer way. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you using alejandra to format? If so I highly recommend to switch back to nixpkgs-fmt because it creates code that is not compatible with the style in nixpkgs.
ah yeah, didn't even think about that, but your right, atm the format of nixpkgs is more in line with nixpkgs-fmt output. I'll reformat in a bit |
any reviewers so far care to approve? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks fine to me
tried with nvidia and intel, on Wayland and X
Successfully created backport PR #186347 for |
Package was added to nixpkgs in <NixOS/nixpkgs#181788>.
Description of changes
Closes #162562
Based on @samueldr's version #162562 (comment)
All I did was update to the latest tag,
add a pkgconfig file for stb, and add a small patch to stop meson from trying to load wlroots and libliftoff from it's src directory and instead rely on pkgconfig. That way we don't have to rely on copying sources as in the original.I also figured out a way to add the
cap_sys_nice
capbility for NixOS systems to launch steam. But the change may be a bit contentious since I'd have to patch the steam derivation (since bubblewrap will fail without suid bit), so I'll save that for a seprate PR.Note
I have not been able to successfully launch gamescope with the DRM backend from a VT. I have only been able to use it from a wayland session so far. Not sure if I just don't know the right flags to pass, or if this is a genuine upstream bug, or if it's an issue with Nvidia on a dual graphics laptop. Likely an upstream bug ValveSoftware/gamescope#498 (comment)It works by passing--disable-layers
ValveSoftware/gamescope#560Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notes