Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[(custom) Wine bug?] - Not recognizing directories (in Vortex) #312

Closed
frostworx opened this issue Sep 30, 2021 · 3 comments
Closed

[(custom) Wine bug?] - Not recognizing directories (in Vortex) #312

frostworx opened this issue Sep 30, 2021 · 3 comments

Comments

@frostworx
Copy link
Collaborator

frostworx commented Sep 30, 2021

While testing which wine version works (best) with winetricks dotnet48 (vanilla wine-6.16 & wine-6.17 do, wine-6.18 has below upstream bug, and staging fails)
I found a strange bug in several wine variants/versions:

When selecting any directory in a vortex dialog, vortex opens a requester, complaining with
"The selection contains an object which is no directory" (free translated)

Tested affected wine versions are:

Working wine versions:

This probably can be broken down to a more simple example to reproduce, but I haven't found a simple "open directory" exe.
dotnet is not required to reproduce this.

Steps to reproduce:

  • (download this vortex version 1.4.15)
  • mkdir /tmp/testvort
  • WINEDEBUG=-all WINEPREFIX=/tmp/testvort/ "/path/to/tested/wine" vortex-setup-1.4.15.exe
  • select a directory in any dialog (f.e. settings/downloads, or manage game → select its installation folder)

Result:
The selected directory is rejected with
"The selection contains an object which is no directory"

Expected result:
The selected directory should be accepted

WINEDEBUG=-all is required, as else Vortex hangs in an endless
02b4:fixme:taskschd:regtasks_get_Item 000000000C52A810,000000000081C140 {VT_I4: 339303},000000000081C0A0: stub loop

@frostworx
Copy link
Collaborator Author

Very likely the upstream bug: https://bugs.winehq.org/show_bug.cgi?id=51816

@frostworx
Copy link
Collaborator Author

@Kron4ek found the regression and reported it upstream. 👍

@frostworx
Copy link
Collaborator Author

fixed upstream: https://bugs.winehq.org/show_bug.cgi?id=51816
Thanks to anybody involved 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant