[GH-ISSUE #5683] [Bug] Using Appflowy 0.61 causes kwin reset (graphical effects reset) under Plasma6 and shows graphical glitches #2531

Open
opened 2026-03-23 21:23:09 +00:00 by mirror · 7 comments
Owner

Originally created by @AkechiShiro on GitHub (Jul 4, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/5683

Bug Description

The UI seems to glitch when sometimes updating the UI, the glitch shows like dark spots/glitches on screen.

My hardware is an AMD Framework laptop, and I did not see any glitches with any other software on my current kernel/linux-firmware (6.6.36, 20240610).

How to Reproduce

Just launch Appflowy under Plasma6 (Wayland)

Expected Behavior

No graphical glitches and no kwin resets of the Desktop environment.

Operating System

NixOS Uakari 24.05 (stable channel)

AppFlowy Version(s)

0.61

Screenshots

No response

Additional Context

I couldn't catch a screenshot as it is not easily reproductible but I found out it is most likely a bug upstream, in my dmesg, I saw this :

[145727.279926] amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:1 pasid:32786, for process AppFlowy pid 323363 thread AppFlowy:cs0 pid 323369)
[145727.279934] amdgpu 0000:c1:00.0: amdgpu:   in page starting at address 0x000000003e000000 from client 10
[145727.279937] amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00101430
[145727.279938] amdgpu 0000:c1:00.0: amdgpu:     Faulty UTCL2 client ID: SQC (data) (0xa)
[145727.279940] amdgpu 0000:c1:00.0: amdgpu:     MORE_FAULTS: 0x0
[145727.279941] amdgpu 0000:c1:00.0: amdgpu:     WALKER_ERROR: 0x0
[145727.279942] amdgpu 0000:c1:00.0: amdgpu:     PERMISSION_FAULTS: 0x3
[145727.279943] amdgpu 0000:c1:00.0: amdgpu:     MAPPING_ERROR: 0x0
[145727.279944] amdgpu 0000:c1:00.0: amdgpu:     RW: 0x0
[145737.362555] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered
Originally created by @AkechiShiro on GitHub (Jul 4, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/5683 ### Bug Description The UI seems to glitch when sometimes updating the UI, the glitch shows like dark spots/glitches on screen. My hardware is an AMD Framework laptop, and I did not see any glitches with any other software on my current kernel/linux-firmware (6.6.36, 20240610). ### How to Reproduce Just launch Appflowy under Plasma6 (Wayland) ### Expected Behavior No graphical glitches and no kwin resets of the Desktop environment. ### Operating System NixOS Uakari 24.05 (stable channel) ### AppFlowy Version(s) 0.61 ### Screenshots _No response_ ### Additional Context I couldn't catch a screenshot as it is not easily reproductible but I found out it is most likely a bug upstream, in my dmesg, I saw this : ``` [145727.279926] amdgpu 0000:c1:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:1 pasid:32786, for process AppFlowy pid 323363 thread AppFlowy:cs0 pid 323369) [145727.279934] amdgpu 0000:c1:00.0: amdgpu: in page starting at address 0x000000003e000000 from client 10 [145727.279937] amdgpu 0000:c1:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00101430 [145727.279938] amdgpu 0000:c1:00.0: amdgpu: Faulty UTCL2 client ID: SQC (data) (0xa) [145727.279940] amdgpu 0000:c1:00.0: amdgpu: MORE_FAULTS: 0x0 [145727.279941] amdgpu 0000:c1:00.0: amdgpu: WALKER_ERROR: 0x0 [145727.279942] amdgpu 0000:c1:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [145727.279943] amdgpu 0000:c1:00.0: amdgpu: MAPPING_ERROR: 0x0 [145727.279944] amdgpu 0000:c1:00.0: amdgpu: RW: 0x0 [145737.362555] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered ```
Author
Owner

@AkechiShiro commented on GitHub (Jul 4, 2024):

image

<!-- gh-comment-id:2208883385 --> @AkechiShiro commented on GitHub (Jul 4, 2024): ![image](https://github.com/AppFlowy-IO/AppFlowy/assets/14914796/2d1b6c47-70f5-473b-b572-299a1673bb19)
Author
Owner

@AkechiShiro commented on GitHub (Jul 4, 2024):

Maybe linked to this issue upstream : https://gitlab.freedesktop.org/drm/amd/-/issues/3470

<!-- gh-comment-id:2208944142 --> @AkechiShiro commented on GitHub (Jul 4, 2024): Maybe linked to this issue upstream : https://gitlab.freedesktop.org/drm/amd/-/issues/3470
Author
Owner

@AkechiShiro commented on GitHub (Jul 4, 2024):

Weirdly enough, this isn't reproducible under release 0.57

<!-- gh-comment-id:2209124321 --> @AkechiShiro commented on GitHub (Jul 4, 2024): Weirdly enough, this isn't reproducible under release `0.57`
Author
Owner

@annieappflowy commented on GitHub (Oct 1, 2024):

Thanks, @AkechiShiro , for the update. Closing this issue

<!-- gh-comment-id:2385694486 --> @annieappflowy commented on GitHub (Oct 1, 2024): Thanks, @AkechiShiro , for the update. Closing this issue
Author
Owner

@AkechiShiro commented on GitHub (Oct 1, 2024):

Hello @annieappflowy I'm not sure if that still shows up on the latest release, will retest at some point, but it was fixed in an older release but not on the newer 0.61 and up I believe.

<!-- gh-comment-id:2386502197 --> @AkechiShiro commented on GitHub (Oct 1, 2024): Hello @annieappflowy I'm not sure if that still shows up on the latest release, will retest at some point, but it was fixed in an older release but not on the newer 0.61 and up I believe.
Author
Owner

@AkechiShiro commented on GitHub (Nov 6, 2024):

I was able to reproduce under latest release 0.7.1, if I use --no-gpu-sandbox there is no glitch anymore, might be an upstream issue in Electron ?

Note : My hardware is AMD only (AMD Ryzen 7 7840U w/ Radeon 780M Graphics)
I am on Linux Kernel release 6.11.5

<!-- gh-comment-id:2460494883 --> @AkechiShiro commented on GitHub (Nov 6, 2024): I was able to reproduce under latest release 0.7.1, if I use `--no-gpu-sandbox` there is no glitch anymore, might be an upstream issue in Electron ? Note : My hardware is AMD only (AMD Ryzen 7 7840U w/ Radeon 780M Graphics) I am on Linux Kernel release 6.11.5
Author
Owner

@annieappflowy commented on GitHub (Jan 3, 2025):

@AkechiShiro , we don't use Electron

<!-- gh-comment-id:2569187967 --> @annieappflowy commented on GitHub (Jan 3, 2025): @AkechiShiro , we don't use Electron
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#2531
No description provided.