[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 Zamundaaa changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/commit/05877a83211a |ma/kwin/commit/ba43e3d662e3 |ee64a47e227dde433ef19fec0b2 |2a1e3cfced759a13b7ca1e1f765 |e |0 --- Comment #27 from Zamundaaa --- Git commit ba43e3d662e32a1e3cfced759a13b7ca1e1f7650 by Xaver Hugl. Committed on 28/04/2022 at 14:14. Pushed by zamundaaa into branch 'Plasma/5.24'. backends/drm: reduce "max bpc" to what is actually used This prevents triggering a bug in the BenQ GW2765 monitor, and should in theory have no downsides. FIXED-IN: 5.24.5 M +5-1src/backends/drm/drm_pipeline.cpp https://invent.kde.org/plasma/kwin/commit/ba43e3d662e32a1e3cfced759a13b7ca1e1f7650 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 Zamundaaa changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/05877a83211a ||ee64a47e227dde433ef19fec0b2 ||e Version Fixed In||5.24.5 Status|REPORTED|RESOLVED --- Comment #26 from Zamundaaa --- Git commit 05877a83211aee64a47e227dde433ef19fec0b2e by Xaver Hugl. Committed on 28/04/2022 at 00:32. Pushed by zamundaaa into branch 'master'. backends/drm: reduce "max bpc" to what is actually used This prevents triggering a bug in the BenQ GW2765 monitor, and should in theory have no downsides. FIXED-IN: 5.24.5 M +5-1src/backends/drm/drm_pipeline.cpp https://invent.kde.org/plasma/kwin/commit/05877a83211aee64a47e227dde433ef19fec0b2e -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #25 from brady.phillip...@gmail.com --- I'm pleased to report that the new patch fixed it! 1440p now works fine on the BenQ. Thanks for helping even with such a niche issue. Interestingly, I changed the patch to be 10lu and that also fixed the issue. Booting into a tty or xorg works fine. I also tried riverwm, a wlroots based compositor, and that worked fine as well. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #24 from Zamundaaa --- Created attachment 148405 --> https://bugs.kde.org/attachment.cgi?id=148405&action=edit patch bpc=8 I still suspect that the bpc is the problem; I read today on dri-devel that the "max bpc" property currently works a bit differently than assumed. The attached patch for KWin (5.24 branch) should ensure that the "max bpc" property is always 8 or lower, like it was before 5.24. Can you test it? Additionally, if it helps and you change the "8lu" to "10lu", does it still work? To get some more clarity about that, how does it work on other display servers? So, if you reboot your computer and log into Xorg or Weston without first logging into the Plasma Wayland session, does that make a difference? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #23 from brady.phillip...@gmail.com --- (In reply to Zamundaaa from comment #22) > As this only appeared with 5.24 and this sounds vaguely like it could be > related to bandwidth issues of some sort, could you try running KWin with > the environment variable "KWIN_DRM_PREFER_COLOR_DEPTH=24" set? Trying > "KWIN_DRM_USE_MODIFIERS=1" could also be worth a shot Just gave this a try but unfortunately neither of those environment variables seemed to help. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #22 from Zamundaaa --- I had a good look at the logs and it doesn't seem like KWin ever updates outputs after startup, it never sets the CRTC ID of anything to 0, link-status is always good and both outputs get presentation events pretty much without interruption. In other words, according to those logs both outputs stay enabled the whole time and everything is working fine. Parts of the log are missing all information for some reason though, maybe all the problems are hiding in there... As this only appeared with 5.24 and this sounds vaguely like it could be related to bandwidth issues of some sort, could you try running KWin with the environment variable "KWIN_DRM_PREFER_COLOR_DEPTH=24" set? Trying "KWIN_DRM_USE_MODIFIERS=1" could also be worth a shot -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #21 from brady.phillip...@gmail.com --- I have uploaded the requested logs split into 4 different files due to the upload size limit. I first let it cycle around 3 times and then changed the resolution of the broken monitor to 1080p which made it work normally. This change can be seen in part 3 of the logs on line 21718. I then changed it back to 1440p which made it start cycling again. This change can be seen in part 4 of the logs on line 32397. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #20 from brady.phillip...@gmail.com --- Created attachment 147610 --> https://bugs.kde.org/attachment.cgi?id=147610&action=edit verbose kwin log part 4 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #19 from brady.phillip...@gmail.com --- Created attachment 147609 --> https://bugs.kde.org/attachment.cgi?id=147609&action=edit verbose kwin log part 3 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #18 from brady.phillip...@gmail.com --- Created attachment 147608 --> https://bugs.kde.org/attachment.cgi?id=147608&action=edit verbose kwin log part 2 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #17 from brady.phillip...@gmail.com --- Created attachment 147607 --> https://bugs.kde.org/attachment.cgi?id=147607&action=edit verbose kwin log part 1 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #16 from Zamundaaa --- Oh right, systemd boot is still disabled by default in 5.24. You can either check if legacy logging works (which goes into the file ~/.local/share/sddm/wayland-session.log) or you can enable systemd boot with kwriteconfig5 --file startkderc --group General --key systemdBoot true and reboot, then journalctl should show kwin logs -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 Joost Cassee changed: What|Removed |Added CC||jo...@cassee.net -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #15 from brady.phillip...@gmail.com --- When I tried to apply the patch, I didn't see any output in the journal that looked related to kwin and "journalctl --boot 0 | grep kwin_wayland_drm" returned nothing. I built the patched kwin first by adding the patch command to the pkgbuild and using pacman -U and when that showed nothing in the logs I tried building using the instructions in https://bugs.kde.org/show_bug.cgi?id=448220#c39 but I still got nothing in the logs. I did set the QT_LOGGING_RULES variable in /etc/environment so I'm not sure what I'm doing wrong. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #14 from Zamundaaa --- (In reply to brady.phillips99 from comment #13) > I had a quick look through the logs and did notice that at line 151 in the > dmesg-drm log, it says that the supported refresh rate is 0 Hz - 0 Hz which > doesn't seem right. AFAIK that just means that FreeSync is not supported. Weirdly enough, according to the logs, the monitor gets detected and nothing else happens. Are you sure the monitor disabled itself in time? I uploaded a patch for very verbose logging for this sort of stuff at https://bugs.kde.org/show_bug.cgi?id=448220#c37, could you try the same patch for this? It should at least tell us very clearly what KWin and KScreen are doing So, apply the patch, put QT_LOGGING_RULES="kwin_*.debug=true" into /etc/environment, reboot, let a few cycles happen and then upload the output of "journalctl --boot 0 | grep kwin_wayland_drm" here. Afterwards you'll want to revert to original KWin, to not fill your storage up with all the logging -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #13 from brady.phillip...@gmail.com --- (In reply to Zamundaaa from comment #10) > In order to maybe get more information on the process that happens, can > someone here execute the script on the bottom of the page > https://invent.kde.org/plasma/kwin/-/wikis/Debugging-DRM-issues and upload > the files it generates? > If the power cycling takes longer than 3 seconds, maybe also increase the > sleep time a bit, to catch at least one cycle I ran the script with 2 monitors connected with the sleep set to 20 to capture a full cycle. Note the broken monitor is the BenQ GW2765 which is connected through HDMI. The other monitor works fine. I had a quick look through the logs and did notice that at line 151 in the dmesg-drm log, it says that the supported refresh rate is 0 Hz - 0 Hz which doesn't seem right. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #12 from brady.phillip...@gmail.com --- Created attachment 147436 --> https://bugs.kde.org/attachment.cgi?id=147436&action=edit kwin-drm log -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #11 from brady.phillip...@gmail.com --- Created attachment 147435 --> https://bugs.kde.org/attachment.cgi?id=147435&action=edit dmesg-drm log -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #10 from Zamundaaa --- In order to maybe get more information on the process that happens, can someone here execute the script on the bottom of the page https://invent.kde.org/plasma/kwin/-/wikis/Debugging-DRM-issues and upload the files it generates? If the power cycling takes longer than 3 seconds, maybe also increase the sleep time a bit, to catch at least one cycle -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 --- Comment #9 from 0x10c...@gmail.com --- The Manjaro stable release channel just updated recently, and I can confirm the bug still exists. Linux/KDE Plasma: 5.16.11-2-MANJARO KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 The temporary workaround with setting the resolution to a lower 16:9 ratio works for now. I also tried setting the resolution to 1920x1200 and this resulted in the power cycling described above. I also tried setting the refresh rate to 50hz at 1920x1200 and for 2560x1440 and this also resulted in the power cycling. If anyone has any suggestions for troubleshooting this bug, I'm willing and able to test things out. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 449906] A monitor keeps power-cycling and disconnecting upon login
https://bugs.kde.org/show_bug.cgi?id=449906 0x10c...@gmail.com changed: What|Removed |Added Summary|A monitor keeps |A monitor keeps |power-cycling and |power-cycling and |disconnecting |disconnecting upon login -- You are receiving this mail because: You are watching all bug changes.
