https://bugs.kde.org/show_bug.cgi?id=475322
--- Comment #3 from fililip ---
I don't think that's relevant (but may as well be); it works with native
Wayland apps, just not with XWayland (xwayland blocks kwin).
Though, sometimes resetting the GPU does make KWin crash/hang even without
XWayland
https://bugs.kde.org/show_bug.cgi?id=475322
--- Comment #6 from fililip ---
Also, the first GPU reset is *extremely* slow with newer Mesa.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=475322
--- Comment #4 from fililip ---
I tested Mesa 23.3, as well as 24. The reset mechanism is now extremely buggy;
the second reset always resets kwin, killing all apps.
Is this a Mesa issue or a Plasma 5 issue (that's fixed in 6)?
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=475322
--- Comment #5 from fililip ---
It starts with
kwin_wayland[60753]: kwin_scene_opengl: Waiting for glGetGraphicsResetStatus to
return GL_NO_ERROR timed out!
and ends with a long stack trace:
#0 0x7f870c43f73d syscall (libc.so.6 + 0x10e73d)
#1
https://bugs.kde.org/show_bug.cgi?id=464868
--- Comment #9 from fililip ---
Thanks!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=480895
Bug ID: 480895
Summary: KWin 5.93.0 has a DRM timeout issue with GPU resets
Classification: Plasma
Product: kwin
Version: 5.93.0
Platform: Arch Linux
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=480895
--- Comment #9 from fililip ---
Thanks a lot for the prompt fix!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478938
Bug ID: 478938
Summary: The presentation time protocol is buggy with VRR on
Chromium
Classification: Plasma
Product: kwin
Version: 5.91.0
Platform: Arch Linux
https://bugs.kde.org/show_bug.cgi?id=475322
--- Comment #8 from fililip ---
As funny as that sounds, you can try using HIP with Blender to trigger a real
reset (https://projects.blender.org/blender/blender/issues/100353, this is
still not fixed...):
1. Open Blender
2. Select the Cycles HIP
https://bugs.kde.org/show_bug.cgi?id=478938
--- Comment #3 from fililip ---
Done https://bugs.chromium.org/p/chromium/issues/detail?id=1517884
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=479845
Bug ID: 479845
Summary: The current Wayland GPU recovery experience (AMD) is
not ideal
Classification: Plasma
Product: kwin
Version: 5.92.0
Platform: Arch Linux
https://bugs.kde.org/show_bug.cgi?id=479845
--- Comment #1 from fililip ---
Don't know if it's related to the issue (sorry if it isn't), but I tried
applying this MR:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/27097 on top of Mesa
24.0.0-rc1 (and the linked patches against Linux
https://bugs.kde.org/show_bug.cgi?id=479845
--- Comment #3 from fililip ---
> GPU reset handling is something that's very WIP throughout the stack
By the stack do you mean kwin, upstream, or both? I thought kwin already had
GPU recovery support for Wayland, I might be wrong though (unless wha
https://bugs.kde.org/show_bug.cgi?id=479845
--- Comment #5 from fililip ---
Oh, I noticed one important thing - I was using the legacy DRM API
(KWIN_DRM_NO_AMS=1) for tearing support. After disabling it, on latest Mesa
24.1 (dev) stuff works fine even on Plasma 5. Sorry for the trouble
https://bugs.kde.org/show_bug.cgi?id=475322
--- Comment #9 from fililip ---
I've just had an idea: would it be possible to kill/restart Xwayland (togglable
somehow with an env var or something similar) on a reset? That would be much
better than a frozen desktop session.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=464868
fililip changed:
What|Removed |Added
CC||t...@nitrosubs.live
--- Comment #7 from fililip
https://bugs.kde.org/show_bug.cgi?id=480895
fililip changed:
What|Removed |Added
Summary|KWin 5.93.0 has a DRM |KWin has a DRM timeout
|timeout
https://bugs.kde.org/show_bug.cgi?id=480895
--- Comment #2 from fililip ---
One more thing: it also happens on 5.92.0 but can be worked around by disabling
the hardware cursor, then it works. Should have added that.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=480895
--- Comment #3 from fililip ---
(In reply to Zamundaaa from comment #1)
> This is a kernel bug, please report it to
> https://gitlab.freedesktop.org/drm/amd/-/issues
>
> Maybe we should add a fallback timer for when pageflips time out so
https://bugs.kde.org/show_bug.cgi?id=480895
--- Comment #4 from fililip ---
(In reply to fililip from comment #3)
> (In reply to Zamundaaa from comment #1)
> > This is a kernel bug, please report it to
> > https://gitlab.freedesktop.org/drm/amd/-/issues
> >
> > May
https://bugs.kde.org/show_bug.cgi?id=480895
--- Comment #5 from fililip ---
Another observation: this has nothing to do with KWin's version. Disabling the
hardware cursor just makes it work somehow.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=479845
--- Comment #7 from fililip ---
Personally, I don't think there's a point to maintaining legacy modesetting
(even if there's still no tearing support for atomic), unless it's actually
used on some devices (it's great for my non-VRR laptop; with a 60Hz
https://bugs.kde.org/show_bug.cgi?id=485425
Bug ID: 485425
Summary: Running Steam breaks always-on VRR on desktop, forcing
full refresh rate
Classification: Plasma
Product: kwin
Version: 6.0.3
Platform: Arch Linux
https://bugs.kde.org/show_bug.cgi?id=486081
--- Comment #2 from fililip ---
I've noticed one more thing.
Going to https://mozilla.github.io/webrtc-landing/gum_test.html and setting a
high FPS value (like 60 or even 120) results in the "FPS now" metric severely
dropping while moving
https://bugs.kde.org/show_bug.cgi?id=486081
Bug ID: 486081
Summary: Frame swapping in WebRTC screensharing while moving
the mouse
Classification: Plasma
Product: kwin
Version: 6.0.4
Platform: Arch Linux
https://bugs.kde.org/show_bug.cgi?id=486081
--- Comment #5 from fililip ---
Thanks a lot for finding relevant information! I'll try to patch kwin and
report back.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=485425
--- Comment #5 from fililip ---
Running Steam in gamescope seems to mitigate this problem.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=485425
--- Comment #1 from fililip ---
I've also observed much higher CPU usage with KWin while idle.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=485425
--- Comment #3 from fililip ---
Do you exhibit the CPU usage issue though? On my system, kwin_wayland's CPU
usage increases by around 8% even after Steam is terminated. Restarting KWin
helps.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=485425
--- Comment #6 from fililip ---
Oh, alright, suspecting that it might be relevant, I unloaded the nvidia driver
and removed the card from the PCI tree on my PC, everything is 100% fine now.
I do wonder what Steam is doing with nvidia that is causing
https://bugs.kde.org/show_bug.cgi?id=485425
fililip changed:
What|Removed |Added
Summary|Running Steam breaks|Running Steam causes KWin's
https://bugs.kde.org/show_bug.cgi?id=485425
--- Comment #7 from fililip ---
One final note though, to whom it may concern: on AMD/NVIDIA systems launching
Steam has to be done like so:
VK_DRIVER_FILES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json steam
This also works.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=485425
--- Comment #8 from fililip ---
Ah, unfortunately not - I still had the nvidia driver unloaded. The Vulkan
driver choice doesn't seem to matter.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=485425
--- Comment #4 from fililip ---
I've just checked it with the Show Paint effect: before Steam has ever been
opened during a session on an empty desktop everything is fine. After Steam has
run at least once, the effect constantly triggers, even
https://bugs.kde.org/show_bug.cgi?id=485425
--- Comment #9 from fililip ---
I reported the issue to the Steam issue tracker too:
https://github.com/ValveSoftware/steam-for-linux/issues/10847
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=485425
fililip changed:
What|Removed |Added
Summary|Running Steam causes KWin's |Running Steam on AMD+NVIDIA
|CPU
https://bugs.kde.org/show_bug.cgi?id=485425
--- Comment #10 from fililip ---
After further testing, this can also happen when any
"custom-border"/"custom-window" Xwayland app (such as FL Studio via Wine,
Steam, game/mod launchers via Wine, etc.) is launched.
This in turn
https://bugs.kde.org/show_bug.cgi?id=485425
fililip changed:
What|Removed |Added
Summary|Running Steam on AMD+NVIDIA |Running a "custom"
https://bugs.kde.org/show_bug.cgi?id=483240
fililip changed:
What|Removed |Added
CC||t...@nitrosubs.live
--- Comment #6 from fililip
https://bugs.kde.org/show_bug.cgi?id=485425
fililip changed:
What|Removed |Added
CC||t...@nitrosubs.live
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=485425
fililip changed:
What|Removed |Added
Summary|Running some Wine (X11) |Running some Wine
|applications
https://bugs.kde.org/show_bug.cgi?id=486081
--- Comment #6 from fililip ---
It looks like https://webrtc-review.googlesource.com/c/src/+/349881 has been
merged.
Now we need to wait for Firefox and Chromium to make use of this WebRTC fix.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=485425
fililip changed:
What|Removed |Added
Summary|Running a "custom" X window |Running a Wine/X11
|vi
https://bugs.kde.org/show_bug.cgi?id=485425
fililip changed:
What|Removed |Added
Summary|Running a Wine/X11 |Running some Wine (X11
https://bugs.kde.org/show_bug.cgi?id=475322
fililip changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=483240
--- Comment #4 from fililip ---
One note I'll add: after resuming from suspend, even when using the HW cursor,
VRR still breaks below 30 FPS and requires a restart of KWin. Is this just
random behavior or a bug?
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=483240
Bug ID: 483240
Summary: VRR below 30-ish FPS turns off completely
Classification: Plasma
Product: kwin
Version: 6.0.1
Platform: Arch Linux
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=483240
--- Comment #1 from fililip ---
I should probably add that using the hardware cursor works fine (I was using
the software one), but I'd personally prefer to have the option to retain even
a low software cursor refresh rate anyway, or at least not have
https://bugs.kde.org/show_bug.cgi?id=483240
--- Comment #3 from fililip ---
Ok, thanks for the quick response! I appreciate it. I'll stick to the HW cursor
for now then.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=483240
--- Comment #5 from fililip ---
I managed to add an option to override this behavior with an environment
variable, LFC finally works as it did before.
diff --git a/src/core/renderloop.cpp b/src/core/renderloop.cpp
index 5e3a74c..de7b7d3 100644
https://bugs.kde.org/show_bug.cgi?id=475322
fililip changed:
What|Removed |Added
Status|RESOLVED|REPORTED
Ever confirmed|1
https://bugs.kde.org/show_bug.cgi?id=481688
Bug ID: 481688
Summary: KWin crashes when both Alt+F3 and Alt+F4 are pressed
on a window
Classification: Plasma
Product: kwin
Version: master
Platform: Arch Linux
https://bugs.kde.org/show_bug.cgi?id=481688
--- Comment #1 from fililip ---
One thing of note is that the issue goes away after unsetting the default Alt +
F3 shortcut
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481688
--- Comment #3 from fililip ---
kwin_wayland[3942]: ASSERT: "!window->isDeleted()" in file
/usr/src/debug/kwin/kwin/src/focuschain.cpp, line 217
systemd-coredump[78293]: Process 3942 (kwin_wayland) of user 100
https://bugs.kde.org/show_bug.cgi?id=481688
--- Comment #4 from fililip ---
Thread 1 "kwin_wayland" received signal SIGABRT, Aborted.
0x7f5a1b6ab32c in ?? () from /usr/lib/libc.so.6
Thread 39 (Thread 0x7f5991a006c0 (LWP 89386) "Thread (pooled)"):
#0 0x7f5a1b6a5ebe i
https://bugs.kde.org/show_bug.cgi?id=481688
--- Comment #5 from fililip ---
Note: this only seems to affect xwayland apps. Native wayland ones don't have
this issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481716
--- Comment #3 from fililip ---
I have observed something in dmesg when using the Nvidia card with KWin:
[ 303.194078] [drm] [nvidia-drm] [GPU ID 0x0c00] Framebuffer memory not
appropriate for scanout
[ 303.194258] [drm] [nvidia-drm] [GPU ID
https://bugs.kde.org/show_bug.cgi?id=481716
--- Comment #5 from fililip ---
Only happens on startplasma-wayland with the env var or connecting a display to
the nvidia card, gets displayed only two times, making apps fullscreen doesn't
trigger it again. I just thought it's relevant
https://bugs.kde.org/show_bug.cgi?id=481716
--- Comment #1 from fililip ---
Note: I set my CPU frequency to 1750MHz minimum, now the framedropping doesn't
occur with cursor motion, but there are observable CPU usage spikes on one
thread when anything's happening on the screen.
--
You
https://bugs.kde.org/show_bug.cgi?id=481716
--- Comment #2 from fililip ---
The stutters still occur on Plasma 6.0.0. Will the explicit sync protocol
address this? (I do not have a problem with apps glitching out on xwayland,
just desktop wide stutters, even in native Wayland apps.)
--
You
https://bugs.kde.org/show_bug.cgi?id=481716
fililip changed:
What|Removed |Added
Version|5.93.0 |6.0.0
--- Comment #9 from fililip ---
Alright, I
https://bugs.kde.org/show_bug.cgi?id=481716
Bug ID: 481716
Summary: KWin drops frames on nvidia (Wayland)
Classification: Plasma
Product: kwin
Version: 5.93.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=481716
--- Comment #8 from fililip ---
> (which is not the case for Intel)
Interesting. I did not have these problems on an Arc A750 at all, even though I
was also doing dual-GPU back when I still had it.
What's more, these stutters do not happen on gn
https://bugs.kde.org/show_bug.cgi?id=486081
fililip changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=485425
--- Comment #15 from fililip ---
Changing the window open/close animation to another mode/disabling and
re-enabling it (or, to be safe, disabling and re-enabling all desktop effects
one by one) seems to fix this issue entirely.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=485425
--- Comment #17 from fililip ---
Does switching back to the Glide effect bring the issue back for you? For me it
does; I have to use Scale.
--
You are receiving this mail because:
You are watching all bug changes.
66 matches
Mail list logo
