What "program" are you talking about and what is even your actual problem?
Sorry but I literally don't understand what this is supposed to be about at all.
wine dxdiag.exe works fine on my end.
This only happens to DirectX applications they are not displaying anything. Not functioning or not working correctly. Excuse me the convenience. I'll try to be as clear as i can.
When i run dxdiag i get commandline output which seems to be functioning but also no 'window' and no 'icon' in the taskbar.
I have purged and reinstalled the wine prefix and wine packages but it did not resolve this issue.
I was able to run wine vkcube.exe the testapplication from the Vulkan SDK.
I mean, it even says that it doesn't create a window?
0134:fixme:dxdiag:wWinMain Information dialog is not implemented
not sure what the expectation is here, in order for you to see a window and a task bar icon, the application has to be programmed in such a way to actually create a window and a task bar icon, which this is not. wine's dxdiag is a command line application only.
I expected the dxdiag window to pop up and might display some information regarding Wine/DirectX handling of Display configuration to trace trouble i am having with some of the games i play on wine run but have stopped functioning.
Elder Scrolls Online gave a AssertionError in getDeviceMemoryRequirement
Borderlands 3 - Runs but nothing happens, has ran before. No errors. Task visible in task manager and top.
World of Warcraft - Run nothing happns, has ran before. No errors. Task visible in task manager and top.
Fallout4 - Black screen. Has worked with F4se using a startup script.
Battle.net - Runs working.
Own test applications - run
VkCube.exe - runs in Wine with no problem.
Steam - Runs
Manually wiped SPIRV/GLSL shader cache but there could be remnant left unhandled.
I have been having a lot of trouble with Vulkan corrupting installation on Windows 10 with the standard driver. I have to reinstall the computer every 3 months due to the current circumstances. Of all times the driver tries to map memory from a onboard GPU which is not possible on my computer.
At this moment due to the frequency of the BSOD's i am not able to access my win10 partition due to recovery loops.
yeah idk, sounds like something on your setup is fucked. Not much to go on here.
Yes.... I have really outdone myself this time.
$ wmctrl -l
0x0140001e -1 pretty_name.home Desktop @ QRect(0,0 1920x1080)
0x01400036 -1 pretty_name.home plasmashell
0x0340000e 0 pretty_name.home ~ : bash — Konsole
0x03800000 0 N/A N/A
Segmentation Fault
rt_sigreturn({mask=[]}) = 3221225477
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x0000000000000000 in ?? ()
@jorikdeleeuw Did you figure out the issue?
A regression / driver bug introduced by Pebkag 1d1-0t abuse of logical query interrupt.
This has been 'solved' as of the introduction of a new version of the OS. An upgrade solved this problem.
But other things do reintroduce severely damaging crashes such as driver Overrides requiring the usage of Vulkan or are written in Vulkan because it 'actually' does improve everything even on Older Cards still do "Swap chaining" on motherboards that can not; this will shortcircuit.
Apparently something had corrupted PATH
I found out the problem here is not DXDiag but a regression caused by AMD drivers.
The official date which they was eventually solved was around 2 weeks after this.
Hi
Unfortunately DirectX on Fedora Linux 41 has corrupted after abrupt termination of active program and update and since then it has failed to properly display or communicate with X11.
Wine DXDIAG
wine +x11drv