You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On latest nixpkgs master commit, xwayland-satellite is broken.
At time of writing, the latest commit to nixos-unstable is 807e915. If the steps below don't work in a few days from now, replace nixos-unstable in commands with 807e915. The latest commit to master as i'm writing is 769a6a5.
nix run github:nixos/nixpkgs/nixos-unstable#xwayland-satellite -- :12
Observe that it says Connected to Xwayland on :12
nix run github:nixos/nixpkgs/master#xwayland-satellite -- :12
Observe that Xwayland never initializes
Expected behavior
Xwayland should initialize and xwayland-satellite should connect to it within less than a second of startup. (from what i can observe, usually within less than 100ms)
Screenshots
Here is some terminal output showing several xwayland-satellite packages. The first two invocations are identical, as i have the xwayland-satellite-unstable package from my niri flake installed in my system. Those packages are used here to indicate that this isn't necessarily a problem with nixpkgs' package expression, it is inherently a problem with a dependency (likely Xwayland). They're built against nixos-unstable.
This doesn't seem to be caused by us. I think it needs to be fixed upstream. I'm making this issue first, though, in case it is actually nixos-specific.
The PR updating xwayland was backported to nixos-24.05, and although that branch has no xwayland-satellite to break, my niri flake has a package that works on nixos-24.05 and when i try to check if the same regression applies there, i see no issue. This suggests the issue may not be caused by an xwayland update after all, since the backported PR (#352314) does not break an xwayland-satellite built against nixos-24.05
I'm currently bisecting nixpkgs to find the offending commit in case it's not that PR updating xwayland (which it seems not to be, given that it doesn't break on 24.05), This is taking a while, as Hydra doesn't cache every commit to nixpkgs, and i'm currently on the third iteration of a bisect script which has taken over am hour so far and doesn't seem to be anywhere near the end. Will update once this bisect yields a result, or if i fall asleep before that point, hopefully i'll have an update in the morning if it finished by then
Describe the bug
On latest nixpkgs master commit,
xwayland-satellite
is broken.At time of writing, the latest commit to
nixos-unstable
is 807e915. If the steps below don't work in a few days from now, replacenixos-unstable
in commands with 807e915. The latest commit to master as i'm writing is 769a6a5.nixos-unstable
): 807e915master
): 769a6a5Steps To Reproduce
Steps to reproduce the behavior:
nix run github:nixos/nixpkgs/nixos-unstable#xwayland-satellite -- :12
Connected to Xwayland on :12
nix run github:nixos/nixpkgs/master#xwayland-satellite -- :12
Expected behavior
Xwayland should initialize and xwayland-satellite should connect to it within less than a second of startup. (from what i can observe, usually within less than 100ms)
Screenshots
Here is some terminal output showing several xwayland-satellite packages. The first two invocations are identical, as i have the
xwayland-satellite-unstable
package from my niri flake installed in my system. Those packages are used here to indicate that this isn't necessarily a problem with nixpkgs' package expression, it is inherently a problem with a dependency (likely Xwayland). They're built againstnixos-unstable
.Additional context
This doesn't seem to be caused by us. I think it needs to be fixed upstream. I'm making this issue first, though, in case it is actually nixos-specific.
Notify maintainers
@if-loop69420 @getchoo are the other maintainers of the
xwayland-satellite
packageMetadata
"x86_64-linux"
Linux 6.6.54, NixOS, 24.11 (Vicuna), 24.11.20241029.807e915
yes
yes
nix-env (Nix) 2.24.9
"nixos"
""
/nix/store/m68ikm8045fj7ys7qvgr608z9l70hh1k-source
Add a 👍 reaction to issues you find important.
The text was updated successfully, but these errors were encountered: