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
In #368074 and #368084, NixOS swapped to using Wayland by default for Plasma6 systems, in unstable and 24.11 respectively. On Hyper-V, this prevents the window manager from ever loading; instead all you get is the systemd startup log as far as [ OK ] Reached Target Graphical Interface.
Copy the .vhdx file out of the store and onto your Hyper-V host, and set up a Hyper-V VM using the defaults except for (a) using a Generation 2 VM, (b) selecting the generated .vhdx as the hard disk, and (c) disabling Secure Boot.
Short term, I suspect we should do one or both of:
Back out this change from 24.11, since it's clearly a regression in some circumstances even if it fixes others
Change services.displayManager.sddm.wayland.enable from mkDefault true to mkDefault (!config.virtualisation.hypervGuest.enable)
Longer-term we should probably work out why Hyper-V and Plasma+Wayland aren't playing nicely together. I'd guess that's an upstream problem, but I've not tried investigating and wouldn't be sure where to start.
Metadata
system: "x86_64-linux"
host os: Linux 6.6.67, NixOS, 24.11 (Vicuna), 24.11pre-git
Describe the bug
In #368074 and #368084, NixOS swapped to using Wayland by default for Plasma6 systems, in unstable and 24.11 respectively. On Hyper-V, this prevents the window manager from ever loading; instead all you get is the systemd startup log as far as
[ OK ] Reached Target Graphical Interface
.Steps To Reproduce
Steps to reproduce the behavior:
Get a checkout of nixpkgs and install
nixos-generators
.I've been testing with the following
configuration.nix
(most of which is just personal preference for a minimal image):Go to your nixpkgs repository and check out a relevant commit:
git switch --detach f3160e4c2f38
git switch --detach f3160e4c2f38^
Build a VHDX file to use in Hyper-V:
Copy the .vhdx file out of the store and onto your Hyper-V host, and set up a Hyper-V VM using the defaults except for (a) using a Generation 2 VM, (b) selecting the generated .vhdx as the hard disk, and (c) disabling Secure Boot.
Boot the VM.
Expected behavior
The system boots to the SDDM greeter.
Screenshots
Additional context
This change was introduced to fix #363797.
Short term, I suspect we should do one or both of:
services.displayManager.sddm.wayland.enable
frommkDefault true
tomkDefault (!config.virtualisation.hypervGuest.enable)
Longer-term we should probably work out why Hyper-V and Plasma+Wayland aren't playing nicely together. I'd guess that's an upstream problem, but I've not tried investigating and wouldn't be sure where to start.
Metadata
"x86_64-linux"
Linux 6.6.67, NixOS, 24.11 (Vicuna), 24.11pre-git
no
yes
nix-env (Nix) 2.24.10
/nix/var/nix/profiles/per-user/root/channels/nixos
Notify maintainers
Not sure who's entirely appropriate here, but making a few hopefully-reasonable guesses:
kdePackages.qtwayland
: @milahu @NickCaoNote for maintainers: Please tag this issue in your PR.
Add a 👍 reaction to issues you find important.
The text was updated successfully, but these errors were encountered: