err:ninecfg:nine_get removing dead symlink about wine-nine-standalone

[jcmolero]

me too, just running the ninewinecfg the symlinks are gone, so I had to do them manually, but not sure if I am pointing at the right files (d3d9-nine.dll.so) but game has been running anyway
ln -s /usr/lib32/wine/d3d9-nine.dll.so ~/.wine/drive_c/windows/syswow64/d3d9.dll
ln -s /usr/lib/wine/d3d9-nine.dll.so ~/.wine/drive_c/windows/system32/d3d9.dll

Also getting this.

[Espionage724]

Can also confirm this with Staging 4.8; but it works fine on 4.7 after downgrading to it.

[Charadon]

What's worse, is that I found that installing galliumnine through winetricks in a new prefix doesn't create the symlink at all.

[jcmolero]

Can also confirm this with Staging 4.8; but it works fine on 4.7 after downgrading to it.

can you upload the symlinked d3d9.dll inside ~/.wine/drive_c/windows/system32/ please?

[Charadon]

@jcmolero d3d9.dll is supposed to symlink to d3d9-nine.dll in the same folder. Though, I don't think that matters since I don't think gallium-nine even works anymore in 4.8. Atleast it doesn't for me.

[axeldavy]

I guess wine will need to be bisected to find the fauly commit and understand the behaviour change.

[Charadon]

Wasn't wine replacing their direct3d9 renderer from OpenGL to Vulkan? If so, something they did could be the reason. But I feel like i'm mis-remembering.

[jcmolero]

I guess wine will need to be bisected to find the fauly commit and understand the behaviour change.

in fact wine shows this everytime i run winecfg:
000d:err:menubuilder:init_xdg error looking up the desktop directory

[Charadon]

@jcmolero That has to do with your applications menu in your Desktop Environment. iirc

[jcmolero]

@jcmolero That has to do with your applications menu in your Desktop Environment. iirc

yes, but in 4.7 has not shown, just after updating

[Charadon]

So, after doing some testing. I can confirm that gallium nine on 4.8 staging is completely broken for me. Applications that use Direct3d9 will just close instantly. The workaround was to downgrade back to 4.7

[jcmolero]

managed to downgrade to wine staging 3.7, checked the symlinks and actually they can be done in case of using 3.8:
ln -s /usr/bin/../lib32/wine/d3d9-nine.dll.so ~/.wine/drive_c/windows/syswow64/d3d9.dll
ln -s /usr/bin/../lib/wine/d3d9-nine.dll.so ~/.wine/drive_c/windows/system32/d3d9.dll

[Charadon]

@jcmolero I've done that, the issue is that, atleast for me, galliumnine just refuses to work on 4.8

[soredake]

https://bugs.winehq.org/show_bug.cgi?id=47160 (fixed by wine-staging/wine-staging@92cc781)

[Charadon]

Oh sweet, so I should just wait until 4.9 before updating wine-staging again?

[axeldavy]

Nice finding, but then why is there report vanilla is affected too ? had it the same commit ?

[Myrddin-Wyllt]

@axeldavy Charadon neglected to mention that they were using Wine Staging, not Vanilla & I don't believe anyone else mentioned Vanilla; so this issue must lie with Wine Staging specifically.

The OP didn't reveal their use of Staging until this comment:

Oh sweet, so I should just wait until 4.9 before updating wine-staging again?

This issue affects everyone using 4.8 Staging so far as I can tell.

[Charadon]

@Myrddin-Wyllt Gah, I re-read my first post probably 5 times and failed to mention I was on staging. Sorry about that. If this is an issue with staging, then perhaps its time to close this issue?

[axeldavy]

Sure, please reopen if the problem comes back. Thanks for reporting and investigating.