-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
NixOS hyprland fails to start #9449
Comments
try building from latest commit edit - [LOG] Switching from VT 2 to VT 4 tbh just from this spam, probs not an issue with hyprland |
Same issue on 6d25ef0 logfile looks the same at first glance. What about this stuff?
|
Appears the issue is Hyprland was trying to start on my laptops dedicated GPU, using |
@TotalTaxAmount try aquamarine-git cause this commit prob fixes choosing the igpu |
I think my (Nixos) desktop is currently loading off integrated graphics instead of my actual GPU. How can I use aquamarine-git if I am using hyprland from the flake? I should already be using that correct? Edit: Swapping to the closed source drivers resolved this issue for me. I think this one was on nvidia. |
Instead of using
|
Already reported ? *
Regression?
Probably not a regression / I don't remember it happening before
System Info and Hyprland Version
System/Version info
Description
When trying to start Hyprland (not after update or anything) it now refuses to start, just hanging the login screen or tty. The only thing that I did was plug in a external monitor into HDMI, it was behaving weirdly but after I unplugged it the internal display on my laptop doesn't work with Hyprland. I tried reverting to a previous config via my nix config but even reverting to something I know worked in the past did not fix the issue.
How to reproduce
Attach not paste
Checklist of files to include below
hyprctl systeminfo -c
(always include)Additional info & File uploads
Logfile: https://paste.c-net.org/ClaricePrevail
Config (generated via nix): https://paste.c-net.org/WandaScrewed
The text was updated successfully, but these errors were encountered: