Skip to content
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

build-fhs-userenv: Propagate $XAUTHORITY #27462

Merged
merged 1 commit into from
Jul 18, 2017
Merged

Conversation

jameysharp
Copy link
Contributor

The DISPLAY environment variable is propagated into chroots built with
buildFHSUserEnv, but currently the XAUTHORITY variable is not. When
the latter is set, its value is usually necessary in order to connect to
the X server identified by the former.

This matters for users running gdm3, for example, who have XAUTHORITY
set to something like /run/user/1000/gdm/Xauthority instead of the X
default of ~/.Xauthority, which doesn't exist in that setup.

Fixes #21532.

Motivation for this change
Things done
  • Tested using sandboxing
    (nix.useSandbox on NixOS,
    or option build-use-sandbox in nix.conf
    on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • Linux
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

The `DISPLAY` environment variable is propagated into chroots built with
`buildFHSUserEnv`, but currently the `XAUTHORITY` variable is not. When
the latter is set, its value is usually necessary in order to connect to
the X server identified by the former.

This matters for users running gdm3, for example, who have `XAUTHORITY`
set to something like `/run/user/1000/gdm/Xauthority` instead of the X
default of `~/.Xauthority`, which doesn't exist in that setup.

Fixes NixOS#21532.
@Mic92 Mic92 merged commit e4af2d6 into NixOS:master Jul 18, 2017
@Mic92
Copy link
Member

Mic92 commented Jul 18, 2017

Thanks!

@Mic92
Copy link
Member

Mic92 commented Jul 18, 2017

I also applied this to 17.03.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Steam fails to launch: "failed to initialize update status ui, or create initial window"
3 participants