-
-
Notifications
You must be signed in to change notification settings - Fork 773
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
Hyprctl dispatch dpms off issues with Dell monitor over HDMI #1475
Comments
Same with crappy ViewSonic HDMI monitor. My VGA Dell monitor appears to work correctly. |
I am having the very same issue here with a BenQ GW2283. The BenQ monitor is connected over DP to HDMI |
UPDATE:
So this is definitely an HDMI issue here, D-SUB VGA and DisplayPort work fine. Btw, in my case swaylock is not bypassed I use this script:
@vaxerski This looks like a software issue, but I'm not sure. |
can you test on sway-git? (important: git) If it's reproducible there it's a wlr issue |
Yup, tested on Sway-git, DPMS stays off there. |
Yes |
Same here with AOC U2790B model but with one addition... my monitor OSD turns off as soon as I turn it on! It's basically unusable because it lasts for only fraction of a second. Maybe you could check if you have the same issue on those other monitors reported and if issue is related? |
Quick add: I've removed the |
Here's my What I did was:
This is my This is the part from turning DPMS off till I unlock swaylock: From what I read out of the part of the log, Hyprland destroys the monitor, then finds it and sets it up again. |
@verystealthy; @beltofdespair; @psiho Hey back, I have developed a workaround using 2 shellscripts:
Hope this helps at least a bit! |
Thanks, @HanoJing. I'm sure this will come in handy for someone, but I've moved on from Hyprland. I'm leaving this issue here just in case. |
Having the same issue atm. Noticed it first when running |
Same for me. @vaxerski How's the progress on this? Thanks! |
there is no progress, and please consider not adding noise. I am aware. It's not my fault your monitor(s) behave weirdly. I have other things to worry about as well. If you want this fixed faster, make a mr yourself. |
Open source, am I right? |
It might be HDMI vs Display Port or more than one screen connected. I don't think closing the bug helps.. |
My thought exactly. I might be able to look into this soon™, but will definitely need some time getting familiar with the codebase and so on. Edit: Also what is kinda scary (imo) about this is the window manager being able to bypass swaylock |
Hyprland is not a window manager. It's the entire display server, like Xorg itself. Again, don't know how many times I have to repeat that. swaylock is not possible to bypass if you update it to use the proper protocol and stop using a horribly outdated fork.
I don't think so either, but some people apparently expect undivided attention from me at all times and bugfixes within 10 minutes. I am not in any way, shape, or form obliged to give any support. I work on things that I deem the most important at a given time. Doesn't mean I will never work on your issue, it just means there are more pressing ones. Adding to the fact of course that I do not use HDMI anywhere and have never seen this happen myself, so I can't repro. |
well, this escalated quickly. I understand some people expect "undevided attention" as you say, but what about many others, having the same issue, that are not? Closing the issue in this manner is just... mah. |
Umm, consider reading who closed it. Not me. |
My apologies. I think I might have given the impression that I still care about this issue, Hyprland, or extremely low stakes drama. About three months ago (give or take), I went through the trouble of gathering the information required for a useful bug report, submitted it, and that was it. It went unassigned, unacknowledged, and no further information was asked. I have since moved on from, well, all of this, but I keep getting notifications from GitHub about the issue. Needless to say that those notifications are a nuisance, entitled users are indeed annoying, and bitchy developers, who—much like DJ Khaled—seem to be suffering from success, are tiresome. Given all that, I did indeed close this. So, reopen the issue. Create a new one. Move away from Hypland. Purchase a Mac. I do not care. Just let this particular thread die peacefully and let's all move on with our lives. |
You can disable notifications for this issue.. |
If I was Vaxry, I would be easily stressed out, given how much they work. And I think that it is totally ok and necessary for them to rightfully stand their ground and reject issues that are unimportant. I don't expect anything from them, I was just asking. And I wanted to help them and the people who have this issue by mitigating the issue with the shellscript I wrote. |
Thanks for all your hard work, @vaxerski! For anyone else still having issues with getting this to work, here's the locking script I run which works flawlessly both with HDMI and DP:
Adjust timeout duration and other settings to your liking. |
After a frankly absurd amount of testing, it seems that for me that script works, but only if I leave timeout at 1. Any other number and the monitors immediately turn back on. A real head scratcher. But that might be enough to lure me back from Sway. On Arch Linux with latest release version 0.26.0-1. |
I'm running into the same issue with an MSI MAG274QRF-QD. DPMS doesn't stay off, and in swaylock/swayidle it keeps turning it off and then on again until finally it crashes with a red screen of death. |
After further testing, it seems not to be my MSI monitor but instead the dell secondary monitor. It keeps turning on immediately after turning itself off on the "no output on DP" message. Both my monitors are running purely on DP. No HDMI nor converters. |
That's interesting, so it's not an HDMI issue then. I will test this again soon and see if things have changed now that Hyprland has evolved a lot more. |
I did some more testing, and it actually seems to be an issue with my wireless mouse. I have a logitech g pro wireless, and if I disable
It will work, however, my 2nd monitor won't turn on when I unlock swaylock. My primary MSI monitor turns on fine, however. If I enable In either case, it doesn't enable the dell monitor on unlock, as I removed the swayidle resumecommand and thus have to run Not sure if my issue is exactly the same as the reported one, in my case at least it's definitely swayidle/hyprland responding wrongly to my wireless mouse. Also, swaylock is not bypassed and no new workspaces are created. |
Hmm weird, I have an issue with My BenQ GW2283 will come on again a few seconds after DPMS has been turned off. Maybe it's the screen-brightness indicator of my monitor that causes it to want to turn on again who knows. |
I had this issue with an HP monitor (HP M24fw FHD 3CM2230DRR). I simply disabled the 'Auto-Switch Input' feature in it, and since then, it has been working as expected. If this doesn't work try disabling any other automatic options your monitor may have; maybe one of them is causing the issue. |
Thanks for the suggestion, it sadly didn't work for my monitor model, good that you mention it though. My monitor seems to turn on because it wants to show me some icon regarding brightness. It doesn't want to not shot it even when turning off auto-brightness. |
Update on this: |
|
Radeon RX 550 here, |
Do note that it will prevent HDMI audio from working, so if your setup involves using that (Mine for example did), you may want to stick to broken Display Core |
Turning off auto input select on my Dell fixed it for me also, fwiw. |
Using HDMI on Samsung monitor, turned auto source to manual solved the problem for me! Thanks for continuing the comments. |
@beltofdespair |
I've found really good work around for this using ddcutil + hypridle
|
I have a monitor on which I can't turn off auto input switch so I made script to send dpms off repeatedly. dpms-off.sh #!/usr/bin/env bash
start_time=$(date +%s)
end_time=$((start_time + 30))
while [[ $start_time -lt $end_time ]]; do
sleep 0.1
hyprctl dispatch dpms off &>> /tmp/dpms-off.log
start_time=$(date +%s)
done
|
Turning off auto scan on my MSI monitor fixed the issue for me, dpms will stay off on both of my monitors now. The only thing that I did need in my config is to remove mouse_move_enables_dpms as somehow my wireless mouse can't not send data. |
hyprctl dispatch dpms off
directly or viaswayidle
dpms on
is called, or input is detected.That being said, I am somewhat reluctant to even create this issue, because it seems like the monitor is at fault here. My hope is that folks having the same issue can find this and get some peace of mind.
The monitor in question is a Dell S3221QS connected over HDMI.
swayidle
callsswaylock
normally after the timeout,swaylock
does its job if input activity happens beforehyprctl dispatch dpms off
is called. Ifhyprctl dispatch dpms off
is called, the monitor turns off, and turns back on after a few seconds. When the monitor turns back on,swaylock
is bypassed, and a new workspace is created. For example, if 3 workspaces were active whenhyprctl dispatch dpms off
was called, workspace number 4 would be created when the monitor turns back on. Another "interesting" tidbit is that after the monitor turns back on,swayidle
is no longer active unless you go back to one of the original workspaces (i.e.swayidle
andswaylock
won't trigger on this newly created workspace).Looking at the logs (attached here), something is causing
Events::listener_monitorDestroy
to be called. After a bit of testing, it is clear that this is being caused by the monitor itself, as I've performed the following:hyprctl dispatch dpms off
on a laptop running Hyprland: Normal behavior (e.g. screen remained off);hyprctl dispatch dpms off
on a TV connected to the original computer via HDMI: Normal behavior (e.g. screen remained off);Additional details:
Hyprland log:
hyprland.log
The text was updated successfully, but these errors were encountered: