Can't install `wine32` (or 3rd party WINE) on 22.04

Bug #2000832 reported by Liam Proven
48
This bug affects 10 people
Affects Status Importance Assigned to Milestone
wine (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I am trying to install the standard `wine32` package. This was recommended to me by the OS once I installed WINE:

````
lproven@ThinkPad-X220:~$ wine clock
it looks like wine32 is missing, you should install it.
as root, please execute "apt-get install wine32"
````

If I try to do this, it fails:

````
lproven@ThinkPad-X220:~$ sudo apt install wine32
[sudo] password for lproven:
Reading package lists... Done
Building dependency tree... Done
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.
 apt : Depends: libapt-pkg6.0 (>= 2.4.7) but it is not going to be installed
 init : PreDepends: systemd-sysv
 libcurl3-gnutls : Depends: libldap-2.5-0 (>= 2.5.4) but it is not installable
 snapd : Depends: openssh-client
         Depends: systemd
         Depends: udev
         Depends: libudev1 (>= 183) but it is not installable
         Recommends: gnupg but it is not going to be installed
 util-linux : PreDepends: libudev1 (>= 183) but it is not installable
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
````

I have no held/pinned/locked packages, and no broken packages. The listed dependencies are present.

I also tried installing WINE 7 from WineHQ. I get very similar errors:

````
lproven@ThinkPad-X220:~$ sudo apt install wine-stable
Reading package lists... Done
Building dependency tree... Done
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.
 apt : Depends: libapt-pkg6.0 (>= 2.4.7) but it is not going to be installed
 init : PreDepends: systemd-sysv
 libgphoto2-6 : Depends: libcurl4 (>= 7.16.2) but it is not installable
 libgphoto2-port12 : Depends: libusb-1.0-0 (>= 2:1.0.8) but it is not installable
 libgstreamer-plugins-base1.0-0 : Depends: libgstreamer1.0-0 (>= 1.20.0) but it is not installable
                                  Recommends: gstreamer1.0-plugins-base but it is not going to be installed
 libpoppler118 : Depends: libnss3 (>= 2:3.16) but it is not installable
 libsane1 : Depends: libcurl3-gnutls (>= 7.16.2) but it is not installable
            Depends: libsnmp40 (>= 5.9.1+dfsg) but it is not installable
            Depends: libusb-1.0-0 (>= 2:1.0.22) but it is not installable
            Recommends: sane-utils (>= 1.1.1-5)
            Recommends: ipp-usb but it is not going to be installed
 snapd : Depends: openssh-client
         Depends: systemd
         Depends: libudev1 (>= 183) but it is not installable
         Recommends: gnupg but it is not going to be installed
 util-linux : PreDepends: libudev1 (>= 183) but it is not installable
 wine-stable-amd64 : Depends: libgstreamer1.0-0 (>= 1.4.0) but it is not installable
                     Depends: libldap-2.5-0 (>= 2.5.4) but it is not installable
                     Depends: libudev1 (>= 183) but it is not installable
                     Depends: libusb-1.0-0 (>= 2:1.0.21) but it is not installable
                     Recommends: libosmesa6 but it is not installable
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
lproven@ThinkPad-X220:~$

````

I get the same error whether I try to install `wine-stable`, `wine-devel` or `wine-staging`.

Other people are reporting this or similar errors as well. Examples:

* https://askubuntu.com/questions/1434526/jammy-22-04-wont-install-wine32
* https://askubuntu.com/questions/1421863/trouble-with-wine32
* https://askubuntu.com/questions/1410718/cannot-install-wine32-in-jammy-22-04
* https://askubuntu.com/questions/1434526/jammy-22-04-wont-install-wine32

The list of requirements seems to vary, so I think that this is unrelated to the real underlying problem, or not directly related.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: wine 6.0.3~repack-1
ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Jan 1 13:57:07 2023
InstallationDate: Installed on 2013-11-15 (3334 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
PackageArchitecture: all
SourcePackage: wine
UpgradeStatus: Upgraded to jammy on 2022-09-05 (117 days ago)

Revision history for this message
Liam Proven (lproven) wrote :
Revision history for this message
Liam Proven (lproven) wrote :

The machine is fully updated. I got the error with wine32 *before* I tried adding the WineHQ repos; they were an attempt to resolve it.

This installation started out as 12.04, I think, on different hardware, and has been upgraded LTS->LTS since. It is stable in use and is a production laptop.

Revision history for this message
Liam Proven (lproven) wrote :

Possibly also relevant/related:

"Unable to install wine Ubuntu 22.04"
https://forum.winehq.org/viewtopic.php?t=36501

"I can't complete wine setup on Linux Ubuntu 22.04.01 LTS"
https://forum.winehq.org/viewtopic.php?t=37236

Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

You need to run "sudo dpkg --add-architecture i386" first - otherwise (if I'm understanding correctly) Ubuntu won't install the needed 32-bit packages for wine32 to work. This should be done whether you're installing Wine from the Ubuntu repos or from third-party repos.

This is currently pretty much expected behavior, however I'm going to leave this bug open (and even add myself to the list of affected users) since I can't help but think there's probably a way that the needed 32-bit enabling command can be run from within the Wine packaging in Ubuntu.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in wine (Ubuntu):
status: New → Confirmed
Revision history for this message
Liam Proven (lproven) wrote :

> You need to run "sudo dpkg --add-architecture i386" first

Thanks for responding.

Yes, I know -- I tried that, and as I have other 32-bit apps installed, it was already in place.

So it's not that.

Revision history for this message
jre (jre-phoenix) wrote :

Yes, the official Debian/Ubuntu Wine explicitly tells a user to add this architecture, but only if it is needed. So we know you did this.

Next probable issue:
There's some conflict between your 64-bit packages and some 32-bit packages, or some 3rd party packages.

According to your Dependencies.txt you have several packages of "origin: unknown". So you probably added 3rd party package repositories and installed packages from there. Now, any problem from there is much easier to cause troubles when installing Wine, because packages that you need for 32-bit AND 64-bit need to be in EXACTLY the same version to install them at the same time.

The first line in your error report:

apt : Depends: libapt-pkg6.0 (>= 2.4.7) but it is not going to be installed

... indicates that something is completely wrong with your packeges, because the apt dependency is at the core of your system and not related to Wine.
Later issues in your report however show additional problems with specific Wine dependencies.

Either go down this whole dependency tree, by trying "sudo apt install libapt-pkg6.0=2.4.7" (or whatever the correct version for your system is according to
 https://packages.ubuntu.com/search?keywords=libapt-pkg6.0
and then repeat this process for the next error that you get, until you see something solvable.

Or "just"
- remove 3rd party repositories from your apt sources.list,
- make sure all official repositories point to the same Ubuntu version
- uninstall every 3rd party package (and replace them by official packages if needed) and
- uninstall every 32-bit package.

Once you can do a "apt update && apt upgrade" without error, try again.

jre (jre-phoenix)
Changed in wine (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
GreyGeek (greygeek77) wrote :

Running a fully updated KDE Neon (jammy) and encountered this issue while trying to use a 32bit WinXP app.
Tried several approaches using WineHq, PlayOnLinux, Winetricks and Bottles.
WineHq ended with the "impossible situation" error, PlayOnLinux and Bottles failed to run the app.
Just adding my post to increment the "wine32 doesn't work on 22.04 counter.

Revision history for this message
Liam Proven (lproven) wrote :

#8

> Just adding my post to increment the "wine32 doesn't work on 22.04 counter.

Thanks for this, @greygeek77! From the number of reports out there, I thought it wasn't just me.

Revision history for this message
Liam Proven (lproven) wrote :

#7

> Once you can do a "apt update && apt upgrade" without error, try again.

I think you may misunderstand, @jre-phoenix. The machine is otherwise functioning perfectly, and I *can* do my daily `apt update/full-upgrade` without error. My dependencies aren't scrambled, everything works fine -- _including Wine 6_ -- but I can't install the `wine32` package _or_ external versions of Wine.

I'd really like to because I am writing about it!

e.g. https://www.theregister.com/2023/02/03/wine_80_dxvk_21/

Revision history for this message
GreyGeek (greygeek77) wrote :

Tried installing WineHq on to KDE Neon Jammy
It failed.
sudo mkdir -pm755 /etc/apt/keyrings

sudo wget -O /etc/apt/keyrings/winehq-archive.key https://dl.winehq.org/wine-builds/winehq.key

wget -nc https://dl.winehq.org/wine-builds/ubuntu/dists/jammy/winehq-jammy.sources

sudo mv winehq-jammy.sources /etc/apt/sources.list.d/

sudo apt update

$ sudo apt install --install-recommends winehq-stable
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) winehq-stable:amd64 < none -> 8.0.0.0~jammy-1 @un puN Ib >
Broken winehq-stable:amd64 Depends on wine-stable:amd64 < none @rc H > (= 8.0.0.0~jammy-1)
  Considering wine-stable:amd64 0 as a solution to winehq-stable:amd64 9999
  Considering wine-stable:i386 0 as a solution to winehq-stable:amd64 9999
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 (= 8.0.0.0~jammy-1)
E: Unable to correct problems, you have held broken packages

Revision history for this message
jre (jre-phoenix) wrote :
Download full text (5.7 KiB)

Na, sorry, I understood you correctly and stand by my suggestions. ;)

But don't worry, I just set up a fresh VM with ubuntu-22.04.2-desktop-amd64.iso to see what's going on.

First I installed wine:

~~~~~
test@ubuntu2004:~$ sudo dpkg --add-architecture i386
test@ubuntu2004:~$ sudo apt update
test@ubuntu2004:~$ sudo apt upgrade
test@ubuntu2004:~$ sudo apt install wine
test@ubuntu2004:~$ wine --version
wine-6.0.3 (Ubuntu 6.0.3~repack-1)
test@ubuntu2004:~$ dpkg -l "*wine*"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-p
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-================-==============-============-==========================
ii fonts-wine 6.0.3~repack-1 all Windows API implementation
ii libwine:amd64 6.0.3~repack-1 amd64 Windows API implementation
ii libwine:i386 6.0.3~repack-1 i386 Windows API implementation
un q4wine <none> <none> (no description available)
ii wine 6.0.3~repack-1 all Windows API implementation
un wine-binfmt <none> <none> (no description available)
un wine-stable <none> <none> (no description available)
ii wine32:i386 6.0.3~repack-1 i386 Windows API implementation
un wine32-preloader <none> <none> (no description available)
ii wine64 6.0.3~repack-1 amd64 Windows API implementation
un wine64-preloader <none> <none> (no description available)
un winetricks <none> <none> (no description available)
~~~~~

So this worked for the regular Wine packages from the Ubuntu archive, including the wine32 package. However this is Wine 6.0.3. If you want Wine 8.0 you need to get it from somewhere else (e.g. winehq.org) - but make sure to uninstall every other Wine package first, e.g.
~~~~~
sudo apt purge wine wine32 wine64 libwine libwine:i386 fonts-wine
~~~~~

Verify you uninstalled all Wine packages:
~~~~~
dpkg -l "*wine*"
~~~~~
Lines starting with "ii" mean the package is installed, "un" is not installed.

Then install whatever Wine package you want.

Note that the Wine packages from winehq.org do not have, suggest or require a wine32 package. Only the "wine" package from the Ubuntu archives asks you to install "wine32". Do not install wine32 together with winehq packages.

For reference, this is what you should get for winehq-stable:

~~~~~
test@ubuntu2004:~$ dpkg -l "*wine*"
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=====================-===============-============-=======================
un wine <none> <none> (no description available)
un wine-amd64 <none> <none> (no description available)
un wine-i386 <none> <none> (no description available)
ii wine-stable 8.0.0.0~j...

Read more...

Revision history for this message
GreyGeek (greygeek77) wrote (last edit ):

As I wrote before, I tried all of the solutions posted to install wine32 in neon. The final block was the libpoppler library.

While researching the installation problem I came across a post by the lead developer of KDE neon, jridelle (sp?) in which he said that wine32 will never be added to neon because modifying the libpoppler library is too complicated and would require huge modifications to neon, and other reasons. IIRC, the post was on reddit, but my astonishment was so great I failed to bookmark the link.

So, since I need wine32 to run EKG software for my wife's heart condition I have opted to move back to Kubuntu. If one doesn't need wine32 then neon is still an awesome "distro".

PS:
Here is Jonathon Riddell statement about wine32 in neon:

" Re: I cannot install Wine staging on Jammy-rebased KDE Neon
https://forum.kde.org/viewtopic.php?f=309&t=176375#p458746

Tue Nov 01, 2022 4:38 pm
Yes I'm afraid our poppler build makes the neon archive incompatible with the wine-staging packages at least on i386. There's no easy way around this unfortunately and it's not a priority for Neon to be compatible with non-KDE software. "

Lambert (skirando)
Changed in wine (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Lambert (skirando) wrote :

I have the same problem.
For me, when I tried to install wine32, I got a conflicting dependancy with libgd3

"Les paquets suivants contiennent des dépendances non satisfaites :
 libgphoto2-6:i386 : Dépend: libgd3:i386 (>= 2.1.0~alpha~) mais ne sera pas installé
"
See report bug I did - https://bugs.launchpad.net/ubuntu/+source/wine/+bug/2016010

Revision history for this message
banananas (banananares) wrote (last edit ):

I also have this problem! (Linux Mint 21.2 (Victoria); Cinnamon 5.8.4; Ubuntu 22.04 jammy)

Please, i hope someone is looking into it. Urgently in need for Wine at the moment :(
I'm even considering clean installing Mint 21.2 right now to see if Wine would work. Or even a total new distro and the hassle of a new learning curve.

I was discussing my issue in the Linux Mint Forum:
https://forums.linuxmint.com/viewtopic.php?t=401014&sid=977dd7c1c20a0847fa03ddfd040dff11

Thank you.

Revision history for this message
Liam Proven (lproven) wrote :

I traced this problem on my machine, and it was something very unexpected.

All my repositories in /etc/apt/sources.list were disabled: on some machines, they were commented out with # symbols. On others the lines were missing. (My original installation of Ubuntu 13.10 has been copied from one machine to another several times.)

The `software-settings-gtk` app did not notice and was happy to change mirrors, even though it wasn't actually looking at any of them.

I had so many other repos configured that every update fetched some updates, of other packages, and looked normal if I didn't pay close attention.

Restoring the default set of repos from a clean install caused about 1GB of updates to be found and installed. Then, changing mirrors started to work correctly, too.

Once updated, I could install the WINE packages from WINEHQ.

I think Ubuntu needs an `apt-lint` or `aptck` or comparable tool, which is able to check that repos are set to sane values, confirm they work, and automatically fix them to the local geolocated default mirrrors.

Since I discovered this issue I found it affected several of my machines. Related issues I have discovered:

* APT defaults to trying to fetch over IPv6 but only a local IPv6 connection is available (not routed to the outside world) so it fails.

* APT uses HTTPS but only HTTP works from some mirror servers.

* Mirrors that only work intermittently so dependencies can't be fetched.

* ISPs that block Github (!)

General message: bizarre software installation problems? Check your repositories. You may find you have none. Check that you have valid entries in `/etc/apt/sources.list`, check that you can `ping` those servers, check that you machine can download from them over your selected protocol. If you are not sure, change to a different mirror, just in case.

Revision history for this message
Kim Lilliestierna (kill-t) wrote :

Almost a year later and no resoloution?

For me it stumbles on :

libgphoto2-6:i386 : Depends: libgd3:i386 (>= 2.1.0~alpha~) but it is not installable

Trying to force the install of libgd3:i386 removes libgd3:amd64 which a large set of packages has dependency on, chief amongst them being php7.x and php8.x

Tried to download the source package of libgd3 but that seems unavailable anywhere...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.