Can wine32 be installed on jammy Mate
Can somebody please explain me: Is it possible to install wine for win 32 programs on Jammy and which repositories have to be used? Are there principle obstacles by missing packages?
I have tried already this:
1) From the standard Ubuntu repositories:
It ends up with broken packages
2) Binding wine repositories https:/
It ends up with broken packages
3) Binding wine-development:
It ends up with this message:
Package wine-development has no available version, but exists in the database.
This typically means that the package was mentioned in a dependency and never uploaded, has been obsoleted or is not available with the contents of sources.list
4) Following the proceedure in "Building Biarch Wine On Ubuntu" although it is outdated
(https:/
It hangs with missing dependencies
I have checked in several forums about this special wine32 problem, but no result. So what to do?
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu wine Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Jochen
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Using the standard Ubuntu repositories should work and should not lead to broken packages.
For diagnostic purposes please provide the output that you receive for the following commands (to be executed in a terminal window):
uname -a
lsb_release -crid
dpkg --print-
dpkg --print-
sudo dpkg --audit
sudo apt update
apt policy wine wine32 wine64
Revision history for this message
|
#2 |
What are you wanting to run in WINE?
The application you want to run may be known to not run. Have you checked the WINE AppDb for compatibility?
Revision history for this message
|
#3 |
Manfred Hampl requested more information:
Thank you for the reply. I send all the required terminal outputs:
uname -a:
yx@yx-HP:~$ uname -a
Linux yx-HP 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
yx@yx-HP:~$
lsb_release -crid:
yx@yx-HP:~$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy
yx@yx-HP:~$
dpkg --print-
yx@yx-HP:~$ dpkg --print-
amd64
yx@yx-HP:~$
dpkg --print-
yx@yx-HP:~$ dpkg --print-
amd64
yx@yx-HP:~$
sudo dpkg --audit:
yx@yx-HP:~$ sudo dpkg --audit
[sudo] Passwort für yx:
yx@yx-HP:~$
sudo apt update:
yx@yx-HP:~$ sudo apt update
Ign:1 http://
Ign:2 https:/
Ign:3 http://
Ign:4 http://
Ign:5 http://
Ign:6 http://
Ign:1 http://
Ign:2 https:/
Ign:3 http://
Ign:4 http://
Ign:5 http://
Ign:6 http://
Ign:1 http://
Ign:2 https:/
Ign:3 http://
Ign:4 http://
Ign:5 http://
Ign:6 http://
Fehl:1 http://
Temporärer Fehlschlag beim Auflösen von »security.
Fehl:2 https:/
Temporärer Fehlschlag beim Auflösen von »dl.winehq.org«
Fehl:3 http://
Temporärer Fehlschlag beim Auflösen von »archive.
Fehl:4 http://
Temporärer Fehlschlag beim Auflösen von »archive.
Fehl:5 http://
Temporärer Fehlschlag beim Auflösen von »archive.
Fehl:6 http://
Temporärer Fehlschlag beim Auflösen von »archive.
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Aktualisierung für 143 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
W: Fehlschlag beim Holen von http://
W: Fehlschlag beim Holen von http://
W: Fehlschlag beim Holen von http://
W: Fehlschlag beim Holen von http://
W: Fehlschlag beim Holen von http://
W: Fehlschlag beim Holen von https:/
W: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stelle benutzt.
yx@yx-HP:~$
apt policy wine wine32 wine64:
yx@yx-HP:~$ apt policy wine wine32 wine64
wine:
Installiert: (keine)
Installations
Versionstabelle:
6.0.3~repack-1 500
500 http://
500 http://
wine32:i386:
Installiert: (keine)
Installations
Versionstabelle:
6.0.3~repack-1 500
500 http://
wine64:
Installiert: (keine)
Installations
Versionstabelle:
6.0.3~repack-1 500
500 http://
yx@yx-HP:~$
Let me makes some notes about the state of the system:
1) It is a temporary experimental system on an external HD, Ubuntu jammy 64bit. My productive system is still 20.04 32bit. On that one wine32 works perfectly and I am only interested in some old windows32 programs.
2) I had already made many wine experiments with 22.04 (before I plan to install it as productive system). I had removed all wine packets and the last try was that mentioned proceedure in "Building Biarch Wine On Ubuntu" what failed. For that purpose I had used
sudo apt-get build-dep wine
and installed 229 packages as dependencies. They are still installed.
3) Experiments with the wine installation I have always made with a just updated system (at present it needs an update)
4) The sudo dpkg --audit gave no reply
5) Intersting for me, the result of "apt policy wine wine32 wine64". There the package 6.0.3~repack-1 is mentioned. I had already tried that unsuccessfully before and still have "wine32_
Revision history for this message
|
#4 |
actionparsnip requested more information:
What are you wanting to run in WINE?
The application you want to run may be known to not run. Have you checked the WINE AppDb for compatibility?
No, you misunderstood my question. It is not about installing a certain win program, it is about installing wine32. The win programs I am interested in run perfectly in wine focal fossa.
Revision history for this message
|
#5 |
I understand. Just didn't want you to be wanting to installing WINE when the application known to not work
Revision history for this message
|
#6 |
1. Quote
W: Fehlschlag beim Holen von http://
End of quote
For whatever reason you had a network problem at that time, making it impossible to reach the repository servers. It is required to get that network problem solved before anything related to wine can be installed. Does "normal" internet access (e.g. searching on google.com) work on that system?
2. Quote
Aktualisierung für 143 Pakete verfügbar.
End of quote
Before you start installing wine, you should care for installing all available updates for other packages (sudo apt full-upgrade).
3. In addition to the standard Ubuntu repositories you also have the winehq.org repository activated. You have to be aware that the wine package there are named a bit differently. As far as I know the main wine package is named "wine-stable" in the winehq repository. I dob that you can install both wine (from Ubuntu) and wine-stable (from winehq) at the same time.
You should decide whether you want to install wine from the Ubuntu repositories or from the winehq servers.
4. You missed a command
dpkg --print-
Suggested next steps:
Try getting networking up and running and then execute the command
apt --simulate install wine
and copy/paste the output.
Revision history for this message
|
#7 |
Let me answer to 1. Quote and 2.Quote:
I had already mentioned before, that all experiments with wine have been made with an updated system. The message
W: Fehlschlag beim Holen von http://
occured when I launched the "yx@yx-HP:~$ sudo apt update" command and I had no internet connection at that time. I am just doing an update and will send it again.
About 3.
I know that the packages from winehq and ubuntu may be different. But finally I have to rely on apt to figure out which packages can fit. I had added the winehq source because I read in several wikis and forums, that the Ububtu source is not complete concerning the wine 32, but it is suported by wine devel. The original winehq information is a bit confusing and outdated, what I do not wonder as it is a very complex system.
I work usually with synaptic and the winehq source is visible there. Interesting was, just now when I started the upgrade, I got this message:
W: https:/
what is definately wrong, the winekey is in "/etc/apt/keyrings" (I am wondering, never before got that message)
About 4.
You said: "You missed a command dpkg --print-
Yes, there was an error, here now:
yx@yx-HP:~$ dpkg --print-
i386
yx@yx-HP:~$
And now the output of sudo apt update after upgrade:
yx@yx-HP:~$ sudo apt update
[sudo] Passwort für yx:
OK:1 http://
Holen:2 http://
Holen:3 http://
OK:4 https:/
Holen:5 http://
Holen:6 http://
Holen:7 http://
Holen:8 http://
Holen:9 http://
Holen:10 http://
Holen:11 http://
Holen:12 http://
Es wurden 639 kB in 9 s geholt (68,5 kB/s).
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Aktualisierung für 17 Pakete verfügbar. Führen Sie »apt list --upgradable« aus, um sie anzuzeigen.
W: https:/
yx@yx-HP:~$
What I do not understand is "Aktualisierung für 17 Pakete verfügbar" just after an upgrade. Anyway, here it is:
yx@yx-HP:~$ apt list --upgradable
Auflistung… Fertig
gir1.2-
grub-efi-
grub-efi-
libpango-
libpango1.
libpangocairo-
libpangoft2-
libpangoxft-
libqmi-
libqmi-
modemmanager/
pango1.
python3-
software-
software-
tcpdump/
ubuntu-
yx@yx-HP:~$
And here now the simulation (I did not know that command before, could have helped me)
yx@yx-HP:~$ apt --simulate install wine
HINWEIS: Dies ist nur eine Simulation!
apt benötigt root-Privilegien für die reale Ausführung.
Behalten Sie ebenfalls in Hinterkopf, dass die Sperren deaktiviert
sind, verlassen Sie sich also bezüglich des reellen aktuellen
Status der Sperre nicht darauf!
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt:
libmozjs-91-0 linux-headers-
linux-
linux-
Verwenden Sie »apt autoremove«, um sie zu entfernen.
Die folgenden zusätzlichen Pakete werden installiert:
fonts-wine gir1.2-pango-1.0 libcapi20-3 libfaudio0 libpango-1.0-0
libpango1.0-dev libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0
libstb0 libvkd3d-shader1 libvkd3d1 libwine libz-mingw-w64 pango1.0-tools
vkd3d-compiler wine64
Vorgeschlagene Pakete:
libpango1.0-doc ttf-mscorefonts
winetricks playonlinux wine-binfmt wine64-preloader
Empfohlene Pakete:
wine32
Die folgenden NEUEN Pakete werden installiert:
fonts-wine libcapi20-3 libfaudio0 libstb0 libvkd3d-shader1 libvkd3d1 libwine
libz-mingw-w64 vkd3d-compiler wine wine64
Die folgenden Pakete werden aktualisiert (Upgrade):
gir1.2-pango-1.0 libpango-1.0-0 libpango1.0-dev libpangocairo-1.0-0
libpangoft2-1.0-0 libpangoxft-1.0-0 pango1.0-tools
7 aktualisiert, 11 neu installiert, 0 zu entfernen und 10 nicht aktualisiert.
Inst fonts-wine (6.0.3~repack-1 Ubuntu:22.04/jammy [all])
Inst libpango1.0-dev [1.50.6+ds-2] (1.50.6+ds-2ubuntu1 Ubuntu:
Inst pango1.0-tools [1.50.6+ds-2] (1.50.6+ds-2ubuntu1 Ubuntu:
Inst gir1.2-pango-1.0 [1.50.6+ds-2] (1.50.6+ds-2ubuntu1 Ubuntu:
Inst libpangoxft-1.0-0 [1.50.6+ds-2] (1.50.6+ds-2ubuntu1 Ubuntu:
Inst libpangoft2-1.0-0 [1.50.6+ds-2] (1.50.6+ds-2ubuntu1 Ubuntu:
Inst libpango-1.0-0 [1.50.6+ds-2] (1.50.6+ds-2ubuntu1 Ubuntu:
Inst libpangocairo-1.0-0 [1.50.6+ds-2] (1.50.6+ds-2ubuntu1 Ubuntu:
Inst libstb0 (0.0~git2021091
Inst libfaudio0 (22.02-1 Ubuntu:22.04/jammy [amd64])
Inst libvkd3d-shader1 (1.3~jammy-1 winehq:jammy [amd64])
Inst libvkd3d1 (1.3~jammy-1 winehq:jammy [amd64])
Inst libz-mingw-w64 (1.2.11+dfsg-4 Ubuntu:22.04/jammy [all])
Inst libwine (6.0.3~repack-1 Ubuntu:22.04/jammy [amd64])
Inst vkd3d-compiler (1.3~jammy-1 winehq:jammy [amd64])
Inst wine64 (6.0.3~repack-1 Ubuntu:22.04/jammy [amd64])
Inst wine (6.0.3~repack-1 Ubuntu:22.04/jammy [all])
Inst libcapi20-3 (1:3.27-3 Ubuntu:22.04/jammy [amd64])
Conf fonts-wine (6.0.3~repack-1 Ubuntu:22.04/jammy [all])
Conf libpango1.0-dev (1.50.6+ds-2ubuntu1 Ubuntu:
Conf pango1.0-tools (1.50.6+ds-2ubuntu1 Ubuntu:
Conf gir1.2-pango-1.0 (1.50.6+ds-2ubuntu1 Ubuntu:
Conf libpangoxft-1.0-0 (1.50.6+ds-2ubuntu1 Ubuntu:
Conf libpangoft2-1.0-0 (1.50.6+ds-2ubuntu1 Ubuntu:
Conf libpango-1.0-0 (1.50.6+ds-2ubuntu1 Ubuntu:
Conf libpangocairo-1.0-0 (1.50.6+ds-2ubuntu1 Ubuntu:
Conf libstb0 (0.0~git2021091
Conf libfaudio0 (22.02-1 Ubuntu:22.04/jammy [amd64])
Conf libvkd3d-shader1 (1.3~jammy-1 winehq:jammy [amd64])
Conf libvkd3d1 (1.3~jammy-1 winehq:jammy [amd64])
Conf libz-mingw-w64 (1.2.11+dfsg-4 Ubuntu:22.04/jammy [all])
Conf libwine (6.0.3~repack-1 Ubuntu:22.04/jammy [amd64])
Conf vkd3d-compiler (1.3~jammy-1 winehq:jammy [amd64])
Conf wine64 (6.0.3~repack-1 Ubuntu:22.04/jammy [amd64])
Conf wine (6.0.3~repack-1 Ubuntu:22.04/jammy [all])
Conf libcapi20-3 (1:3.27-3 Ubuntu:22.04/jammy [amd64])
yx@yx-HP:~$
Revision history for this message
|
#8 |
1. Explanation to "Schlüssel ist im veralteten Schlüsselbund trusted.gpg gespeichert (/etc/apt/
In the past all cryptographic keys for apt were stored in /etc/apt/
For the time being that warning can be ignored.
2. Explanation to "Aktualisierung für 17 Pakete verfügbar"
There is a new function in updates named "phased updates". When there is a new version of a package, it is not made available to everybody at the same time, but only gradually over a period of a few days, see https:/
It seems that from the 17 packages that were pending, you already get 7 updated now.
I suggest that you run
sudo apt full-upgrade
to install the updates that are available for you now.
3. Now for installing wine:
The output looks promising.
Your initial question was about installing wine32, so I recommend running
apt --simulate install wine wine32 wine64
Let's see whether this indicates probable success or shows a problem.
Revision history for this message
|
#9 |
So I made this:
(started the terminal in English, that may be of interest for many other people)
apt --simulate install wine wine32 wine64:
yx@yx-HP:~$ apt --simulate install wine wine32 wine64
NOTE: This is only a simulation!
apt needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
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:
libgstreamer1.
E: Unable to correct problems, you have held broken packages.
yx@yx-HP:~$
In fact, the package "wine32" does not exist alt all in the repositories of ubuntu, winehq, backports and dpkg.
libgstreamer1.0-0 and libdw1 are installed but not as :i386.
Revision history for this message
|
#10 |
"... the package "wine32" does not exist ..."
This is not true.
In the Ubuntu repositories "wine32" is a separate *.deb package, see e.g. https:/
Winehq is packaging the software in a different way, there "wine32" is not a separate *.deb package, but a "virtual package" that is delivered by winehq-devel or winehq-stable
For the dependency problem please provide the output of the command:
apt policy libgstreamer1.0-0 libdw1 libgstreamer1.
Revision history for this message
|
#11 |
And please also provide the outptu of the command
apt --simulate install wine wine32 wine64 libdw1:i386
Revision history for this message
|
#12 |
Here the demanded outputs:
yx@yx-HP:~$ apt policy libgstreamer1.0-0 libdw1 libgstreamer1.
libgstreamer1.0-0:
Installed: 1.20.3-0ubuntu1
Candidate: 1.20.3-0ubuntu1
Version table:
*** 1.20.3-0ubuntu1 500
500 http://
100 /var/lib/
1.20.1-1 500
500 http://
libdw1:
Installed: 0.188-1~bpo22.04.1
Candidate: 0.188-1~bpo22.04.1
Version table:
*** 0.188-1~bpo22.04.1 100
100 http://
100 /var/lib/
0.186-1build1 500
500 http://
libgstreamer1.
Installed: (none)
Candidate: 1.20.3-0ubuntu1
Version table:
1.
500 http://
1.20.1-1 500
500 http://
libdw1:i386:
Installed: (none)
Candidate: 0.186-1build1
Version table:
0.
100 http://
0.186-1build1 500
500 http://
yx@yx-HP:~$
yx@yx-HP:~$ apt --simulate install wine wine32 wine64 libdw1:i386
NOTE: This is only a simulation!
apt needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
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:
libdw1:i386 : Depends: libelf1:i386 (= 0.186-1build1) but it is not going to be installed
libgstreamer1.0-0 : Depends: libdw1 (>= 0.126) but it is not installable
E: Unable to correct problems, you have held broken packages.
yx@yx-HP:~$
You say:
"In the Ubuntu repositories "wine32" is a separate *.deb package, see e.g. https:/
I find there for jammy a package
6.0.3~repack-1
Downloading that link I get three files:
wine_6.
wine_6.
wine_6.
How to handle that? I had already mentioned that I have tried that package before but without success. (I have a deb package in my archive: wine32_
Its function is not clear to me, does it replace wine32 and why is it not in the standard ubuntu repository. What is special on it.
Revision history for this message
|
#13 |
"In https:/
If you open https:/
The three files
wine_6.
wine_6.
wine_6.
are the source files that have to be compiled to receive the installable packages
Further down there are all *.deb files with the installable packages (file name ending in *.deb). There is no need for manual downloading, because you better do that with the package management system that automatically resolves dependencies (or at least signals dependency problems).
The cause of your problem probably is related to the jammy-backports repository which has a lower priority set that the jammy-updates repository. The amd64 version of libdw1 is already installed from jammy-backports, but the priority settings select jammy-updates for the i386 version.
libdw1:
Installed: 0.188-1~bpo22.04.1
Candidate: 0.188-1~bpo22.04.1
Version table:
*** 0.188-1~bpo22.04.1 100
100 http://
100 /var/lib/
0.186-1build1 500
500 http://
libdw1:i386:
Installed: (none)
Candidate: 0.186-1build1
Version table:
0.
100 http://
0.186-1build1 500
500 http://
What output do you receive for the commands
grep -i pin /etc/apt/
apt policy libdw1 libelf1 libdw1:i386 libelf1:i386
apt --simulate install wine wine32 wine64 libdw1 libelf1 libdw1:i386 libelf1:i386
apt --simulate install wine wine32 wine64 libdw1:
Revision history for this message
|
#14 |
yes thank you, received, but tomorrow 06.03.23 I am not at home. I will try to work on it as soon as possible
Revision history for this message
|
#15 |
Oh yes, you said:
"click on the triangle besides" and "Further down there are all *.deb files with the installable packages (file name ending in *.deb)."
That I had not seen before. I have not downloaded yet packages, I wait for your instructions. Here the demanded output:
x@yx-HP:~$ grep -i pin /etc/apt/
grep: /etc/apt/
grep: /etc/apt/
yx@yx-HP:~$
yx@yx-HP:~$ apt policy libdw1 libelf1 libdw1:i386 libelf1:i386
libdw1:
Installed: 0.188-1~bpo22.04.1
Candidate: 0.188-1~bpo22.04.1
Version table:
*** 0.188-1~bpo22.04.1 100
100 http://
100 /var/lib/
0.186-1build1 500
500 http://
libelf1:
Installed: 0.188-1~bpo22.04.1
Candidate: 0.188-1~bpo22.04.1
Version table:
*** 0.188-1~bpo22.04.1 100
100 http://
100 /var/lib/
0.186-1build1 500
500 http://
libdw1:i386:
Installed: (none)
Candidate: 0.186-1build1
Version table:
0.
100 http://
0.186-1build1 500
500 http://
libelf1:i386:
Installed: (none)
Candidate: 0.186-1build1
Version table:
0.
100 http://
0.186-1build1 500
500 http://
yx@yx-HP:~$
yx@yx-HP:~$ apt --simulate install wine wine32 wine64 libdw1 libelf1 libdw1:i386 libelf1:i386
NOTE: This is only a simulation!
apt needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libdw1 is already the newest version (0.188-
libdw1 set to manually installed.
libelf1 is already the newest version (0.188-
libelf1 set to manually installed.
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:
libdw1 : Breaks: libdw1:i386 (!= 0.188-1~bpo22.04.1) but 0.186-1build1 is to be installed
libdw1:i386 : Breaks: libdw1 (!= 0.186-1build1) but 0.188-1~bpo22.04.1 is to be installed
libelf1 : Breaks: libelf1:i386 (!= 0.188-1~bpo22.04.1) but 0.186-1build1 is to be installed
libelf1:i386 : Breaks: libelf1 (!= 0.186-1build1) but 0.188-1~bpo22.04.1 is to be installed
E: Unable to correct problems, you have held broken packages.
yx@yx-HP:~$
yx@yx-HP:~$ apt --simulate install wine wine32 wine64 libdw1:
NOTE: This is only a simulation!
apt needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
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:
libdw1:i386 : Depends: libelf1:i386 (= 0.188-1~bpo22.04.1) but it is not installable
E: Unable to correct problems, you have held broken packages.
yx@yx-HP:~$
Revision history for this message
|
#16 |
What output do you receive for
apt --simulate install wine wine32 wine64 libdw1:
Revision history for this message
|
#17 |
yx@yx-HP:~$ apt --simulate install wine wine32 wine64 libdw1:
NOTE: This is only a simulation!
apt needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
libmozjs-91-0 linux-headers-
linux-
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
fonts-wine gir1.2-pango-1.0 glib-networking
gstreamer1.
libavahi-
libcairo-
libdbus-1-3:i386 libdecor-0-0:i386 libdecor-
libdrm-
libgbm1:i386 libgdk-
libglx0:i386 libgpm2:i386 libgraphite2-3:i386 libgsm1:i386 libgstreamer-
libgstreamer-
libjack-
libncursesw6:i386 libodbc2:i386 libogg0:i386 libopenal1:i386 libopus0:i386 liborc-0.4-0:i386 libosmesa6:i386
libpango-1.0-0 libpango-1.0-0:i386 libpango1.0-dev libpangocairo-1.0-0 libpangocairo-
libpangoft2-
libraw1394-
libsndfile1:i386 libsndio7.0:i386 libsoup2.4-1:i386 libspeex1:i386 libsqlite3-0:i386 libstb0 libstb0:i386
libtag1v5:i386 libtag1v5-
libv4l-0:i386 libv4lconvert0:i386 libvisual-
libvorbis0a:i386 libvorbisenc2:i386 libvpx7:i386 libvulkan1:i386 libwavpack1:i386 libwayland-
libwayland-
libxcb-
libxcb-shm0:i386 libxcb-sync1:i386 libxcb-xfixes0:i386 libxcomposite1:i386 libxcursor1:i386 libxdamage1:i386
libxext6:i386 libxfixes3:i386 libxi6:i386 libxinerama1:i386 libxkbcommon0:i386 libxrandr2:i386 libxrender1:i386
libxshmfence1
ocl-icd-
Suggested packages:
gvfs:i386 libdv-bin:i386 oss-compat:i386 gpm:i386 libvisual-
odbc-
lm-sensors:i386 sndiod:i386 speex:i386 ttf-mscorefonts
gstreamer1.
playonlinux wine-binfmt wine32-
Recommended packages:
libgl1-
The following NEW packages will be installed:
fonts-wine glib-networking
libaa1:i386 libapparmor1:i386 libasound2-
libavahi-
libcairo2:i386 libcapi20-3 libcapi20-3:i386 libcdparanoia0:i386 libcups2:i386 libdatrie1:i386 libdbus-1-3:i386
libdecor-0-0:i386 libdecor-
libdrm2:i386 libdv4:i386 libdw1:i386 libedit2:i386 libelf1:i386 libfaudio0 libfaudio0:i386 libflac8:i386
libfribidi0:i386 libgbm1:i386 libgdk-
libglx-mesa0:i386 libglx0:i386 libgpm2:i386 libgraphite2-3:i386 libgsm1:i386 libgstreamer-
libgstreamer-
libjack-
libncursesw6:i386 libodbc2:i386 libogg0:i386 libopenal1:i386 libopus0:i386 liborc-0.4-0:i386 libosmesa6:i386
libpango-
libproxy1v5:i386 libpulse0:i386 libraw1394-11:i386 libsamplerate0:i386 libsdl2-2.0-0:i386 libsensors5:i386
libshout3:i386 libslang2:i386 libsndfile1:i386 libsndio7.0:i386 libsoup2.4-1:i386 libspeex1:i386 libsqlite3-0:i386
libstb0 libstb0:i386 libtag1v5:i386 libtag1v5-
libtwolame0:i386 libunwind8:i386 libv4l-0:i386 libv4lconvert0:i386 libvisual-
libvkd3d-
libwavpack1:i386 libwayland-
libwine:i386 libx11-xcb1:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-
libxcb-
libxcursor1:i386 libxdamage1:i386 libxext6:i386 libxfixes3:i386 libxi6:i386 libxinerama1:i386 libxkbcommon0:i386
libxrandr2:i386 libxrender1:i386 libxshmfence1:i386 libxslt1.1:i386 libxss1:i386 libxv1:i386 libxxf86vm1:i386
libz-mingw-w64 mesa-vulkan-
The following packages will be upgraded:
gir1.2-pango-1.0 libpango-1.0-0 libpango1.0-dev libpangocairo-1.0-0 libpangoft2-1.0-0 libpangoxft-1.0-0 pango1.0-tools
7 upgraded, 144 newly installed, 0 to remove and 10 not upgraded.
Inst libbz2-1.0:i386 (1.0.8-5build1 Ubuntu:22.04/jammy [i386])
Inst libtinfo6:i386 (6.3-2 Ubuntu:22.04/jammy [i386])
Inst libncurses6:i386 (6.3-2 Ubuntu:22.04/jammy [i386])
Inst libncursesw6:i386 (6.3-2 Ubuntu:22.04/jammy [i386])
Inst libapparmor1:i386 (3.0.4-2ubuntu2.2 Ubuntu:
Inst libdbus-1-3:i386 (1.12.20-2ubuntu4.1 Ubuntu:
Inst libelf1:i386 (0.188-1~bpo22.04.1 Ubuntu:
Inst libfribidi0:i386 (1.0.8-2ubuntu3.1 Ubuntu:
Inst libslang2:i386 (2.3.2-5build4 Ubuntu:22.04/jammy [i386])
Inst libsqlite3-0:i386 (3.37.2-2ubuntu0.1 Ubuntu:
Inst libdrm2:i386 (2.4.113-
Inst libedit2:i386 (3.1-20210910-
Inst libpcap0.8:i386 (1.10.1-4build1 Ubuntu:22.04/jammy [i386])
Inst libxext6:i386 (2:1.3.4-1build1 Ubuntu:22.04/jammy [i386])
Inst fonts-wine (6.0.3~repack-1 Ubuntu:22.04/jammy [all])
Inst libpango1.0-dev [1.50.6+ds-2] (1.50.6+ds-2ubuntu1 Ubuntu:
Inst pango1.0-tools [1.50.6+ds-2] (1.50.6+ds-2ubuntu1 Ubuntu:
Inst gir1.2-pango-1.0 [1.50.6+ds-2] (1.50.6+ds-2ubuntu1 Ubuntu:
Inst libpangoxft-1.0-0 [1.50.6+ds-2] (1.50.6+ds-2ubuntu1 Ubuntu:
Inst libpangoft2-1.0-0 [1.50.6+ds-2] (1.50.6+ds-2ubuntu1 Ubuntu:
Inst libpango-1.0-0 [1.50.6+ds-2] (1.50.6+ds-2ubuntu1 Ubuntu:
Inst libpangocairo-1.0-0 [1.50.6+ds-2] (1.50.6+ds-2ubuntu1 Ubuntu:
Inst libproxy1v5:i386 (0.4.17-2 Ubuntu:22.04/jammy [i386])
Inst glib-networking
Inst libcdparanoia0:i386 (3.10.2+
Inst libdw1:i386 (0.188-1~bpo22.04.1 Ubuntu:
Inst libunwind8:i386 (1.3.2-2build2 Ubuntu:22.04/jammy [i386])
Inst libgstreamer1.
Inst liborc-0.4-0:i386 (1:0.4.32-2 Ubuntu:22.04/jammy [i386])
Inst libgstreamer-
Inst libogg0:i386 (1.3.5-0ubuntu3 Ubuntu:22.04/jammy [i386])
Inst libopus0:i386 (1.3.1-0.1build2 Ubuntu:22.04/jammy [i386])
Inst libpixman-1-0:i386 (0.40.0-
Inst libxcb-render0:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Inst libxcb-shm0:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Inst libxrender1:i386 (1:0.9.10-1build4 Ubuntu:22.04/jammy [i386])
Inst libcairo2:i386 (1.16.0-5ubuntu2 Ubuntu:22.04/jammy [i386])
Inst libtheora0:i386 (1.1.1+
Inst libvisual-
Inst libvorbis0a:i386 (1.3.7-1build2 Ubuntu:22.04/jammy [i386])
Inst libvorbisenc2:i386 (1.3.7-1build2 Ubuntu:22.04/jammy [i386])
Inst gstreamer1.
Inst libgpm2:i386 (1.20.7-10build1 Ubuntu:22.04/jammy [i386])
Inst libaa1:i386 (1.4p5-50build1 Ubuntu:22.04/jammy [i386])
Inst libraw1394-11:i386 (2.1.2-2build2 Ubuntu:22.04/jammy [i386])
Inst libavc1394-0:i386 (0.5.4-5build2 Ubuntu:22.04/jammy [i386])
Inst libcaca0:i386 (0.99.beta19-
Inst libcairo-
Inst libdv4:i386 (1.0.0-14build1 Ubuntu:22.04/jammy [i386])
Inst libflac8:i386 (1.3.3-2ubuntu0.1 Ubuntu:
Inst libgdk-
Inst libgstreamer-
Inst libgudev-1.0-0:i386 (1:237-2build1 Ubuntu:22.04/jammy [i386])
Inst libiec61883-0:i386 (1.2.0-4build3 Ubuntu:22.04/jammy [i386])
Inst libsamplerate0:i386 (0.2.2-1build1 Ubuntu:22.04/jammy [i386])
Inst libjack-
Inst libmp3lame0:i386 (3.100-3build2 Ubuntu:22.04/jammy [i386])
Inst libmpg123-0:i386 (1.29.3-1build1 Ubuntu:22.04/jammy [i386])
Inst libasyncns0:i386 (0.8-6build2 Ubuntu:22.04/jammy [i386])
Inst libsndfile1:i386 (1.0.31-2build1 Ubuntu:22.04/jammy [i386])
Inst libx11-xcb1:i386 (2:1.7.5-1 Ubuntu:22.04/jammy [i386])
Inst libpulse0:i386 (1:15.99.
Inst libspeex1:i386 (1.2~rc1.
Inst libshout3:i386 (2.4.5-1build3 Ubuntu:22.04/jammy [i386])
Inst libtag1v5-
Inst libtag1v5:i386 (1.11.1+
Inst libtwolame0:i386 (0.4.0-2build2 Ubuntu:22.04/jammy [i386])
Inst libv4lconvert0:i386 (1.22.1-2build1 Ubuntu:22.04/jammy [i386])
Inst libv4l-0:i386 (1.22.1-2build1 Ubuntu:22.04/jammy [i386])
Inst libvpx7:i386 (1.11.0-2ubuntu2 Ubuntu:22.04/jammy [i386])
Inst libwavpack1:i386 (5.4.0-1build2 Ubuntu:22.04/jammy [i386])
Inst libxdamage1:i386 (1:1.1.5-2build2 Ubuntu:22.04/jammy [i386])
Inst libxfixes3:i386 (1:6.0.0-1 Ubuntu:22.04/jammy [i386])
Inst libsoup2.4-1:i386 (2.74.2-3 Ubuntu:22.04/jammy [i386])
Inst gstreamer1.
Inst libgraphite2-3:i386 (1.3.14-1build2 Ubuntu:22.04/jammy [i386])
Inst libharfbuzz0b:i386 (2.7.4-1ubuntu3.1 Ubuntu:
Inst libdatrie1:i386 (0.2.13-2 Ubuntu:22.04/jammy [i386])
Inst libthai0:i386 (0.1.29-1build1 Ubuntu:22.04/jammy [i386])
Inst libpango-1.0-0:i386 (1.50.6+ds-2ubuntu1 Ubuntu:
Inst libpangoft2-
Inst libpangocairo-
Inst libxv1:i386 (2:1.0.11-1build2 Ubuntu:22.04/jammy [i386])
Inst gstreamer1.0-x:i386 (1.20.1-1 Ubuntu:22.04/jammy [i386])
Inst libasound2-
Inst libatomic1:i386 (12.1.0-
Inst libavahi-
Inst libavahi-
Inst libavahi-
Inst libcups2:i386 (2.4.1op1-
Inst libwayland-
Inst libdecor-0-0:i386 (0.1.0-3build1 Ubuntu:22.04/jammy [i386])
Inst libwayland-
Inst libdecor-
Inst libdrm-amdgpu1:i386 (2.4.113-
Inst libdrm-
Inst libdrm-radeon1:i386 (2.4.113-
Inst libwayland-
Inst libgbm1:i386 (22.2.5-
Inst libwayland-
Inst libxcursor1:i386 (1:1.2.0-2build4 Ubuntu:22.04/jammy [i386])
Inst libxi6:i386 (2:1.8-1build1 Ubuntu:22.04/jammy [i386])
Inst libxinerama1:i386 (2:1.1.4-3 Ubuntu:22.04/jammy [i386])
Inst libxkbcommon0:i386 (1.4.0-1 Ubuntu:22.04/jammy [i386])
Inst libxrandr2:i386 (2:1.5.2-1build1 Ubuntu:22.04/jammy [i386])
Inst libxss1:i386 (1:1.2.3-1build2 Ubuntu:22.04/jammy [i386])
Inst libxxf86vm1:i386 (1:1.1.4-1build3 Ubuntu:22.04/jammy [i386])
Inst libsdl2-2.0-0:i386 (2.0.20+
Inst libstb0:i386 (0.0~git2021091
Inst libfaudio0:i386 (22.02-1 Ubuntu:22.04/jammy [i386])
Inst libstb0 (0.0~git2021091
Inst libfaudio0 (22.02-1 Ubuntu:22.04/jammy [amd64])
Inst libglapi-mesa:i386 (22.2.5-
Inst libllvm15:i386 (1:15.0.
Inst libsensors5:i386 (1:3.6.0-7ubuntu1 Ubuntu:22.04/jammy [i386])
Inst libxcb-dri3-0:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Inst libgl1-
Inst libxcb-dri2-0:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Inst libxcb-glx0:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Inst libxcb-
Inst libxcb-sync1:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Inst libxcb-xfixes0:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Inst libxshmfence1:i386 (1.3-1build4 Ubuntu:22.04/jammy [i386])
Inst libglx-mesa0:i386 (22.2.5-
Inst libgsm1:i386 (1.0.19-1 Ubuntu:22.04/jammy [i386])
Inst liblcms2-2:i386 (2.12~rc1-2build2 Ubuntu:22.04/jammy [i386])
Inst libodbc2:i386 (2.3.9-5 Ubuntu:22.04/jammy [i386])
Inst libsndio7.0:i386 (1.8.1-1.1 Ubuntu:22.04/jammy [i386])
Inst libvkd3d-shader1 (1.3~jammy-1 winehq:jammy [amd64])
Inst libvkd3d-
Inst libvulkan1:i386 (1.3.204.1-2 Ubuntu:22.04/jammy [i386])
Inst libvkd3d1:i386 (1.3~jammy-1 winehq:jammy [i386])
Inst libvkd3d1 (1.3~jammy-1 winehq:jammy [amd64])
Inst libz-mingw-w64 (1.2.11+dfsg-4 Ubuntu:22.04/jammy [all])
Inst libwine (6.0.3~repack-1 Ubuntu:22.04/jammy [amd64])
Inst libopenal1:i386 (1:1.19.1-2build3 Ubuntu:22.04/jammy [i386])
Inst ocl-icd-
Inst libwine:i386 (6.0.3~repack-1 Ubuntu:22.04/jammy [i386])
Inst libxcb-randr0:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Inst libxcomposite1:i386 (1:0.4.5-1build2 Ubuntu:22.04/jammy [i386])
Inst libxslt1.1:i386 (1.1.34-
Inst mesa-vulkan-
Inst vkd3d-compiler:i386 (1.3~jammy-1 winehq:jammy [i386])
Inst wine64 (6.0.3~repack-1 Ubuntu:22.04/jammy [amd64])
Inst wine32:i386 (6.0.3~repack-1 Ubuntu:22.04/jammy [i386])
Inst wine (6.0.3~repack-1 Ubuntu:22.04/jammy [all])
Inst libcapi20-3 (1:3.27-3 Ubuntu:22.04/jammy [amd64])
Inst libcapi20-3:i386 (1:3.27-3 Ubuntu:22.04/jammy [i386])
Inst libglx0:i386 (1.4.0-1 Ubuntu:22.04/jammy [i386])
Inst libgl1:i386 (1.4.0-1 Ubuntu:22.04/jammy [i386])
Inst libosmesa6:i386 (22.2.5-
Conf libbz2-1.0:i386 (1.0.8-5build1 Ubuntu:22.04/jammy [i386])
Conf libtinfo6:i386 (6.3-2 Ubuntu:22.04/jammy [i386])
Conf libncurses6:i386 (6.3-2 Ubuntu:22.04/jammy [i386])
Conf libncursesw6:i386 (6.3-2 Ubuntu:22.04/jammy [i386])
Conf libapparmor1:i386 (3.0.4-2ubuntu2.2 Ubuntu:
Conf libdbus-1-3:i386 (1.12.20-2ubuntu4.1 Ubuntu:
Conf libelf1:i386 (0.188-1~bpo22.04.1 Ubuntu:
Conf libfribidi0:i386 (1.0.8-2ubuntu3.1 Ubuntu:
Conf libslang2:i386 (2.3.2-5build4 Ubuntu:22.04/jammy [i386])
Conf libsqlite3-0:i386 (3.37.2-2ubuntu0.1 Ubuntu:
Conf libdrm2:i386 (2.4.113-
Conf libedit2:i386 (3.1-20210910-
Conf libpcap0.8:i386 (1.10.1-4build1 Ubuntu:22.04/jammy [i386])
Conf libxext6:i386 (2:1.3.4-1build1 Ubuntu:22.04/jammy [i386])
Conf fonts-wine (6.0.3~repack-1 Ubuntu:22.04/jammy [all])
Conf libpango1.0-dev (1.50.6+ds-2ubuntu1 Ubuntu:
Conf pango1.0-tools (1.50.6+ds-2ubuntu1 Ubuntu:
Conf gir1.2-pango-1.0 (1.50.6+ds-2ubuntu1 Ubuntu:
Conf libpangoxft-1.0-0 (1.50.6+ds-2ubuntu1 Ubuntu:
Conf libpangoft2-1.0-0 (1.50.6+ds-2ubuntu1 Ubuntu:
Conf libpango-1.0-0 (1.50.6+ds-2ubuntu1 Ubuntu:
Conf libpangocairo-1.0-0 (1.50.6+ds-2ubuntu1 Ubuntu:
Conf libproxy1v5:i386 (0.4.17-2 Ubuntu:22.04/jammy [i386])
Conf glib-networking
Conf libcdparanoia0:i386 (3.10.2+
Conf libdw1:i386 (0.188-1~bpo22.04.1 Ubuntu:
Conf libunwind8:i386 (1.3.2-2build2 Ubuntu:22.04/jammy [i386])
Conf libgstreamer1.
Conf liborc-0.4-0:i386 (1:0.4.32-2 Ubuntu:22.04/jammy [i386])
Conf libgstreamer-
Conf libogg0:i386 (1.3.5-0ubuntu3 Ubuntu:22.04/jammy [i386])
Conf libopus0:i386 (1.3.1-0.1build2 Ubuntu:22.04/jammy [i386])
Conf libpixman-1-0:i386 (0.40.0-
Conf libxcb-render0:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Conf libxcb-shm0:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Conf libxrender1:i386 (1:0.9.10-1build4 Ubuntu:22.04/jammy [i386])
Conf libcairo2:i386 (1.16.0-5ubuntu2 Ubuntu:22.04/jammy [i386])
Conf libtheora0:i386 (1.1.1+
Conf libvisual-
Conf libvorbis0a:i386 (1.3.7-1build2 Ubuntu:22.04/jammy [i386])
Conf libvorbisenc2:i386 (1.3.7-1build2 Ubuntu:22.04/jammy [i386])
Conf gstreamer1.
Conf libgpm2:i386 (1.20.7-10build1 Ubuntu:22.04/jammy [i386])
Conf libaa1:i386 (1.4p5-50build1 Ubuntu:22.04/jammy [i386])
Conf libraw1394-11:i386 (2.1.2-2build2 Ubuntu:22.04/jammy [i386])
Conf libavc1394-0:i386 (0.5.4-5build2 Ubuntu:22.04/jammy [i386])
Conf libcaca0:i386 (0.99.beta19-
Conf libcairo-
Conf libdv4:i386 (1.0.0-14build1 Ubuntu:22.04/jammy [i386])
Conf libflac8:i386 (1.3.3-2ubuntu0.1 Ubuntu:
Conf libgdk-
Conf libgstreamer-
Conf libgudev-1.0-0:i386 (1:237-2build1 Ubuntu:22.04/jammy [i386])
Conf libiec61883-0:i386 (1.2.0-4build3 Ubuntu:22.04/jammy [i386])
Conf libsamplerate0:i386 (0.2.2-1build1 Ubuntu:22.04/jammy [i386])
Conf libjack-
Conf libmp3lame0:i386 (3.100-3build2 Ubuntu:22.04/jammy [i386])
Conf libmpg123-0:i386 (1.29.3-1build1 Ubuntu:22.04/jammy [i386])
Conf libasyncns0:i386 (0.8-6build2 Ubuntu:22.04/jammy [i386])
Conf libsndfile1:i386 (1.0.31-2build1 Ubuntu:22.04/jammy [i386])
Conf libx11-xcb1:i386 (2:1.7.5-1 Ubuntu:22.04/jammy [i386])
Conf libpulse0:i386 (1:15.99.
Conf libspeex1:i386 (1.2~rc1.
Conf libshout3:i386 (2.4.5-1build3 Ubuntu:22.04/jammy [i386])
Conf libtag1v5-
Conf libtag1v5:i386 (1.11.1+
Conf libtwolame0:i386 (0.4.0-2build2 Ubuntu:22.04/jammy [i386])
Conf libv4lconvert0:i386 (1.22.1-2build1 Ubuntu:22.04/jammy [i386])
Conf libv4l-0:i386 (1.22.1-2build1 Ubuntu:22.04/jammy [i386])
Conf libvpx7:i386 (1.11.0-2ubuntu2 Ubuntu:22.04/jammy [i386])
Conf libwavpack1:i386 (5.4.0-1build2 Ubuntu:22.04/jammy [i386])
Conf libxdamage1:i386 (1:1.1.5-2build2 Ubuntu:22.04/jammy [i386])
Conf libxfixes3:i386 (1:6.0.0-1 Ubuntu:22.04/jammy [i386])
Conf libsoup2.4-1:i386 (2.74.2-3 Ubuntu:22.04/jammy [i386])
Conf gstreamer1.
Conf libgraphite2-3:i386 (1.3.14-1build2 Ubuntu:22.04/jammy [i386])
Conf libharfbuzz0b:i386 (2.7.4-1ubuntu3.1 Ubuntu:
Conf libdatrie1:i386 (0.2.13-2 Ubuntu:22.04/jammy [i386])
Conf libthai0:i386 (0.1.29-1build1 Ubuntu:22.04/jammy [i386])
Conf libpango-1.0-0:i386 (1.50.6+ds-2ubuntu1 Ubuntu:
Conf libpangoft2-
Conf libpangocairo-
Conf libxv1:i386 (2:1.0.11-1build2 Ubuntu:22.04/jammy [i386])
Conf gstreamer1.0-x:i386 (1.20.1-1 Ubuntu:22.04/jammy [i386])
Conf libasound2-
Conf libatomic1:i386 (12.1.0-
Conf libavahi-
Conf libavahi-
Conf libavahi-
Conf libcups2:i386 (2.4.1op1-
Conf libwayland-
Conf libdecor-0-0:i386 (0.1.0-3build1 Ubuntu:22.04/jammy [i386])
Conf libwayland-
Conf libdecor-
Conf libdrm-amdgpu1:i386 (2.4.113-
Conf libdrm-
Conf libdrm-radeon1:i386 (2.4.113-
Conf libwayland-
Conf libgbm1:i386 (22.2.5-
Conf libwayland-
Conf libxcursor1:i386 (1:1.2.0-2build4 Ubuntu:22.04/jammy [i386])
Conf libxi6:i386 (2:1.8-1build1 Ubuntu:22.04/jammy [i386])
Conf libxinerama1:i386 (2:1.1.4-3 Ubuntu:22.04/jammy [i386])
Conf libxkbcommon0:i386 (1.4.0-1 Ubuntu:22.04/jammy [i386])
Conf libxrandr2:i386 (2:1.5.2-1build1 Ubuntu:22.04/jammy [i386])
Conf libxss1:i386 (1:1.2.3-1build2 Ubuntu:22.04/jammy [i386])
Conf libxxf86vm1:i386 (1:1.1.4-1build3 Ubuntu:22.04/jammy [i386])
Conf libsdl2-2.0-0:i386 (2.0.20+
Conf libstb0:i386 (0.0~git2021091
Conf libfaudio0:i386 (22.02-1 Ubuntu:22.04/jammy [i386])
Conf libstb0 (0.0~git2021091
Conf libfaudio0 (22.02-1 Ubuntu:22.04/jammy [amd64])
Conf libglapi-mesa:i386 (22.2.5-
Conf libllvm15:i386 (1:15.0.
Conf libsensors5:i386 (1:3.6.0-7ubuntu1 Ubuntu:22.04/jammy [i386])
Conf libxcb-dri3-0:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Conf libgl1-
Conf libxcb-dri2-0:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Conf libxcb-glx0:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Conf libxcb-
Conf libxcb-sync1:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Conf libxcb-xfixes0:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Conf libxshmfence1:i386 (1.3-1build4 Ubuntu:22.04/jammy [i386])
Conf libglx-mesa0:i386 (22.2.5-
Conf libgsm1:i386 (1.0.19-1 Ubuntu:22.04/jammy [i386])
Conf liblcms2-2:i386 (2.12~rc1-2build2 Ubuntu:22.04/jammy [i386])
Conf libodbc2:i386 (2.3.9-5 Ubuntu:22.04/jammy [i386])
Conf libsndio7.0:i386 (1.8.1-1.1 Ubuntu:22.04/jammy [i386])
Conf libvkd3d-shader1 (1.3~jammy-1 winehq:jammy [amd64])
Conf libvkd3d-
Conf libvulkan1:i386 (1.3.204.1-2 Ubuntu:22.04/jammy [i386])
Conf libvkd3d1:i386 (1.3~jammy-1 winehq:jammy [i386])
Conf libvkd3d1 (1.3~jammy-1 winehq:jammy [amd64])
Conf libz-mingw-w64 (1.2.11+dfsg-4 Ubuntu:22.04/jammy [all])
Conf libwine (6.0.3~repack-1 Ubuntu:22.04/jammy [amd64])
Conf libopenal1:i386 (1:1.19.1-2build3 Ubuntu:22.04/jammy [i386])
Conf ocl-icd-
Conf libwine:i386 (6.0.3~repack-1 Ubuntu:22.04/jammy [i386])
Conf libxcb-randr0:i386 (1.14-3ubuntu3 Ubuntu:22.04/jammy [i386])
Conf libxcomposite1:i386 (1:0.4.5-1build2 Ubuntu:22.04/jammy [i386])
Conf libxslt1.1:i386 (1.1.34-
Conf mesa-vulkan-
Conf vkd3d-compiler:i386 (1.3~jammy-1 winehq:jammy [i386])
Conf wine64 (6.0.3~repack-1 Ubuntu:22.04/jammy [amd64])
Conf wine32:i386 (6.0.3~repack-1 Ubuntu:22.04/jammy [i386])
Conf wine (6.0.3~repack-1 Ubuntu:22.04/jammy [all])
Conf libcapi20-3 (1:3.27-3 Ubuntu:22.04/jammy [amd64])
Conf libcapi20-3:i386 (1:3.27-3 Ubuntu:22.04/jammy [i386])
Conf libglx0:i386 (1.4.0-1 Ubuntu:22.04/jammy [i386])
Conf libgl1:i386 (1.4.0-1 Ubuntu:22.04/jammy [i386])
Conf libosmesa6:i386 (22.2.5-
yx@yx-HP:~$
Revision history for this message
|
#18 |
It seems that this was the trick.
I expect that the same command (without "--simulate" and with "sudo" in front) will install wine32 as desired.
sudo apt install wine wine32 wine64 libdw1:
Revision history for this message
|
#19 |
ok, let me try it tomorrow morning. I will pass the result.
But can you explain me why ubuntu makes it so very complicated. I mean wine is used by many people and win32 programs are still many. How can that be so neglected. Otherwise, I have checked several forums and I could not find many qustions abou this subject.
Revision history for this message
|
#20 |
The root cause is not wine itself, but the problem only becomes visible with the attempt to install software, that needs both 32bit and 64bit libraries. wine is one of them, steam is another one.
That is the crucial information:
libdw1:
Installed: 0.188-1~bpo22.04.1
Candidate: 0.188-1~bpo22.04.1
Version table:
*** 0.188-1~bpo22.04.1 100
100 http://
100 /var/lib/
0.186-1build1 500
500 http://
You have the version from jammy-backports installed which has a higher version number (0.188-...) but lower pin priority (100) than the version from the main jammy repository which has a lower version number (0.186-...) but a higher pin priority (500).
I do not know what has lead to that situation (maybe manual installation or manual change of pin priorities after installation).
wine32 requires libdw1:i386 in addition to the already-installed libdw1 package.
The package management now ends up with a conflict between two rules:
- select the package with the highest priority (prio 500 - version 0.186-... from the main repository)
- both libdw1 packages need to be the same version
Manually telling the package management system to select the i386 packages with the lower priority but higher version number solves the conflict.
As already told, this is not a problem with wine. Just the simple command
apt --sinulate install libdw1:i386
will show the same conflict (without mentioning wine at all).
Revision history for this message
|
#21 |
Yes, it is working now! I wanted to post the terminal output, but the limited cache has cut of the start. But it worked straight through without any warning messages. Großen Dank an Manfred
Revision history for this message
|
#22 |
Thanks Manfred Hampl, that solved my question.
Revision history for this message
|
#23 |
Let me ask one more question:
I cannot say that have completely understood the procedure, but anyway it works. But: After installation I missed the downloaded packages in "/var/cache/
That is essential for me, because I want to install wine32 also on other machines. So what do I have to do in order to get all the required .deb packages?
Revision history for this message
|
#24 |
Re: I missed the downloaded packages in "/var/cache/
As far as I can remember, there was a change a few Ubuntu releases ago, that the default is deleting the files in /var/cache/
I assume that this can be changed by some settings in the /etc/apt/
There is a note in the man pages for apt-get:
APT::Clean-
Revision history for this message
|
#25 |
As I had said, I do usually update the system with synaptic. My Synaptic is set that is does not delete the downloaded packages in "/var/cache/
So what happened now with the command
"apt --simulate install wine wine32 wine64 libdw1:
was unsual. I thought it may have to do with these strange packages "libdw1:
Anyway, I just install jammy on my experimental disk completely new in order to check everything again. In the course of that I have to try again the wine 32, let me see what will happen with the packages.
Revision history for this message
|
#26 |
The meaning of "libdw1:
The libdw1 package in architecture i386 and with version number 0.188-1~bpo22.04.1.
This is a combination of ":i386" for specifying a different architecture and "=0.188-
The file name for that package in any case is libdw1_
I have not looked into the details of synaptic, but instead of the "apt install" command it of course must be possible to do the same also in synaptic.
Did synaptic tell something about unsolvable dependencies at the beginning?
Remark:
There is an "apt download" command to just download the package files. This should allow downloading the package file for local distribution.
And there are programs like apt-cacher-ng that help setting up a local package cache server.
Revision history for this message
|
#27 |
Re: As far as I can remember, there was a change a few Ubuntu releases ago...
In the apt settings I find this:
/etc/apt/
APT::Archives:
APT::Archives:
APT::Archives:
I interprete it as 30 days max age, I think it has always been like that. But I would like to add what you have proposed from manpage apt-get, but I am uncertain about the correct form:
APT::Clean−
APT::Archives:
I have successfully reinstalled the whole system and are ready to work on downloading wine again. (but would like to cache the packets)
I had just prepared this above to post when I saw you new comment. Let me work on it, seems to be interesting.
Revision history for this message
|
#28 |
If I take
APT::Archives:
as model, then I assume that the correct syntax must be
APT::Clean-
APT::Archives:
(a plain minus character instead of an em-dash, space for separating the "off" value from the parameter name and a semicolon at the end)
Revision history for this message
|
#29 |
Here again the attempt to install wine32. I had updated the new installed system, I had included backports and wine sources and tried the same as it had already been successful before. But did not work: libdw1:i386' was not found, libelf1:i386' was not found
What I have not understood: That repository "deb http://
yx@yx-HP:~$ sudo apt install wine wine32 wine64 libdw1:
[sudo] password for yx:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package libdw1:i386 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
libdw1
Package libelf1:i386 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
libelf1
E: Version '0.188-
E: Version '0.188-
yx@yx-HP:~$
Revision history for this message
|
#30 |
"the new installed system"
Which Ubuntu release did you install and from which medium?
"I had included backports and wine sources"
What exactly have you included?
Which "wine sources"?
"but the key is missing."
Which key?
For diagnostics purposes, what is the output of
uname -a
lsb_release -crid
dpkg --print-
dpkg --print-
apt policy
Revision history for this message
|
#31 |
I had included:
1) deb https:/
with its key: winehq-archive.key
(meanwhile removed, a bit strange: synaptic showed packages originating from that source but the source itself was not indicated the package sources)
2) in synaptic developer options "jammy proposed" is activated
3) Than I have tried also this, but it threw a massege that there is no Release file (sorry not the key is missing):
deb http://
Here the terminal output:
yx@yx-HP:~$ uname -a
Linux yx-HP 5.15.0-68-generic #75-Ubuntu SMP Fri Feb 24 13:01:57 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
yx@yx-HP:~$
yx@yx-HP:~$ lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Codename: jammy
yx@yx-HP:~$
yx@yx-HP:~$ dpkg --print-
amd64
yx@yx-HP:~$
yx@yx-HP:~$ dpkg --print-
i386
yx@yx-HP:~$
yx@yx-HP:~$ apt policy
Package files:
100 /var/lib/
release a=now
500 http://
release v=22.04,
origin archive.ubuntu.com
500 http://
release v=22.04,
origin archive.ubuntu.com
500 http://
release v=22.04,
origin archive.ubuntu.com
500 http://
release v=22.04,
origin archive.ubuntu.com
500 http://
release v=22.04,
origin archive.ubuntu.com
500 http://
release v=22.04,
origin archive.ubuntu.com
500 http://
release v=22.04,
origin archive.ubuntu.com
500 http://
release v=22.04,
origin archive.ubuntu.com
500 http://
release v=22.04,
origin archive.ubuntu.com
500 http://
release v=22.04,
origin archive.ubuntu.com
500 http://
release v=22.04,
origin archive.ubuntu.com
500 http://
release v=22.04,
origin archive.ubuntu.com
500 http://
release v=22.04,
origin archive.ubuntu.com
500 http://
release v=22.04,
origin archive.ubuntu.com
500 http://
release v=22.04,
origin archive.ubuntu.com
Pinned packages:
yx@yx-HP:~$
Revision history for this message
|
#32 |
You have activated jammy-proposed instead of jammy-backports!
Revision history for this message
|
#33 |
Additional remark:
If you want to install the Ubuntu-provided version of wine, then it does not make any sense to add the winehq repository. (It's not in the list of repositories any more, so it seems that this has already been dealt with).
Revision history for this message
|
#34 |
yes ok, I have confused backports with proposed. But I had activated the same sources as were activated in the first attempt, just in order to make sure to have the neccessary sources available.
Now what is still unclear to me: In which source are these missing packages:
E: Version '0.188-
E: Version '0.188-
what sources exactly do I have to include?
Revision history for this message
|
#35 |
libdw1:i386 version 0.188-1~bpo22.04.1 is only in jammy-backports, see https:/
Adding the version number to the command should only be necessary in special cases.
What happens if you just try installing "wine wine64 wine32"?
Revision history for this message
|
#36 |
I have discovered one problem: The settings in synaptic were set only to security updates! Meanwhile I have also learned a bit more about backports (had no experience in it). So something got clear to me: Backport packages are not selected when apt tries to resolve depenencies, so they must be selected individually. That is the reason they have to be mentioned in the apt install command
I did this now:
I have enabled full updates, updated the system. Than try again:
yx@yx-HP:~$ sudo apt install wine wine32 wine64 libdw1:
[sudo] password for yx:
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:
libcurl4:i386 : Depends: libldap-2.5-0:i386 (>= 2.5.4) but it is not installable
libpcap0.8:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not installable
libsdl2-2.0-0:i386 : Depends: libpulse0:i386 (>= 0.99.1) but it is not installable
libusb-1.0-0:i386 : Depends: libudev1:i386 (>= 183) but it is not installable
libwine:i386 : Depends: libldap-2.5-0:i386 (>= 2.5.4) but it is not installable
libxml2:i386 : Depends: libicu70:i386 (>= 70.1-1~) but it is not installable
E: Unable to correct problems, you have held broken packages.
yx@yx-HP:~$
Now libdw1 and libelf1 have disappeared but we have some new problems. I guess the solution is in the same way, but I would like to get some clear advises.
Re: What happens if you just try installing "wine wine64 wine32"?
yx@yx-HP:~$ sudo apt install wine wine64 wine32
[sudo] password for yx:
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:
libcurl4:i386 : Depends: libldap-2.5-0:i386 (>= 2.5.4) but it is not installable
libgstreamer1.
libpcap0.8:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not installable
libsdl2-2.0-0:i386 : Depends: libpulse0:i386 (>= 0.99.1) but it is not installable
libusb-1.0-0:i386 : Depends: libudev1:i386 (>= 183) but it is not installable
libwine:i386 : Depends: libldap-2.5-0:i386 (>= 2.5.4) but it is not installable
libxml2:i386 : Depends: libicu70:i386 (>= 70.1-1~) but it is not installable
E: Unable to correct problems, you have held broken packages.
yx@yx-HP:~$
Revision history for this message
|
#37 |
Which sources do you now have activated out of the list: jammy, jammy-updates jammy-security jammy-backports, jammy-proposed
Synaptic can show from which origin the packages have been installed, are there any packages listed from jammy-propsed?
Revision history for this message
|
#38 |
The good news: it works!
What have I done:
1) activation of proposed, the result was that only libwine remained.
2) activation of winehq, the result was the installation was successfull
I would have liked to post the terminal output, but due to limited terminal cash most of that is lost. (How can I enlarge the cash?)
So the conclusion is: The installation of wine 32 requires proposed and winehq repositories. Shame over ubuntu to make it so complicated.
Remarkable this: As I had already mentioned before, during the first attempt all the downloaded packes in /var/apt/
APT::Archives:
But I was faster, after finish of download and before the installation was finished I have copied them to another folder. It is a bit strange.
With assistance of synaptic I have figured out which packages are coming from which sources:
backports_main:
libdebuginfod-
libelf1_
libelf1_
libdebuginfod1_
libdw1_
libdw1_
winehq:
libvkd3d-shader1
libvkd3d-
libvkd3d1
libvkd3d1:i386
vkd3d-compiler:i386
proposed_main:
a/apt/libapt-
a/apt/apt_
s/systemd/
s/systemd/
x/xorg-
x/xorg-
s/systemd/
s/systemd/
s/systemd/
s/systemd/
p/pulseaudio/
p/pulseaudio/
u/ubuntu-
u/update-
s/systemd/
s/systemd/
a/apt/apt-
i/icu/libicu70_
i/icu/libicu70_
n/netplan.
s/systemd/
s/systemd/
n/netplan.
u/update-
u/update-
d/dnsmasq/
f/fwupd/
g/gdm3/
libc/libcanberr
g/grub2/
g/grub2/
g/grub2/
g/grub2/
libc/libcanberr
libc/libcanberr
libc/libcanberr
f/fwupd/
f/fwupd/
g/gdm3/
g/gjs/libgjs0g_
o/openldap/
o/openldap/
o/openldap/
m/mozjs102/
p/pulseaudio/
p/pulseaudio/
p/pulseaudio/
p/pulseaudio/
n/net-snmp/
n/net-snmp/
l/linux-
l/linux/
l/linux/
l/linux-
l/linux-
l/linux-
l/linux/
l/linux/
l/linux/
s/system-
s/system-
s/system-
s/system-
t/thermald/
u/update-
u/update-
x/xorg-
x/xorg-
g/gjs/gjs_
libc/libcanberr
p/pulseaudio/
Revision history for this message
|
#39 |
I do not trust your assessment, because you activated jammy-proposed. It is advised not to use -proposed unless you want to help testing package updates before they are published for everyone. See e.g. https:/
In comment #30 I have already asked, how you did that new installation (from which *.iso file).
The version that you use for installing has an influence on the list of repositories that you need.
If you use the 22.04 installer iso, then you just have packages installed from the "jammy" repository
If you use the 22.04.1 or 22.04.2 installer iso, then you have some packages installed from the "jammy-updates" and/or "jammy-security" repository. That means that you also need jammy-updates respectively jammy-security activated afterwards, or you may run into version conflicts with some packages.
Revision history for this message
|
#40 |
yes, of course the case with the proposed packages is problematic. But I still use it in the experimental installation only.
In #30 you had asked for the release and the medium (USB stick, CD, network), but you ment the point release, that was not clear to me.
Actually the installation was made based on an iso file 22.04.0, no point release. My proceedure is: After installation I make a complete update and copy all packages into a private repository. Before I try further installations (like wine) I make complete update and add new packages to the repository. With "dpkg --compare-versions" I identify old packages and remove them from the repository.
From my understanding, whem the private repo contains all updates, it should be equivalent to the point releases. I have now made the recent installation completely from the original 22.04.0 and the updates and other programs from the private repo. Except wine that worked fine.
I need that repo because I have to install ubuntu also on other machines with no internet access.
Revision history for this message
|
#41 |
What you write does not make sense to me.
You install from the 22.04.0 iso file and do a full update/upgrade afterwards.
This should either set up the -backports repository in a way that updates are also installed from there, or that NO updates are installed from there.
The situation
Some amd64 packages are already installed from -backports, but the priority settings prefer other versions for the equivalent i386 packages from outside -backports
should not happen at all.
I guess I have to set up a test system myself to verify that.
Revision history for this message
|
#42 |
Yes a good idea to set up the system yourself. I am waiting interestingly for results.
Revision history for this message
|
#43 |
"Works for me."
I have set up a test system from the Ubuntu 22.04 installer iso file and installing wine works without problem.
What I did:
I installed from the Ubuntu 22.04 amd64 iso (I already had a copy, I assume that it is the same as https:/
When installing I selected "download updates" and "install third party software"
after the initial reboot I ran "sudo apt update && sudo apt full-upgrade" and rebooted again
Then I ran "sudo apt install wine wine64 wine32" and wine was correctly installed without any dependency problem.
Note: During the whole process no package from the -backports repository or foreign sources (e.g. winehq) was ever installed.
I assume that your problem was caused by mixing Ubuntu repositories with the foreign winehq sources.
Remark: I installed the "standard" Ubuntu flavor, not mate.
If you have a problem with ubuntu-mate, then you probably better ask at https:/
Revision history for this message
|
#44 |
yes I have noticed that. So I will do exactly the same procedure but with Mate. But I do not believe that the winehq repo is causing the problems because I had already all these difficulties long before I had included the wine repo.
You say it could also be a Mate problem, maybe but I have always assumed that standard and Mate are identical concerning the package system. But finally we don't know that.
I will let you know the result.
Revision history for this message
|
#45 |
I was sick for some days, could not work on the case. But now the results:
I installed from my USB stick 22.04.0 what I had always used. I did not select "download updates" becuase that requires WiFi what I do not have. After first reboot I organised internet connection through modem. Than I performed "sudo apt update && sudo apt full-upgrade". About 874 MB were downloaded and installed.
Than I performed "sudo apt install wine wine64 wine32", what did not cause messages of broken packages and 267MB have been downloaded and installed. It is working now!
The difference to the old procedure was just only in which way the updates and wine have been installed (i.e. the apt command). I had always used synaptic's update function any time I had been working on the system. I assume that in the very first days of Mate 22.04 there was a real problem, which had been forwarded through the step by step updating processes (but how is unclear). Anyway jammy was quite buggy in other cases. I do not believe that the winehq source is the reason for the problems because I had included that in a quite late stage of the experiments.