https://bugs.kde.org/show_bug.cgi?id=452117
Zamundaaa changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=452117
johan.claudebreunin...@gmail.com changed:
What|Removed |Added
CC||johan.claudebreuninger@gmai
https://bugs.kde.org/show_bug.cgi?id=452117
Felix Yan changed:
What|Removed |Added
CC||felixonm...@archlinux.org
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=452117
--- Comment #7 from Antonio Orefice ---
(In reply to Nate Graham from comment #6)
> FWIW I've also been running with KWIN_DRM_NO_AMS=1, just because it keeps
> kwin_wayland's CPU usage down. I haven't noticed any regressions.
Yes, I opened something
https://bugs.kde.org/show_bug.cgi?id=452117
--- Comment #6 from Nate Graham ---
FWIW I've also been running with KWIN_DRM_NO_AMS=1, just because it keeps
kwin_wayland's CPU usage down. I haven't noticed any regressions.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452117
--- Comment #5 from Antonio Orefice ---
(In reply to Zamundaaa from comment #4)
> It's more or less an issue with how the atomic modesetting API currently
> works, changing that is not trivial but being worked on. You can use the
> environment variable
https://bugs.kde.org/show_bug.cgi?id=452117
Nate Graham changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=452117
--- Comment #4 from Zamundaaa ---
It's more or less an issue with how the atomic modesetting API currently works,
changing that is not trivial but being worked on. You can use the environment
variable "KWIN_DRM_NO_AMS=1" to have KWin fall back to the
https://bugs.kde.org/show_bug.cgi?id=452117
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org,
|
https://bugs.kde.org/show_bug.cgi?id=452117
Antonio Orefice changed:
What|Removed |Added
Summary|kwin on wayland not using |kwin on wayland: mouse
10 matches
Mail list logo
