APT Install Of Wine Demands Removal of Unrelated Packages

[tamj]

I only want Wine so I can use Affinity Designer on my Ubuntu 20.04 machine.
I tried installing Wine following this procedure https://wiki.winehq.org/Ubuntu

But at the final stage, i.e.
sudo apt install --install-recommends winehq-stable

I get a strange output that wants permision to remove a load of drivers and applications (with no relation to Wine) before installing Wine . . .

Can anyone explain what is wrong here ?
On the face of it, Wine is sticking its nose in things that are unrelated to its own functioning.

[dimesio]

You're right, the files being removed have nothing to do with Wine. The one thing I can think of that sometimes triggers removal of many unrelated files is the installation of a package that is not multiarch compatible. This can happen if you have installed packages from a PPA; packages from the standard or universe repositories should not cause this problem.

[tamj]

You can see the Wine repos I used in the link https://wiki.winehq.org/Ubuntu

But I have used ppas (or some apps I installed used ppa sources) in the past and these remain there for updates.

Still and all, it is so strange that a new app will only install something if a load of vital drivers and professionally essential apps are uninstalled.
I appreciate that there are Windows versions for many of these drivers and apps.
But Wine is an open-source production - it's not a come-back-to-Windows-again package made by Microsoft.
Someone suggested that it could be an extreme behaviour by APT - which does not itself 'know' what my intention for Wine may be and simply specifies the requirements for an installation of Wine . . .

[jkfloris]

It looks like you are trying to install the Ubuntu packages of Wine (wine, wine64, libwine)
and the WineHQ Wine packages (wine-stable).
While this can be done, it is usually not necessary.
Remove all Ubuntu Wine packages first before installing the WineHQ Wine packages.

[tamj]

Just did that and got same outcome.

Code: Select all

$ sudo apt install wine-stable
[sudo] password for tk: 
Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 206639 (synaptic)      
Reading package lists... Done                                                                                  
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  distro-info docutils-common duplicity evince-common git-man gnome-video-effects gparted-common gstreamer1.0-gtk3 ieee-data libbsd-dev libcolamd2 libdazzle-1.0-0 libedit-dev
  liberror-perl libestr0 libfastjson4 libgmp-dev libgmpxx4ldbl libgsl23 libgslcblas0 libgtkspell0 libimage-magick-perl libimage-magick-q16-perl libkpathsea6 liblapack3
  libmagick++-6.q16-8 libncurses-dev libossp-uuid16 libpcrecpp0v5 libpotrace0 libpython2.7 libraw19 libreadline-dev librsync2 libspectre1 libsuitesparseconfig5 libsynctex2
  libutempter0 libzip5 linux-headers-5.4.0-59 linux-hwe-5.8-headers-5.8.0-55 lp-solve pepperflashplugin-nonfree python-babel-localedata python-backports.functools-lru-cache
  python-bs4 python-chardet python-html5lib python-lxml python-numpy python-six python-soupsieve python-webencodings python3-babel python3-bcrypt python3-debtcollector
  python3-docutils python3-future python3-iso8601 python3-keystoneauth1 python3-keystoneclient python3-lockfile python3-louis python3-msgpack python3-netaddr python3-netifaces
  python3-os-service-types python3-oslo.config python3-oslo.context python3-oslo.i18n python3-oslo.log python3-oslo.serialization python3-oslo.utils python3-paramiko
  python3-pyatspi python3-rfc3986 python3-roman python3-speechd python3-stevedore python3-swiftclient python3-wrapt shotwell-common
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  fonts-wine libfaudio0 libgpg-error-l10n libodbc1 libosmesa6 libstb0 libvkd3d1 libwine wine wine64
Suggested packages:
  libmyodbc odbc-postgresql tdsodbc unixodbc-bin gstreamer1.0-plugins-bad q4wine winbind winetricks playonlinux wine-binfmt dosbox exe-thumbnailer | kio-extras wine64-preloader
Recommended packages:
  libcapi20-3 wine32
The following packages will be REMOVED:
  apparmor-utils cheese deja-dup eog evince gdbserver git gnome-calendar gparted inkscape iwd libc6-dbg libdvdcss-dev libdvdcss2 libevdocument3-4 libevview3-3 libnetplan0
  libreoffice-calc libreoffice-gnome libreoffice-gtk3 libssl-dev linux-headers-5.4.0-59-generic linux-headers-5.8.0-55-generic lshw mesa-utils microsoft-edge-beta
  mysql-workbench-community netplan.io nodejs openjdk-14-jdk openjdk-14-jdk-headless openjdk-14-jre openjdk-14-jre-headless opera-stable orca powertop python3-apparmor
  python3-brlapi python3-libapparmor rsyslog shotwell simple-scan snapd strace swi-prolog-nox thermald tmux ubuntu-advantage-tools ubuntu-minimal ubuntu-standard uuid-runtime
  xbrlapi
The following NEW packages will be installed:
  fonts-wine libfaudio0 libgpg-error-l10n libodbc1 libosmesa6 libstb0 libvkd3d1 libwine wine wine-stable wine64
0 upgraded, 11 newly installed, 52 to remove and 0 not upgraded.
Need to get 29.1 MB of archives.
After this operation, 1,525 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

[tamj]

Then I tried installing using the Ubuntu Software console.
This process didn't even warn me that it was removing anything - just cleared all browsers, wifi client, major apps, etc.
I'd be lost if it wasn't for hourly TimeShift backups.

So hard to see that the major flavor of Unix-like op systems has not been comprehensively tested for running Wine.
If Wine coders aren't writing a Windows layer to suit Ubuntu - just who the hell are they writing it for ?
Plain and simple, Wine is trash - and dangerous trash at that.

[dimesio]

If the Ubuntu Software console just removed packages without any warning, I'd say that's a serious bug in the Ubuntu Software console.

As to why your package managers wanted to remove those packages, you admit to having installed packages from several PPAs, which is what I pointed out could cause this problem. Wine requires multiarch compatible packages--packages where both the i386 and x86_64 versions can be installed. If you have a package installed that is not multiarch compatible, but which is a dependency of Wine (or a dependency of a dependency...), apt tries to solve the problem by uninstalling the x86_64 package and replacing it with the i386 version, which can trigger the uninstallation of its dependencies, leading to a large number of packages being uninstalled that shouldn't be. The solution to that situation is to figure out which package is causing the problem and either uninstall it entirely or replace it with a multiarch-compatible package.

The other thing I noticed from the list of repositories you posted is that you have packages.microsoft.com, which means you are running this in a WSL install of Ubuntu. You are welcome to experiment, but keep in mind that our packages are not tested at all in WSL and not guaranteed to work in that environment.

[jkfloris]

In the "Software & Updates" screenshot, I don't see the WineHQ repo. What is the output of:

Code: Select all

grep -R ^deb /etc/apt/sources.list*

And I wonder why the Ubuntu Wine packages want to be installed when you install the WineHQ Wine packages.
What is the output of:

Code: Select all

dpkg -l | grep wine

Does your system also want to remove all kinds of packages if you do:

Code: Select all

sudo apt install winehq-stable wine-stable wine-stable-amd64 wine-stable-i386:i386

[tamj]

The other thing I noticed from the list of repositories you posted is that you have packages.microsoft.com, which means you are running this in a WSL install of Ubuntu. You are welcome to experiment, but keep in mind that our packages are not tested at all in WSL and not guaranteed to work in that environment.

The Microsoft ppas you refer to are:

packages.microsoft.com/repos/vscode stable main
packages.microsoft.com/repos/code stable main

which relate purely to Visual Studio Code - something I hardly ever use as I'm a Sublime Text 4 user.

As I understand it, Windows Subsystem for Linux (WSL) is for those users who want to run Linux native apps on machines that use Windows 10. WSL therefore seems more the opposite technology to Wine in that it facilitates Windows users who want to use Linux apps without changing over to Linux. As someone who has abandoned Windows for many good reasons, I will never return to it whatever the usefulness of Affinity or other media apps as yet uncompiled to Linux.

I will remove VSC for good measure to see if it's been affecting Wine installation.

Wine requires multiarch compatible packages--packages where both the i386 and x86_64 versions can be installed.

Why have 32-bit version for code in this day and age ?
All op systems and major apps are on 64-bit for years now.
I think this sticking to 32-bit versions is just looking for trouble.

[tamj]

@jkfloris:

If I install Wine, I lose so many things like internet (Intel Wifi daemon removed), apps, Java, etc that I immediately have to revert to my PC's state before installation. Hence the absence of WineHQ repo.

Code: Select all

~$ dpkg -l | grep wine
~$ 

I believe my system would remove all the packages removed by other installation processes if I did

Code: Select all

sudo apt install winehq-stable wine-stable wine-stable-amd64 wine-stable-i386:i386

[tamj]

$ sudo apt install winehq-stable wine-stable wine-stable-amd64 wine-stable-i386:i386
[sudo] password for tk:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package winehq-stable
E: Unable to locate package wine-stable-amd64
E: Unable to locate package wine-stable-i386:i386
$
[/code]

[dimesio]

Why have 32-bit version for code in this day and age ?
All op systems and major apps are on 64-bit for years now.
I think this sticking to 32-bit versions is just looking for trouble.

Complain to Microsoft, which was very late to come 64 bit. Because of that, most Windows apps are still 32 bit, and even most 64 bit ones have 32 bit parts (esp. installers). Many of our users are using Wine to run old Windows apps that will never be available in 64 bit; some are even using Wine to run 16 bit apps.

Code: Select all

E: Unable to locate package winehq-stable

If you haven't added the WineHQ repository, obviously apt won't be able to find its packages. If you really don't want to add it you could download all the required packages and install them locally. However, if you hadn't added the WineHQ repository when you installed Wine, then the packages that triggered the uninstallations were the distro ones, or possibly from one of the PPAs, not WineHQ's.

WineHQ packages do not demand uninstallation of anything, not even distro Wine versions. They do pull in dependencies, just like other packages. Our Wine packages are built against the packages in the standard and universe repositories, and if you stick to those repositories, there should be no problem with the dependencies. But if you have installed packages from a PPA, there may be conflicts in the versions of dependencies (or dependencies of dependencies) required by Wine and the other package. Apt tries to sort out the dependency issues, but sometimes gets it wrong. In those cases, you have to figure out what's triggering the cascade of problems and fix it manually.

[tamj]

Okay, I followed this recent how-to web page to install winehq

https://vitux.com/how-to-install-wine-on-ubuntu/

But I came unstuck at the installing of winehq:

Code: Select all

$ sudo apt-get install --install-recommends winehq-stable
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 winehq-stable : Depends: wine-stable (= 6.0.1~bionic-1)
E: Unable to correct problems, you have held broken packages.

# This seems to imply that wine-stable is a prerequisite package for winehq . . . 


~$ sudo apt install wine-stable

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 wine-stable : Depends: wine-stable-i386 (= 6.0.1~bionic-1)
E: Unable to correct problems, you have held broken packages.

# This seems to imply that wine-stable-i386 is a prerequisite package for wine-stable . . . 

~$ sudo apt install wine-stable-i386
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 wine-stable-i386:i386 : Depends: libasound2:i386 (>= 1.0.16) but it is not going to be installed
                         Depends: libc6:i386 (>= 2.27) but it is not going to be installed
                         Depends: libfaudio0:i386 but it is not going to be installed
                         Depends: libglib2.0-0:i386 (>= 2.12.0) but it is not going to be installed
                         Depends: libgphoto2-6:i386 (>= 2.5.10) but it is not going to be installed
                         Depends: libgphoto2-port12:i386 (>= 2.5.10) but it is not going to be installed
                         Depends: libgstreamer-plugins-base1.0-0:i386 (>= 1.0.0) but it is not going to be installed
                         Depends: libgstreamer1.0-0:i386 (>= 1.4.0) but it is not going to be installed
                         Depends: liblcms2-2:i386 (>= 2.2+git20110628) but it is not going to be installed
                         Depends: libldap-2.4-2:i386 (>= 2.4.7) but it is not going to be installed
                         Depends: libmpg123-0:i386 (>= 1.13.7) but it is not going to be installed
                         Depends: libopenal1:i386 (>= 1.14) but it is not going to be installed
                         Depends: libpcap0.8:i386 (>= 0.9.8) but it is not going to be installed
                         Depends: libpulse0:i386 (>= 0.99.1) but it is not going to be installed
                         Depends: libudev1:i386 (>= 183) but it is not going to be installed
                         Depends: libusb-1.0-0:i386 (>= 2:1.0.21) but it is not going to be installed
                         Depends: libx11-6:i386 but it is not going to be installed
                         Depends: libxext6:i386 but it is not going to be installed
                         Depends: libxml2:i386 (>= 2.9.0) but it is not going to be installed
                         Depends: ocl-icd-libopencl1:i386 but it is not going to be installed or
                                  libopencl1:i386
                         Depends: ocl-icd-libopencl1:i386 (>= 1.0) but it is not going to be installed or
                                  libopencl-1.1-1:i386
                         Depends: libasound2-plugins:i386 but it is not going to be installed
                         Depends: libncurses6:i386 but it is not going to be installed or
                                  libncurses5:i386 but it is not going to be installed or
                                  libncurses:i386 but it is not installable
                         Recommends: libcapi20-3:i386 but it is not going to be installed
                         Recommends: libcups2:i386 but it is not going to be installed
                         Recommends: libdbus-1-3:i386 but it is not going to be installed
                         Recommends: libfontconfig1:i386 but it is not going to be installed
                         Recommends: libfreetype6:i386 but it is not going to be installed
                         Recommends: libglu1-mesa:i386 but it is not going to be installed or
                                     libglu1:i386
                         Recommends: libgnutls30:i386 but it is not going to be installed or
                                     libgnutls28:i386 but it is not installable or
                                     libgnutls26:i386 but it is not installable
                         Recommends: libgsm1:i386 but it is not going to be installed
                         Recommends: libgssapi-krb5-2:i386 but it is not going to be installed
                         Recommends: libjpeg62-turbo:i386 but it is not installable or
                                     libjpeg8:i386 but it is not going to be installed
                         Recommends: libkrb5-3:i386 but it is not going to be installed
                         Recommends: libodbc1:i386 but it is not going to be installed
                         Recommends: libosmesa6:i386 but it is not going to be installed
                         Recommends: libpng16-16:i386 but it is not going to be installed or
                                     libpng12-0:i386 but it is not installable
                         Recommends: libsane:i386 but it is not going to be installed or
                                     libsane1:i386
                         Recommends: libsdl2-2.0-0:i386 but it is not going to be installed
                         Recommends: libtiff5:i386 but it is not going to be installed
                         Recommends: libv4l-0:i386 but it is not going to be installed
                         Recommends: libxcomposite1:i386 but it is not going to be installed
                         Recommends: libxcursor1:i386 but it is not going to be installed
                         Recommends: libxfixes3:i386 but it is not going to be installed
                         Recommends: libxi6:i386 but it is not going to be installed
                         Recommends: libxinerama1:i386 but it is not going to be installed
                         Recommends: libxrandr2:i386 but it is not going to be installed
                         Recommends: libxrender1:i386 but it is not going to be installed
                         Recommends: libxslt1.1:i386 but it is not going to be installed
                         Recommends: libxxf86vm1:i386 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
~$

It looks like the 32-bit architecture is the problem again and again.
On behalf of all Wine users with no interest in 32-bit apps, I ask for a review of your software to allow for purely 64-bit Windows 10 app use, i.e. no need to install i386 versions.

[dimesio]

On behalf of all Wine users with no interest in 32-bit apps, I ask for a review of your software to allow for purely 64-bit Windows 10 app use, i.e. no need to install i386 versions.

Pure 64 bit Windows apps are still rare--as I mentioned above, most 64 bit Windows apps have 32 bit installers--so our package dependencies are not going to change any time soon. However, there is nothing to stop you from compiling 64 bit Wine yourself and trying that. You could also look for a 64 bit Wine package that does not force the installation of 32 bit Wine--that's a decision made by the package maintainers, not the Wine project. Just be aware that pure 64 bit is not supported here.

[dimesio]

I should add that if you want to try to solve the dependency problem you're now seeing, first you need to enable i386 architecture if you haven't, and then follow the instructions in https://wiki.winehq.org/FAQ#How_do_I_so ... ll_Wine.3F.

[tamj]

Code: Select all

:~$ sudo apt-get install wine64
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  distro-info docutils-common duplicity evince-common git-man gnome-video-effects gparted-common gstreamer1.0-gtk3 ieee-data libbsd-dev
  libcolamd2 libdazzle-1.0-0 libedit-dev liberror-perl libestr0 libfastjson4 libgmp-dev libgmpxx4ldbl libgsl23 libgslcblas0 libgtkspell0
  libimage-magick-perl libimage-magick-q16-perl libkpathsea6 liblapack3 libmagick++-6.q16-8 libncurses-dev libossp-uuid16 libpcrecpp0v5
  libpotrace0 libpython2.7 libraw19 libreadline-dev librsync2 libspectre1 libsuitesparseconfig5 libsynctex2 libutempter0 libzip5
  linux-headers-5.4.0-59 linux-hwe-5.8-headers-5.8.0-55 lp-solve pepperflashplugin-nonfree python-babel-localedata
  python-backports.functools-lru-cache python-bs4 python-chardet python-html5lib python-lxml python-numpy python-six python-soupsieve
  python-webencodings python3-babel python3-bcrypt python3-debtcollector python3-docutils python3-future python3-iso8601
  python3-keystoneauth1 python3-keystoneclient python3-lockfile python3-louis python3-msgpack python3-netaddr python3-netifaces
  python3-os-service-types python3-oslo.config python3-oslo.context python3-oslo.i18n python3-oslo.log python3-oslo.serialization
  python3-oslo.utils python3-paramiko python3-pyatspi python3-rfc3986 python3-roman python3-speechd python3-stevedore python3-swiftclient
  python3-wrapt shotwell-common
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  fonts-wine libfaudio0 libgpg-error-l10n libodbc1 libosmesa6 libstb0 libvkd3d1 libwine wine
Suggested packages:
  libmyodbc odbc-postgresql tdsodbc unixodbc-bin gstreamer1.0-plugins-bad q4wine winbind winetricks playonlinux wine-binfmt dosbox
  exe-thumbnailer | kio-extras wine64-preloader
Recommended packages:
  libcapi20-3 wine32
The following packages will be REMOVED:
  apparmor-utils cheese deja-dup eog evince gdbserver git gnome-calendar gparted inkscape iwd libc6-dbg libdvdcss-dev libdvdcss2
  libevdocument3-4 libevview3-3 libnetplan0 libreoffice-calc libreoffice-gnome libreoffice-gtk3 libssl-dev linux-headers-5.4.0-59-generic
  linux-headers-5.8.0-55-generic lshw mesa-utils microsoft-edge-beta mysql-workbench-community netplan.io nodejs openjdk-14-jdk
  openjdk-14-jdk-headless openjdk-14-jre openjdk-14-jre-headless opera-stable orca powertop python3-apparmor python3-brlapi
  python3-libapparmor rsyslog shotwell simple-scan snapd strace swi-prolog-nox thermald tmux ubuntu-advantage-tools ubuntu-minimal
  ubuntu-standard uuid-runtime xbrlapi
The following NEW packages will be installed:
  fonts-wine libfaudio0 libgpg-error-l10n libodbc1 libosmesa6 libstb0 libvkd3d1 libwine wine wine64
0 upgraded, 10 newly installed, 52 to remove and 0 not upgraded.
Need to get 0 B/29.1 MB of archives.
After this operation, 1,495 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
$ 

You'd better tell me where to get the sources for exclusively 64-bit Wine as any attempt to install it from Synaptic tells me that it will effect changes to the previously mentioned list of apps and drivers . . .
How do I strip out attempts to include Wine-32 ?

[dimesio]

You don't have to strip anything out; you just have to run configure with --enable-win64. https://wiki.winehq.org/Building_Wine

[jkfloris]

I only want Wine so I can use Affinity Designer on my Ubuntu 20.04 machine.

Code: Select all

The following packages have unmet dependencies:
 winehq-stable : Depends: wine-stable (= 6.0.1~bionic-1)

If you use Ubuntu 20.04 you must add the focal repo.

[dimesio]

Code: Select all

The following packages have unmet dependencies:
 winehq-stable : Depends: wine-stable (= 6.0.1~bionic-1)

If you use Ubuntu 20.04 you must add the focal repo.

Good catch; I didn't notice that. And that could be the reason apt wants to uninstall a bunch of packages.

[tamj]

Finally got the wine64 configured (needed several more packages installed) and compiled in over an hour.
But although

Code: Select all

$ make install 

runs and outputs no errors, I still get no response from

Code: Select all

$  wine --version

Neither do other operations work even when on the host directory, e.g.:

Code: Select all

$  wine <program> 

If I cd to the host directory (/opt) I can get a response via

Code: Select all

$  ./wine notepad

but this is less than you'd expect from a proper install.

Have I omitted anything ?

[invisible kid]

You would have to add the opt directory to your PATH environment variable(export PATH=$PATH:/opt/<dir>/bin). But it seems like the better path to go is to try to reinstall via ubuntu package manager with the new info above about the focal repo. Just a regular user's opinion.

[tamj]

@invisible kid:

I see what you're suggesting about PATH but:

1. In Linux there is usually no /bin folder in applications, though there are inside the /usr folder.
In applications, the application's host folder holds all the executables.
2. When I change working directory to my Wine installation folder in /opt/wine-6.0.1, then the wine command should be accessible - but it's not. Although the wine command is effectively invocable via ./wine --version or ./wine <program name>

[dimesio]

2. When I change working directory to my Wine installation folder in /opt/wine-6.0.1, then the wine command should be accessible - but it's not. Although the wine command is effectively invocable via ./wine --version or ./wine <program name>

The default for make install is to install to /usr/local, unless you specified a different location (--prefix=/path/to/prefix) when you ran configure. Did you? Or are you perhaps referring to the build directory when you say "installation folder"?

If it is the build directory, it works when you cd to it because the wine and wine64 commands in that directory are symlinks that point to the tools/winewrapper script that enables running Wine from the build directory, which is how most people who build Wine themselves run it.

To run the binary you installed, you would have to use the full path to the installed binary.

[tamj]

Looks like it's in /usr/local/bin folder.

That would mean that it's also on the $PATH .
I get it.
It has to be called via wine64 rather than wine:

Code: Select all

$ wine --version

Command 'wine' not found, but can be installed with:

sudo apt install wine              # version 5.0-3ubuntu1, or
sudo apt install wine-development  # version 5.5-3ubuntu1

Code: Select all

$ wine64 --version
wine-6.0.1

Now the problem is to get wine64 to see Affinity-designer.

[invisible kid]

If the installer/program is on a cdrom one way would be to mount the cdrom and run the install program from there.
If the installer/program is a single file, one way would be to copy the single file to the ~/.wine/drive_c folder and run it via wine64 there, or even any location.