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

Winetricks GUI not working with macOS zenity fork #2240

Open
vapidinfinity opened this issue Jul 7, 2024 · 1 comment
Open

Winetricks GUI not working with macOS zenity fork #2240

vapidinfinity opened this issue Jul 7, 2024 · 1 comment

Comments

@vapidinfinity
Copy link

This is an update on #2227 since it's closed at this time.
Please see ncruces/zenity#103 (comment).

Logs:

winetricks                    
warning: taskset/cpuset not available on your platform!
------------------------------------------------------
warning: You are using a 64-bit WINEPREFIX. Note that many verbs only install 32-bit versions of packages. If you encounter problems, please retest in a clean 32-bit WINEPREFIX before reporting a bug.
------------------------------------------------------
------------------------------------------------------
warning: You apppear to be using Wine's new wow64 mode. Note that this is EXPERIMENTAL and not yet fully supported. If reporting an issue, be sure to mention this.
------------------------------------------------------
Using winetricks 20240105 - sha256sum: 8f28985b06e9e04b5268e2aef3429b2a0f6abd4fd12c4a30472dfe66355128fa with wine-9.0-rc4 (Staging) and WINEARCH=win64
Running on OSX, but DISPLAY is not set...probably using Mac Driver.
winetricks GUI enabled, using zenity zenity v0.10.12 darwin/amd64
https://github.com/ncruces/zenity
flag provided but not defined: -hide-column

EOF

Using macOS 14.4.1, M1 Pro Using zenity 0.10.12 (latest) and brew (latest) both don't work.

@austin987
Copy link
Contributor

The current GUI depends on using --hide-columns (so it looks cleaner)
screen1
screen1-nohide
screen2
screen2-nohide

It's a design choice, not a bug. The bug IMO is a fork that uses the same binary name, but doesn't support the same options.

While I understand that they don't want to support it because osascript doesn't make it easy, then IMO it's up to them to find a workaround. It's not reasonable to expect all other projects to make changes to support a fork that is less featureful than the original.

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

2 participants