-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Corrupted Vulkan windows and Gnome File Manager with 2024.Q4.2+ #393
Comments
This is a known issue upstream with GTK I believe. I think you can force GTK apps to use an alternative renderer besides Vulkan in the mean time. |
I've tracked this down to the PAL setting |
I can confirm that using 2024.Q4.3, and putting the followingent content into
Especially the black border as seen in the second capture can be mitigated by expanding the window to fill the screen. |
The black border issue is fixed with 2025.Q1.1 release, please check it. |
2025.Q1.1 fixes the black border issue, but seems to be missing the m_presentOnSameGpu fix so the windows are corrupted for me. |
The m_presentOnSameGpu fix caused a performance regression so is not included in this release. it will be in next release |
The latest fix has been ported into dev branch. |
Yes, can confirm this works for me 👍 |
When updating from amdvlk 2024.Q4.1 to amdvlk 2024.Q4.2 (same issue persists with 2024.Q4.3), I started having problems with corrupted gnome file manager window and also simple vulkan applications (for example, vkgears is busted). The rest of the desktop and my usual applications (terminal, firefox) work fine.
On a related note, Gnome File manager still doesn't look 100% right with 2024.Q4.1, but it is usable:
System is running Arch Linux:
linux 6.12.7.arch1-1
linux-firmware 20241210.b00a7f7e-1
mesa 1:24.3.2-1
The system is a Asus G15 AMD Advantage laptop (G513QY) which has both integrated (Ryzen 9 5900HX, Vega 8 GPU) and discrete (RX 6800M) GPUs. The applications all appear to be using the discrete GPU (e.g. according to
vkgears -info
).The text was updated successfully, but these errors were encountered: