j8a wrote:Hi, did you try using the following commands?
sudo dpkg --add-architecture i386

sudo apt install libblkid1:i386

sudo apt-mark hold libblkid1

sudo aptitude install wine32

These are on my post above, september 28th
Hope it helps.

Thanks for the answer, I previously performed these actions, but this did not happen then and did not help now.

I wonder, why is installing wine so hard? In other distros I'm using, it's just one command.

If I recall correctly, dependency issue with libblkid1 should already be fixed since a while ago. At the moment, I got libblkid1:2.32-0.1 installed and wine is doing just fine (could also update whenever there was any, in fact just recently upgraded to wine-4.0-rc3/staging).

Hello,

I installed it smoothly using the method described in the WineHQ Wiki (https://wiki.winehq.org/Ubuntu).

Have a good day, have fun.

Hi,
A few moments ago I run this commands:
To unholkd the libblkid1 package
jochoa@jochoapc:~$ sudo apt-mark unhold libblkid1
[sudo] password for jochoa:
Se ha cancelado la retención de libblkid1.

Then, to install the libblkid1 package
sudo aptitude upgrade
The following packages will be upgraded:
libblkid1 libblkid1:i386
2 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 392 kB of archives. After unpacking 6.144 B will be used.
Do you want to continue? [Y/n/?] y
Get: 1 http://archive.neon.kde.org/user bionic/main i386 libblkid1 i386 2.32-0.1+18.04+bionic+build4+18.04+bionic+build5 [204 kB]
Get: 2 http://archive.neon.kde.org/user bionic/main amd64 libblkid1 amd64 2.32-0.1+18.04+bionic+build4+18.04+bionic+build5 [188 kB]
Fetched 392 kB in 2s (208 kB/s)
(Leyendo la base de datos ... 222157 ficheros o directorios instalados actualmente.)
Preparando para desempaquetar .../libblkid1_2.32-0.1+18.04+bionic+build4+18.04+bionic+build5_amd64.deb ...
Desconfigurando libblkid1:i386 (2.31.1-0.4ubuntu3.1) ...
Desempaquetando libblkid1:amd64 (2.32-0.1+18.04+bionic+build4+18.04+bionic+build5) sobre (2.31.1-0.4ubuntu3.1) ...
Preparando para desempaquetar .../libblkid1_2.32-0.1+18.04+bionic+build4+18.04+bionic+build5_i386.deb ...
Desempaquetando libblkid1:i386 (2.32-0.1+18.04+bionic+build4+18.04+bionic+build5) sobre (2.31.1-0.4ubuntu3.1) ...
Configurando libblkid1:amd64 (2.32-0.1+18.04+bionic+build4+18.04+bionic+build5) ...
Configurando libblkid1:i386 (2.32-0.1+18.04+bionic+build4+18.04+bionic+build5) ...
Procesando disparadores para libc-bin (2.27-3ubuntu1) ...

Current status: 0 (-2) upgradable.

At last, I could open any wine 32 bits program after the upgrade and I can confirm that the problem was fixed.

Regards,

As of today, i can say that the method described in https://wiki.winehq.org/Ubuntu does not work, and would fully break the system.

See http://paste.debian.net/hidden/becf28bf/

That has nothing to do with neon.
You'll note in the output that libgcrypt20 are clashing between the version in ubuntu 18.04 and 1.8.4-3ubuntu1. the notable thing about 1.8.4-3ubuntu1 is that this is the version in ubuntu 19.04. seeing as there is no neon on 19.04 whatever is wrong with your system has nothing to do with neon.

I followed the https://wiki.winehq.org/Ubuntu and it seems to work now.