Closed bayazidbh closed 2 years ago
Hi, thanks to being so detailed.
Bottles should not look for the SysWoW64
path when installing in a 32-bit prefix, I'll implement this asap.
Btw this issue is already tracked here: https://github.com/bottlesdevs/Bottles/issues/713 but I'll keep this instead as it provide more details.
Describe the bug Problem with some dependencies on 32-bit bottle. Failed to install, then locks up the dependency tab.
Installation
To Reproduce Steps to reproduce the behavior:
Was able to replicate even after resetting all flatpak overrides and deleting bottle's ~/.var/app folder.
Expected behavior msxml6 exits with no issues.
Screenshots
Desktop (please complete the following information):
Additional context msxml6 installs just fine on 64-bit bottle. I looked in the c:/windows/system32 folder, and found that msxml.dll to msxml6r.dll is present, even without installing the dependency. To check some things, I also tried with mf.dll, and it seems to be the same - dependency installer locks up, error message in console, but mf*.dlls are already present in system32.
Judging by the error message, the file the dependency installer downloaded, and looking at c:/windows, it seems that the dependency installer pulled the 64-bit msxml6 installer, tried to install it, but can't because it's not a 64-bit windows prefix.
I also checked on dotnet35, just in case. That one seems to register just fine, even though it exits with an error message:
Clicked close.
It seems that there are already a number of 32-bit dependencies installed by default, so perhaps a message notifying that "On a 32-bit bottle, this is already intstalled," or disabling unneeded dependencies install if bottles entered a 32-bit bottle? Or maybe it's an issue with grabbing wrong installer or script?