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/k
https://bugs.kde.org/show_bug.cgi?id=449906
Zamundaaa changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
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 th
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
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 envi
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 muc
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 mad
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.
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.
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.
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.
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
kwritecon
https://bugs.kde.org/show_bug.cgi?id=449906
Joost Cassee changed:
What|Removed |Added
CC||jo...@cassee.net
--
You are receiving this mail
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
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 see
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/pl
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.
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.
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
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.
https://bugs.kde.org/show_bug.cgi?id=449906
0x10c...@gmail.com changed:
What|Removed |Added
Summary|A monitor keeps |A monitor keeps
|power-cy
21 matches
Mail list logo
