Possible regression after kernel 7.0.4 / mesa 26.0.6 update (Wine/Proton)

Ask Fedora
, , ,
1

I seem to be hitting an issue after recent kernel and mesa package updates on F44 Silverblue where several games launched via Proton GE seem to stall and have to be force terminated.

Launching a previous deployment with kernel 6.19.14 and mesa 26.0.5 seems to work without any issues.

The updated packages were

kernel 6.19.14-300.fc44 -> 7.0.4-200.fc44
kernel-core 6.19.14-300.fc44 -> 7.0.4-200.fc44
kernel-devel 6.19.14-300.fc44 -> 7.0.4-200.fc44
kernel-devel-matched 6.19.14-300.fc44 -> 7.0.4-200.fc44
kernel-modules 6.19.14-300.fc44 -> 7.0.4-200.fc44
kernel-modules-core 6.19.14-300.fc44 -> 7.0.4-200.fc44
kernel-modules-extra 6.19.14-300.fc44 -> 7.0.4-200.fc44
kernel-tools 6.19.14-300.fc44 -> 7.0.4-200.fc44
kernel-tools-libs 6.19.14-300.fc44 -> 7.0.4-200.fc44
mesa-dri-drivers 26.0.5-3.fc44 -> 26.0.6-2.fc44
mesa-dri-drivers 26.0.5-3.fc44 -> 26.0.6-2.fc44
mesa-filesystem 26.0.5-3.fc44 -> 26.0.6-2.fc44
mesa-filesystem 26.0.5-3.fc44 -> 26.0.6-2.fc44
mesa-libEGL 26.0.5-3.fc44 -> 26.0.6-2.fc44
mesa-libEGL 26.0.5-3.fc44 -> 26.0.6-2.fc44
mesa-libEGL-devel 26.0.5-3.fc44 -> 26.0.6-2.fc44
mesa-libGL 26.0.5-3.fc44 -> 26.0.6-2.fc44
mesa-libGL 26.0.5-3.fc44 -> 26.0.6-2.fc44
mesa-libgbm 26.0.5-3.fc44 -> 26.0.6-2.fc44
mesa-libgbm 26.0.5-3.fc44 -> 26.0.6-2.fc44
mesa-libgbm-devel 26.0.5-3.fc44 -> 26.0.6-2.fc44
mesa-vulkan-drivers 26.0.5-3.fc44 -> 26.0.6-2.fc44
mesa-vulkan-drivers 26.0.5-3.fc44 -> 26.0.6-2.fc44

So far I have not been able to find anything specific looking at kernel messages or logs from proton that indicate what could cause this. Has anyone else run in to this problem or have any suggestions?

2

Are you saying…

Only mesa regressed and the new kernel is fine with old mesa?

Both new mesa and new kernel together cause the regression?

3

I’m not certain that there is a regression, but my pinned deployment with kernel 6.19.14 and mesa 26.0.5 before the update launches the games normally. The updated deployment with kernel 7.0.4 and mesa 26.0.6 seems to reach the same point in the launch process through proton without the games actually launching.

Unfortunately I haven’t been able to test them separately as downgrading the packages individually doesn’t seem to work for me. Trying rpm-ostree override replace produces several conflicts with mesa-vulkan-drivers.

I did find a similar issue posted here about six months ago so it’s possible it could be an issue with mesa.

5

After some more digging I found a difference in the journalctl output of the upgraded linux/mesa deployment that isn’t present in the output of the previous deployment when trying to run a game:

...
May 11 17:51:59 user audit[10299]: AVC avc:  denied  { execmem } for  pid=10299 comm="Game" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:59 user audit[10299]: AVC avc:  denied  { execmem } for  pid=10299 comm="Game" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:59 user audit[10299]: AVC avc:  denied  { execmem } for  pid=10299 comm="Game" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:58 user audit[10299]: AVC avc:  denied  { execmem } for  pid=10299 comm="Game" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:58 user audit[10299]: AVC avc:  denied  { execmem } for  pid=10299 comm="Game" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:57 user audit[10277]: AVC avc:  denied  { execmem } for  pid=10277 comm="explorer.exe" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:57 user audit[10277]: AVC avc:  denied  { execmem } for  pid=10277 comm="explorer.exe" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:55 user audit[10217]: AVC avc:  denied  { execmem } for  pid=10217 comm="python3" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:55 user audit[10217]: AVC avc:  denied  { execmem } for  pid=10217 comm="python3" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
...
May 11 17:51:40 user audit[6388]: AVC avc:  denied  { execmem } for  pid=6388 comm="vulkaninfo" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:40 user audit[6388]: AVC avc:  denied  { execmem } for  pid=6388 comm="vulkaninfo" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:39 user audit[6353]: AVC avc:  denied  { execmem } for  pid=6353 comm="vulkaninfo" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:39 user audit[6353]: AVC avc:  denied  { execmem } for  pid=6353 comm="vulkaninfo" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:39 user audit[6340]: AVC avc:  denied  { execmem } for  pid=6340 comm="lutris" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:39 user audit[6340]: AVC avc:  denied  { execmem } for  pid=6340 comm="lutris" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:38 user audit[6348]: AVC avc:  denied  { execmem } for  pid=6348 comm="glxinfo" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:38 user audit[6348]: AVC avc:  denied  { execmem } for  pid=6348 comm="glxinfo" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:38 user audit[6348]: AVC avc:  denied  { execmem } for  pid=6348 comm="glxinfo" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
May 11 17:51:38 user audit[6348]: AVC avc:  denied  { execmem } for  pid=6348 comm="glxinfo" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=process permissive=0
...

Not sure if it is relevant but from what I could gather, AVC is related to SELinux and permission handling. Maybe something that prevents it from launching?

6

Looks like you have selinux issues.
To have things working you need a fix for those selinux issues.
I’m not a selinux expert…

7

Thanks for taking the time to respond, not really sure what is happening here.

I decided to try a clean install of F44 Silverblue on the same machine only adding nvidia drivers from RPM Fusion (595.71.05-1.fc44) and running the game through Proton GE v34 but still had the same issue.

I managed to downgrade the mesa packages to 26.0.5 using

rpm-ostree override replace https://bodhi.fedoraproject.org/updates/FEDORA-2026-ddabe5d37f

which didn’t help either. I restored the original mesa packages and downgraded only the kernel to 6.19.14 using

rpm-ostree override replace https://bodhi.fedoraproject.org/updates/FEDORA-2026-3470601fbf

and the games launched. So I guess it’s related to the kernel update somehow. If it’s a kernel problem or some issue with the nvidia driver or proton I don’t know.

It doesn’t seem to be a widespread problem so I guess I’m either hitting a rare bug or it’s some sort of edge case. If someone is able to help with pointing me in the right direction of what to look for would be greatly appreciated. I’m not sure if a bug report to kernel developers is warranted.

8

Kernel bug report with information about your hardware is the way to go. Maybe try reporting this upstream depending on your GPU.

9

A late update, but I have at least gotten in working again. Either by disabling the NVAPI or switching to proton-cachyos. So I guess something with the kernel update broke the current Proton Experimental / Proton GE for those games.

Either way, thanks for the suggestions!