WINE on Slackware64

cwizardone · 11-10-2023, 09:03 PM

Wine development release 8.20 is now available.

Quote:

What's new in this release:
- More DirectMusic implementation.
- Protocol associations exported to the Unix desktop.
- Code cleanups in preparation for code freeze.
- Various bug fixes.

https://www.winehq.org/announce/8.20

According to Phoronix, in this release is a fix for a 13 year old bug.
For the story please see, https://www.phoronix.com/news/Wine-8.20-Released

cwizardone · 11-24-2023, 06:27 PM

The Wine development release 8.21 is now available.

Quote:

What's new in this release:
- High-DPI scaling and initial Vulkan support in the Wayland driver.
- Beginnings of support for ARM64EC target.
- Updates to the locale database.
- Various bug fixes.

https://www.winehq.org/announce/8.21

cwizardone · 12-08-2023, 06:22 PM

The Wine development release 9.0-rc1 is now available.

Quote:

This is the first release candidate for the upcoming Wine 9.0. It
marks the beginning of the yearly code freeze period. Please give this
release a good testing and report any issue that you find, to help us
make the final 9.0 as good as possible.

What's new in this release:
- Bundled vkd3d upgraded to version 1.10.
- Support for DH encryption keys with a recent GnuTLS.
- Keyboard layouts support in the Wayland driver.
- Various bug fixes.

https://www.winehq.org/announce/9.0-rc1

cwizardone · 12-22-2023, 07:40 PM

The Wine development release 9.0-rc3 is now available.

Quote:

What's new in this release:
- Bug fixes only, we are in code freeze.

https://www.winehq.org/announce/9.0-rc3

random_guy · 12-26-2023, 05:15 PM

Quote:

Originally Posted by rkelsen

If you don't want multi-lib, but want to run 32 bit Windows stuff, you could try Conty:

https://github.com/Kron4ek/Conty

I use it to play StarCraft, Warcraft 3, etc. I don't have multi-lib.

Thanks for posting this, it piqued my interest. I downloaded conty and played around with some of the environment variables.
I enabled #1 (below) and tried to launch conty.sh and it complained that I didn't have bubblewrap (bwrap) installed. I could run it with bwrap that comes with conty.
I downloaded and compiled bubblewrap but haven't installed it yet,

Which of the env. variables below (if any) do you recommend setting? I'd rather have it sandboxed with the least privs possible, if I can get away with it.
I intend to play some games locally SANDBOX_LEVEL 3 maybe good for that.

1) USE_SYS_UTILS
2) SANDBOX
3) SANDBOX_LEVEL
4) DISABLE_NET
5) HOME_DIR

I'm a complete conty n00b, so any tips, comments or advice would be greatly appreciated.

TIA

Kron4ek · 12-29-2023, 03:31 PM

Quote:

Originally Posted by random_guy

Thanks for posting this, it piqued my interest. I downloaded conty and played around with some of the environment variables.
I enabled #1 (below) and tried to launch conty.sh and it complained that I didn't have bubblewrap (bwrap) installed. I could run it with bwrap that comes with conty.
I downloaded and compiled bubblewrap but haven't installed it yet,

Which of the env. variables below (if any) do you recommend setting? I'd rather have it sandboxed with the least privs possible, if I can get away with it.
I intend to play some games locally SANDBOX_LEVEL 3 maybe good for that.

1) USE_SYS_UTILS
2) SANDBOX
3) SANDBOX_LEVEL
4) DISABLE_NET
5) HOME_DIR

I'm a complete conty n00b, so any tips, comments or advice would be greatly appreciated.

TIA

SANDBOX_LEVEL 3 uses Xephyr and does not support graphics acceleration so most games either won't work with it or will be very slow. I recommend to use level 2 instead, and also DISABLE_NET for singleplayer games that don't require internet connection. This combination of environment variables decently isolates applications:

Code:

HOME_DIR=~/sandboxed_home DISABLE_NET=1 SANDBOX=1 SANDBOX_LEVEL=2 ./conty.sh ...

In this case applications won't be able to use the internet, they won't see your real home directory and will use ~/sandboxed_home directory instead, you will need to put there any games or files (if any) that you wan't to see inside the container.

Kron4ek · 12-29-2023, 03:31 PM

Quote:

Originally Posted by random_guy

Thanks for posting this, it piqued my interest. I downloaded conty and played around with some of the environment variables.
I enabled #1 (below) and tried to launch conty.sh and it complained that I didn't have bubblewrap (bwrap) installed. I could run it with bwrap that comes with conty.
I downloaded and compiled bubblewrap but haven't installed it yet,

Which of the env. variables below (if any) do you recommend setting? I'd rather have it sandboxed with the least privs possible, if I can get away with it.
I intend to play some games locally SANDBOX_LEVEL 3 maybe good for that.

1) USE_SYS_UTILS
2) SANDBOX
3) SANDBOX_LEVEL
4) DISABLE_NET
5) HOME_DIR

I'm a complete conty n00b, so any tips, comments or advice would be greatly appreciated.

TIA

SANDBOX_LEVEL 3 uses Xephyr and does not support graphics acceleration so most games either won't work with it or will be very slow. I recommend to use level 2 instead, and also DISABLE_NET for singleplayer games that don't require internet connection. This combination of environment variables decently isolates applications:

Code:

HOME_DIR=~/sandboxed_home DISABLE_NET=1 SANDBOX=1 SANDBOX_LEVEL=2 ./conty.sh ...

In this case applications won't be able to use the internet, they won't see your real home directory and will use ~/sandboxed_home directory instead, you will need to put there any games or files (if any) that you wan't to see inside the container.

rkelsen · 12-29-2023, 05:40 PM

Quote:

Originally Posted by random_guy

Which of the env. variables below (if any) do you recommend setting? I'd rather have it sandboxed with the least privs possible, if I can get away with it.

It runs unprivileged... so that's how I run it! I'm only running Conty as a user, without setting any of the variables you asked about.

random_guy · 12-29-2023, 10:21 PM

Thanks Kron4ek and rkelsen for the comments and tips. Kron4ek's recommendations on the env vars was exactly what I was looking for.

cwizardone · 01-06-2024, 09:32 AM

The Wine development release 9.0-rc4 is now available.
The change log and a list of 17 bug fixes can be found at, https://gitlab.winehq.org/wine/wine/...s/wine-9.0-rc4

cwizardone · 01-16-2024, 07:53 PM

Wine-9.0 Stable has been released.

Quote:

The Wine team is proud to announce that the stable release Wine 9.0 is now available.
This release represents a year of development effort and over 7,000 individual changes. It contains a large number of improvements that are listed below. The main highlights are the new WoW64 architecture and the experimental Wayland driver.........

Read all about it at, https://gitlab.winehq.org/wine/wine/-/releases/wine-9.0

zeebra · 01-17-2024, 05:44 AM

Quote:

All modules that call a Unix library contain WoW64 thunks to enable calling
the 64-bit Unix library from 32-bit PE code. This means that it is possible to
run 32-bit Windows applications on a purely 64-bit Unix installation. This is
called the new WoW64 mode, as opposed to the old WoW64 mode where 32-bit
applications run inside a 32-bit Unix process.

Wow..

business_kid · 01-17-2024, 12:12 PM

I read but didn't understand the stuff about running windows binaries on Arm64. They were talking about ARMEC and ARMX and (external) emulation libraries and lost me. I gather the ARMEC is 32bit? What did they actually say?

rkelsen · 01-17-2024, 01:12 PM

Quote:

Originally Posted by zeebra

Wow..

*Wow64

zeebra · 01-17-2024, 05:41 PM

Quote:

Originally Posted by rkelsen

*Wow64

It's been my biggest "problem" with wine for a long time. Dealing with 64bit versions and 32bit versions (especially when GNU/Linux was transitioning from 32bit to 64bit) and compatibility with win32 and win64 was just confusing to a casual. All ofcourse because Windows still runs 32 bit stuff, but nonetheless a bit of a braintwister on the occasions that I have installed/used Wine.

This is just great..

rkelsen · 01-17-2024, 06:00 PM

Quote:

Originally Posted by zeebra

It's been my biggest "problem" with wine for a long time. Dealing with 64bit versions and 32bit versions (especially when GNU/Linux was transitioning from 32bit to 64bit) and compatibility with win32 and win64 was just confusing to a casual. All ofcourse because Windows still runs 32 bit stuff, but nonetheless a bit of a braintwister on the occasions that I have installed/used Wine.

This is just great..

Yeah, up to now multi-lib has pretty much been a requirement. I'm not going to repeat myself, but there is a simple drop-in solution to this problem which I've suggested several times in this thread and others about wine.

With that said, this is a truly great development. The wine project is one which I've been following since I first started using Linux, and it is always pleasing to see such significant advancements being made. Their comment about 16 bit support made me chuckle. The project is in excellent hands!