Bug 1942655 - Wine programs no longer open when using vulkan
Summary: Wine programs no longer open when using vulkan
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 33
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-24 16:55 UTC by Hein-Pieter van Braam
Modified: 2021-03-30 23:47 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-03-30 23:47:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Hein-Pieter van Braam 2021-03-24 16:55:21 UTC
User-Agent:       Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:86.0) Gecko/20100101 Firefox/86.0
Build Identifier: 

when opening any wine program the following error is displayed:
1065.377:0068:006c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.

I have tried setting VK_ICD_FILENAMES both to the intel and the amd vulkan driver (this system has both an Intel and an AMD GPU). Neither works. When setting VK_ICD_FILENAMES to a non-existent file wine opens.

I have also tried uninstalling wine-dxvk and creating a new wineprefix. The same behavior occurs. This leads me to believe this is not a dxvk issue but a wider vulkan issue.

I have also tried running proton applications. None of them will open unless I set PROTON_USE_WINE3D3=1.

vkcube opens and runs as expected on both the intel and amd icds

Reproducible: Always

Steps to Reproduce:
1. Create an empty directory
2. Set WINEPREFIX to point to this empty directory
3. Run winecfg
Actual Results:  
1065.377:0068:006c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. is displayed. Wine program does not open

Expected Results:  
Wine program opens

This problem started to happen yesterday after an update. 

mesa-vulkan-drivers-20.3.4-2.fc33.x86_64
vulkan-loader-1.2.148.1-1.fc33.x86_64

Comment 1 Hein-Pieter van Braam 2021-03-24 16:58:43 UTC
Note that I tested proton because that is a wine version now shipped by Fedora. This is why I filed the bug against mesa and not wine.

Comment 2 Hein-Pieter van Braam 2021-03-24 17:02:51 UTC
(In reply to Hein-Pieter van Braam from comment #1)
> Note that I tested proton because that is a wine version now shipped by
> Fedora. This is why I filed the bug against mesa and not wine.

I meant NOT shipped by Fedora. My apologies.

Comment 3 Hein-Pieter van Braam 2021-03-30 13:43:34 UTC
I just installed the Mesa update to 20.3.5-1 but the problem persists.

Comment 4 Hein-Pieter van Braam 2021-03-30 23:47:38 UTC
After a reboot from 5.11.8-200 to 5.11.10-200 the problem seems to have fixed itself. (I had previously rebooted into 5.11.8-200 after I first encountered this problem). So I guess this is... 'fixed'? :)


Note You need to log in before you can comment on or make changes to this bug.