No content rendered after libdrm update

[tdltdc]

On 2023-10-16 apt upgraded (among others) the following libdrm related packages:

libdrm-nouveau2:amd64 (2.4.115-1, 2.4.116-1)
libdrm-common:amd64 (2.4.115-1, 2.4.116-1)
libdrm-amdgpu1:amd64 (2.4.115-1, 2.4.116-1)
libdrm-radeon1:amd64 (2.4.115-1, 2.4.116-1)
libdrm2:amd64 (2.4.115-1, 2.4.116-1)
libdrm-intel1:amd64 (2.4.115-1, 2.4.116-1)

After this upgrade, Joplin fails to render its content. Screenshot:

Related bug reports:
ferdium/ferdium-app#1265 (comment)
#8923 (not a duplicate, because I was running Joplin 2.12.18 before the libdrm upgrade)

Environment

Joplin version: 2.12.18
Platform: Linux
OS specifics: Debian Sid

Steps to reproduce

1. Run Debian Sid and have current version of Joplin installed
2. Launch and close Joplin
3. Upgrade certain libdrm packages (see above)
4. Launch Joplin again. Content is now not rendered / blank.

Describe what you expected to happen

Content being rendered.

Logfile

Couldn't set debug logging due to broken GUI. Here's the start of the output of "./.joplin/Joplin.AppImage".

appimage_output.txt

[tdltdc]

As suggested in ferdium/ferdium-app#1265 (comment), running rm -rf .config/Joplin/GPUCache/ and then starting Joplin again fixes the issue.

[PaulVanSchayck]

Flatpak suffers the same. The directory is located (by default) at:

~/.var/app/net.cozic.joplin_desktop/config/Joplin/GPUCache/

[TechD123]

Thanks @PaulVanSchayck, you saved me!

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[tdltdc]

Bumped into once this in the last couple of days again on Joplin 2.12.19, so this doesn't appear to be solved.

[github-actions]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? If you require support or are requesting an enhancement or feature then please create a topic on the Joplin forum. This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions.

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, feel free to create a new issue with up-to-date information.