https://bugs.kde.org/show_bug.cgi?id=469558
Nate Graham changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=469558
medin changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=469558
Zamundaaa changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #12 from Nate Graham ---
FWIW to the extent that I do experience a mild version of this from time to
time with my 10th gen intel i7 CPU, KWIN_DRM_NO_AMS=1 makes it much worse.
--
You are receiving this mail because:
You are watching all bu
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #11 from medin ---
(In reply to Zamundaaa from comment #10)
> Okay, so udev events triggering stuff in KWin can be ruled out. Can you try
> putting
> > KWIN_DRM_PREFER_COLOR_DEPTH=24
> and
> > KWIN_DRM_USE_MODIFIERS=0
> and
> > KWIN_DRM_NO_
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #10 from Zamundaaa ---
Okay, so udev events triggering stuff in KWin can be ruled out. Can you try
putting
> KWIN_DRM_PREFER_COLOR_DEPTH=24
and
> KWIN_DRM_USE_MODIFIERS=0
and
> KWIN_DRM_NO_AMS=1
into /etc/environment and see if that makes a
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #9 from medin ---
(In reply to Zamundaaa from comment #8)
> Okay, so KWin is using OpenGL, and not using software rendering. If you run
> > udevadm monitor
> are there any events being printed?
It displays just the following lines without a
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #8 from Zamundaaa ---
Okay, so KWin is using OpenGL, and not using software rendering. If you run
> udevadm monitor
are there any events being printed?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #7 from medin ---
We(In reply to Nate Graham from comment #3)
> Interesting, I'm using a i7-10510U which is the same generation as the first
> processor you mentioned, and I don't experience these issues. i7 vs i3,
> though.
With another ol
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #6 from medin ---
Created attachment 159013
--> https://bugs.kde.org/attachment.cgi?id=159013&action=edit
drm_info_output.txt
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #5 from medin ---
(In reply to Zamundaaa from comment #4)
> Please attach the output of
> > journalctl --user-unit plasma-kwin_wayland --boot 0
> after running the Wayland session for a bit.
May 16 21:00:01 manjaro-med systemd[2932]: Start
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #4 from Zamundaaa ---
Please attach the output of
> journalctl --user-unit plasma-kwin_wayland --boot 0
after running the Wayland session for a bit.
The output of drm_info (https://gitlab.freedesktop.org/emersion/drm_info) would
also be usef
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #3 from Nate Graham ---
Interesting, I'm using a i7-10510U which is the same generation as the first
processor you mentioned, and I don't experience these issues. i7 vs i3, though.
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #2 from medin ---
(In reply to Nate Graham from comment #1)
> What kind of GPU are you using?
My laptop has CPU i3-1005g1 running Manjaro, the same happens with another
laptop with i3-5005u running KUbuntu.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=469558
--- Comment #1 from Nate Graham ---
What kind of GPU are you using?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469558
Nate Graham changed:
What|Removed |Added
Product|plasmashell |kwin
CC|
16 matches
Mail list logo
