Updating wine over ppa installs me 32bit instead of 64

[De1m0s]

I've followed the instruction for Linux Mint on https://wiki.winehq.org/Ubuntu to always get the newest wine version automatically.
This works so far on two pcs, but on one of them, this installs me only the 32 bit version (system is 64 bit) ???

Any idea to solve this?

[Bob Wya]

I've followed the instruction for Linux Mint on https://wiki.winehq.org/Ubuntu to always get the newest wine version automatically.
This works so far on two pcs, but on one of them, this installs me only the 32 bit version (system is 64 bit) ???

Any idea to solve this?

What's the output from:

Code: Select all

inxi --system --machine

on the "32-bit only" system...

Thanks
Bob

[De1m0s]

Code: Select all

inxi --system --machine

gives me error message.

inxi -F:
System: Host: chris-LinuxPC Kernel: 4.13.0-43-generic x86_64 (64 bit)
Desktop: Cinnamon 3.4.6 Distro: Linux Mint 18.2 Sonya
Machine: Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x
Bios: American Megatrends v: 0805 date: 06/20/2017
CPU: Octa core AMD Ryzen 7 1700 Eight-Core (-HT-MCP-) cache: 4096 KB
clock speeds: max: 3500 MHz 1: 1383 MHz 2: 1382 MHz 3: 1375 MHz
4: 1379 MHz 5: 1540 MHz 6: 1409 MHz 7: 1394 MHz 8: 1493 MHz
9: 1374 MHz 10: 1374 MHz 11: 1384 MHz 12: 1376 MHz 13: 1374 MHz
14: 1374 MHz 15: 1501 MHz 16: 1501 MHz
Graphics: Card: NVIDIA GM206 [GeForce GTX 960]
Display Server: X.Org 1.18.4 drivers: nvidia (unloaded: fbdev,vesa,nouveau)
Resolution: [email protected]
GLX Renderer: GeForce GTX 960/PCIe/SSE2
GLX Version: 4.6.0 NVIDIA 396.24
Audio: Card-1 Advanced Micro Devices [AMD] Device 1457
driver: snd_hda_intel
Card-2 NVIDIA Device 0fba driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.13.0-43-generic
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169
IF: enp30s0 state: up speed: 1000 Mbps duplex: full
mac: 88:d7:f6:df:af:22
Drives: HDD Total Size: 1128.2GB (64.8% used)
ID-1: /dev/sda model: Intenso_SSD_Sata size: 128.0GB
ID-2: /dev/sdb model: WDC_WD10EZEX size: 1000.2GB
Partition: ID-1: / size: 102G used: 20G (20%) fs: ext4 dev: /dev/sda2
ID-2: swap-1 size: 17.11GB used: 0.00GB (0%) fs: swap dev: /dev/sda3
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: N/A mobo: N/A gpu: 43C
Fan Speeds (in rpm): cpu: 0
Info: Processes: 315 Uptime: 14 min Memory: 2201.8/16038.7MB
Client: Shell (bash) inxi: 2.2.35

[Bob Wya]

@De1m0s

Righteo, that looks fine (hint: but would have looked even finer with the lovely forum Code tags)...

What's the output from:

Code: Select all

sudo aptitude search '~iwine'

Thanks
Bob

[De1m0s]

ok, this brings:

Code: Select all

iB  wine-devel                      - WINE Is Not An Emulator - runs MS Windows 
idA wine-devel-amd64                - WINE Is Not An Emulator - runs MS Windows 
idA wine-devel-i386:i386            - WINE Is Not An Emulator - runs MS Windows 
i   wine-staging:i386               - WINE Is Not An Emulator - runs MS Windows 
i   wine-staging-amd64              - WINE Is Not An Emulator - runs MS Windows 
i   wine-staging-dbg:i386           - WINE Is Not An Emulator - runs MS Windows 
i   wine-staging-i386:i386          - WINE Is Not An Emulator - runs MS Windows 
i   winehq-staging                  - WINE Is Not An Emulator - runs MS Windows 
i   winetricks                      - Simple tool to work around common problems

[Bob Wya]

ok, this brings:

Code: Select all

iB  wine-devel                      - WINE Is Not An Emulator - runs MS Windows 
idA wine-devel-amd64                - WINE Is Not An Emulator - runs MS Windows 
idA wine-devel-i386:i386            - WINE Is Not An Emulator - runs MS Windows 
i   wine-staging:i386               - WINE Is Not An Emulator - runs MS Windows 
i   wine-staging-amd64              - WINE Is Not An Emulator - runs MS Windows 
i   wine-staging-dbg:i386           - WINE Is Not An Emulator - runs MS Windows 
i   wine-staging-i386:i386          - WINE Is Not An Emulator - runs MS Windows 
i   winehq-staging                  - WINE Is Not An Emulator - runs MS Windows 
i   winetricks                      - Simple tool to work around common problems

That's fine. You've a full Syswow64 multilib Wine Staging installation.

I'm guessing you haven't read the WineHQ FAQ.

More specifically: WineHQ FAQ: 6.5.3 How do I create a 32 bit wineprefix on a 64 bit system?

Any existing WINEPREFIX's will only be updated when you install a new version of Wine.
They are locked at specific architecture (32-bit or 64-bit), when the WINEPREFIX is first created.

This kind of issue often comes when people only use a Wine Wrapper like Play On Linux.
It's one of the reasons why these 3rd party tools aren't supported on this site.

Bob

[De1m0s]

I read the FAQ; but i don´t know what and when i did something wrong. I never created any 32bit wine-prefix; i don´t use the prefixes direct from wine. I do only use orginal wine instead of the PoL-ones.
What do i have to do now?

PlayOnLInux, DXVK and DumbXInput are making a lot of things much more easier. I know that you don´t like them.
I´m in the opinion, these should grow together to one piece.

[dimesio]

I read the FAQ; but i don´t know what and when i did something wrong.

So what made you think that only 32 bit Wine was installed on that system? The output you posted from aptitude shows that 64 bit Wine is installed.

[Bob Wya]

What do i have to do now?

Create a new 64-bit WINEPREFIX - if you want to install a 64-bit Windows application.
This is the default architecture for a new WINEPREFIX - when created using a Syswow64 / multilib 64-bit Wine installation.

E.g.

Code: Select all

export WINEPREFIX=~/.wine64  # Path to any directory, where the final element (.wine64 - in this example) is an empty directory or does not yet exist
wineboot -u                        # Create WINEPREFIX and update it

A WINEPREFIX is like a virtual Windows installation.
You can create as many as you want on any system.
You can just as easily delete them again (be sure you want to do this first!). E.g.

Code: Select all

rm -rf "${WINEPREFIX:-${HOME}/.wine}"

The WINEPREFIX root directory contains:

• system management files (text-based Registry files)
• a virtual C:\ drive
• directory (dosdevices) containing other Windows drive links

E.g. for this example:

Code: Select all

ls -hl ~/.wine64/

drwxr-xr-x 2 user users 4.0K May 30 11:11 dosdevices/
drwxr-xr-x 7 user users 4.0K May 30 11:11 drive_c/
-rw-r--r-- 1 user users 2.4M May 30 11:11 system.reg
-rw-r--r-- 1 user users   11 May 30 11:11 .update-timestamp
-rw-r--r-- 1 user users 3.3K May 30 11:11 userdef.reg
-rw-r--r-- 1 user users  64K May 30 11:11 user.reg

Wine installs a very minimal Windows setup to: "${WINEPREFIX}/drive_c".
With the usual Windows C:\ drive structure.
E.g. for this example:

Code: Select all

ls -hl ~/.wine64/drive_c
drwxr-xr-x  3 user users 4.0K May 30 11:11 ProgramData/
drwxr-xr-x  6 user users 4.0K May 30 11:11 Program Files/
drwxr-xr-x  6 user users 4.0K May 30 11:11 Program Files (x86)/
drwxr-xr-x  4 user users 4.0K May 30 11:11 users/
drwxr-xr-x 18 user users 4.0K May 30 11:11 windows/

PlayOnLInux, DXVK and DumbXInput are making a lot of things much more easier. I know that you don´t like them.
I´m in the opinion, these should grow together to one piece.

• I've not written any comments about DumbXInput anywhere, because I don't even know what it is.
• I think DXVK is amazing and I use it personally. It serves the vital purpose of providing a performant DX11 translation layer.
  The only real drawback with it (that I can see), is that it is a third party project (outside the control of the Wine project).
• PlayOnLInux might make things easier for a few days... Up until something breaks or doesn't work...
  Which happens pretty soon - since POL4 isn't maintained any more.
  Then people come "here" to complain that "Wine" isn't working and have no concept of basic Wine usage (e.g. how to set up a WINEPREFIX)...

Bob

[De1m0s]

I read the FAQ; but i don´t know what and when i did something wrong.

So what made you think that only 32 bit Wine was installed on that system? The output you posted from aptitude shows that 64 bit Wine is installed.

When using PoL, you can download wine-version direct by PoL, or you can choose "System". PoL-wine-versions are located in ...\home\USER\.PlayOnLinux\... System-wine is located in \opt\wine\
If i set wine-version in PoL now to "System", and start a 64bit application, i get the error-message "....this program can not be run under 32bit wine-server....". Now, i go to my second pc, copy \opt\wine\ to an usb-stick, and replace this version with mine, the program is running, and no error-message appears.
Somewhere must be a difference.

@BobWya:
I do not use wine this way. See above; i do not use any wine-prefix that was build by system-wine. I have about 5 different Prefixe, with different games and apps installed. Some of them are working, some other not; but all of them are 64 bit. I try now every new wine-version, to make the things work, they're not at this time. So, since several months, i get above error, when setting wine-version to system-wine.

[dimesio]

If i set wine-version in PoL now to "System", and start a 64bit application, i get the error-message "....this program can not be run under 32bit wine-server....".

Sounds like a PoL problem, and PoL is not supported here.

[De1m0s]

If i set wine-version in PoL now to "System", and start a 64bit application, i get the error-message "....this program can not be run under 32bit wine-server....".

Sounds like a PoL problem, and PoL is not supported here.

,
?? I don't think so.
How i said: If i get the "wine-devel"-folder from my other pc, and replace this with mine in /opt/wine/ , the error is gone. So, wine installs on my first pc an other version as on my second pc. Thats the problem, and i don't know why, and how i can fix this.

[dimesio]

According to the output you posted, what you have installed on that system is wine-staging, not wine-devel. The winehq-staging packages install to /opt/wine-staging, not /opt/wine-devel, so if PoL is looking for it in the latter directory, it won't find it. If PoL is looking in the wrong directory, that's a PoL problem.

Does running plain Wine from the command line (without PoL) work?

[De1m0s]

According to the output you posted, what you have installed on that system is wine-staging, not wine-devel. The winehq-staging packages install to /opt/wine-staging, not /opt/wine-devel, so if PoL is looking for it in the latter directory, it won't find it. If PoL is looking in the wrong directory, that's a PoL problem.

Does running plain Wine from the command line (without PoL) work?

I have both installed; staging and vanilla-wine. Problem occurs with both of them.
Its not a PoL problem, believe me. There's another trick i'm often using, if i want to keep any wine-version: Copying f.e. the wine-staging folder from /opt/wine to /home/USER/.Playonlinux/wine/.... and rename it f.e. from "wine-staging" to "3.8-staging". Then this version won't be overwritten next time i update wine, and i can easily choose it from PoLs dropdown-list. The problem occurs here exact so, as if i choose "system". Problem occurs not, if i use the wine-version (staging or not) from the other pc. And the problem occurs only since 2 or 3 month. I guess i did something (don't know what), that gave me this problem.

What is the best way, to complete remove wine, with all settings, and settings for updating and installation? Uninstall and then re-install takes only several minutes. This could fix the problem maybe.

[De1m0s]

Completely removing wine with deleting everything related to wine, and re-installation fixed the problem.
But nice try, that you wanted to blame it on PoL....

[Bob Wya]

Completely removing wine with deleting everything related to wine, and re-installation fixed the problem.

Technically that's not fixing a problem, it's simply nuking it from orbit!