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
I have searched the existing open and closed issues.
Regression?
Yes
System Info and Version
System/Version info
Hyprland, built from branch at commit dirty ().
Date:
Tag: , commits:
flags: (if any)
System Information:
System name: Linux
Node name: <redacted>
Release: 6.6.33
Version: #1-NixOS SMP PREEMPT_DYNAMIC Wed Jun 12 09:13:03 UTC 2024
GPU information:
os-release: ANSI_COLOR="1;34"
BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues"
BUILD_ID="24.11.20240613.e9ee548"
DOCUMENTATION_URL="https://nixos.org/learn.html"
HOME_URL="https://nixos.org/"
ID=nixos
IMAGE_ID=""
IMAGE_VERSION=""
LOGO="nix-snowflake"
NAME=NixOS
PRETTY_NAME="NixOS 24.11 (Vicuna)"
SUPPORT_URL="https://nixos.org/community.html"
VERSION="24.11 (Vicuna)"
VERSION_CODENAME=vicuna
VERSION_ID="24.11"
plugins:
WLR_DRM_NO_ATOMIC is set to '1'
Description
in version 0.40.0, my two Lenovo monitors both connected to a Dell WD19TB dock are working fine, both on [email protected].
However, when I update my nix flake, one of them stops working. It will be detected in hyprctl monitors, and hyprctl does seem to think it is running fine, but it has no input. If I go to the workspace by hotkey or mouse, it will also just think it's displaying it, but the monitor stays black. If I reduce the resolution by running
hyprctl keyword monitor "DP-5,disable"
followed by hyprctl keyword monitor "DP-5,1920x1200@60,0x0,1"
It does work with a 1920x1200 resolution. However, if I then change it back with hyprctl keyword monitor "DP-5,disable" hyprctl keyword monitor "DP-5,2560x1440@60,0x0,1"
It will create all sorts of weird issues where either the monitor renders partly, it does not render at all but is turned on, etc. Also moving my cursor to the border of my working monitor to that monitor will make it lagg, and switching to the workspace that is supposedly on that monitor will make it lagg a lot as well.
In the past, I faced this same issue, but adding WLR_DRM_NO_MODIFIERS fixed this. In the later version, this option no longer seems to have effect.
Laptop driving it is a Dell latitude 5401, without a discrete graphics card, so only integrated graphics.
How to reproduce
0.40.0-unstable-2024-05-05 is the confirmed working version (git rev f155133)
0.43.0 Is the version where it for sure does not work anymore
Crash reports, logs, images, videos
No response
The text was updated successfully, but these errors were encountered:
Already reported ? *
Regression?
Yes
System Info and Version
System/Version info
WLR_DRM_NO_ATOMIC is set to '1'
Description
in version 0.40.0, my two Lenovo monitors both connected to a Dell WD19TB dock are working fine, both on [email protected].
However, when I update my nix flake, one of them stops working. It will be detected in hyprctl monitors, and hyprctl does seem to think it is running fine, but it has no input. If I go to the workspace by hotkey or mouse, it will also just think it's displaying it, but the monitor stays black. If I reduce the resolution by running
hyprctl keyword monitor "DP-5,disable"
followed by
hyprctl keyword monitor "DP-5,1920x1200@60,0x0,1"
It does work with a 1920x1200 resolution. However, if I then change it back with
hyprctl keyword monitor "DP-5,disable"
hyprctl keyword monitor "DP-5,2560x1440@60,0x0,1"
It will create all sorts of weird issues where either the monitor renders partly, it does not render at all but is turned on, etc. Also moving my cursor to the border of my working monitor to that monitor will make it lagg, and switching to the workspace that is supposedly on that monitor will make it lagg a lot as well.
In the past, I faced this same issue, but adding WLR_DRM_NO_MODIFIERS fixed this. In the later version, this option no longer seems to have effect.
Laptop driving it is a Dell latitude 5401, without a discrete graphics card, so only integrated graphics.
How to reproduce
0.40.0-unstable-2024-05-05 is the confirmed working version (git rev f155133)
0.43.0 Is the version where it for sure does not work anymore
Crash reports, logs, images, videos
No response
The text was updated successfully, but these errors were encountered: