https://bugs.kde.org/show_bug.cgi?id=444298
j...@dnsense.pub changed:
What|Removed |Added
Status|RESOLVED|REOPENED
CC|
https://bugs.kde.org/show_bug.cgi?id=444298
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=444298
--- Comment #12 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=444298
--- Comment #11 from battler...@gmail.com ---
(In reply to Vlad Zahorodnii from comment #10)
> Have you tried setting KWIN_DRM_USE_MODIFIERS to 1? This may result in
> framebuffers having compressed modifier, which is good in terms of bandwidth.
Yea I
https://bugs.kde.org/show_bug.cgi?id=444298
--- Comment #10 from Vlad Zahorodnii ---
Have you tried setting KWIN_DRM_USE_MODIFIERS to 1? This may result in
framebuffers having compressed modifier, which is good in terms of bandwidth.
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=444298
--- Comment #9 from battler...@gmail.com ---
(In reply to Vlad Zahorodnii from comment #7)
> Based on drm_info output
>
> │ ├───CRTC 0
> │ │ ├───Object ID: 53
> │ │ ├───Mode: 2560x1440@199.99 driver phsync nvsync
> │ │ ├───Gamma size: 256
https://bugs.kde.org/show_bug.cgi?id=444298
--- Comment #8 from Vlad Zahorodnii ---
Another thing that's worth testing is whether it's due to kwin not using
modifiers. Can you add
KWIN_DRM_USE_MODIFIERS=1
to your /etc/environment and reboot the computer?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=444298
--- Comment #7 from Vlad Zahorodnii ---
Based on drm_info output
│ ├───CRTC 0
│ │ ├───Object ID: 53
│ │ ├───Mode: 2560x1440@199.99 driver phsync nvsync
│ │ ├───Gamma size: 256
│ │ └───Properties
│ │ ├───"ACTIVE" (atomic):
https://bugs.kde.org/show_bug.cgi?id=444298
--- Comment #6 from battler...@gmail.com ---
(In reply to Vlad Zahorodnii from comment #3)
> It might be a bandwidth limitation. Can you please check wayland session
> logs after changing the refresh rate? the logs can be found at
>
https://bugs.kde.org/show_bug.cgi?id=444298
--- Comment #5 from battler...@gmail.com ---
Created attachment 142859
--> https://bugs.kde.org/attachment.cgi?id=142859=edit
wayland-session.log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444298
--- Comment #4 from battler...@gmail.com ---
Created attachment 142858
--> https://bugs.kde.org/attachment.cgi?id=142858=edit
drm_info as requested
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=444298
--- Comment #3 from Vlad Zahorodnii ---
It might be a bandwidth limitation. Can you please check wayland session logs
after changing the refresh rate? the logs can be found at
~/.local/share/sddm/wayland-session.log (please remove any sensitive
https://bugs.kde.org/show_bug.cgi?id=444298
--- Comment #2 from battler...@gmail.com ---
(In reply to Vlad Zahorodnii from comment #1)
> How do you measure the frame rate? and what do you expect to see
>
> > OBSERVED RESULT
> > Nothing Happens
Easiest way for me is to simply look at the Monitor
https://bugs.kde.org/show_bug.cgi?id=444298
Vlad Zahorodnii changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
14 matches
Mail list logo
