|
Problem with broken package wine i386
Hi Guys,
I hope you can help me with this problem. I got the following notification in the package manager on Ubuntu 20.04 Code:
Broken dependencies Package -> wine:i386 Installed Version -> 1:16.5-0ubuntu14 Description -> Microsoft Windows Compatibiliity Layer (meta-package)Code:
You might want to run 'apt --fix-broken install' to correct theseI tried the suggested command but there are some errors at the output Code:
Do you want to continue? [Y/n] |
Oh dear, I think you need the libs lecture.
64 bit binaries reference 64 bit libraries. Ditto for 32bit binaries, and 32 ≠ 64. 32bit systems use /lib & /usr/lib, and sadly, on most distros, 64bit systems use /lib, & /usr/lib as well. Now wine translates windows system calls into Posix ones So on a 64bit system, with a 64bit wine running a 64bit windows program all is good. But most windows software is 32bit, not 64bit. 32bit windows software needs a 32bit wine and 32bit libs. Slackware and Fedora, to my knowledge use /lib for 32bit, & /lib64 for 64bit. There may be others. Slackware also uses a special compile of wine source to get a 64 and 32 bit wine package, and offers multilib packages for providing the 32bit libraries. The messages you have are the sort of thing you get when you try to install a 32bit wine with no 32bit libs really on a 64bit OS. See how the distro tells you to handle installing 32bit wine, or install a 32bit system as well. You could alternatively install a multilib system, like Slackware or some other. |
Thanks for your help
Hello business_kid,
I am pretty new with Ubuntu and I don't know how to implement your advice. I want to fix the problem I have with the package manager because I can't upgrade my Ubuntu system (sudo apt-get upgrade). I don't want to install wine or any other package or software just solve this issue. I have Ubuntu 20.04 in 64 bits |
Quote:
First of all, manually delete the .deb files mentioned at the end. Then, run Code:
sudo dpkg configure --all |
I' also like to see the output of
Code:
dpkg-query -Wf'${db:Status-Abbrev}${binary:Package}:${Architecture}\n'|sed '/:i386$/!d' |
Hi guys,
I deleted all four files and this is the output for the first command Code:
levalsac@FocalFossa:/var/cache/apt/archives$ sudo dpkg configure --allCode:
levalsac@FocalFossa:/var/cache/apt/archives$ sudo apt --fix-broken installCode:
levalsac@FocalFossa:/var/cache/apt/archives$ dpkg-query -Wf'${db:Status-Abbrev}${binary:Package}:${Architecture}\n'|sed '/:i386$/!d' |
The first command should have been
Code:
sudo dpkg --configure -aCode:
sudo apt-get purge wine:i386 wine-staging-i386:i386Code:
dpkg -C |
I noticed in one of your replies that you're running 20.04 however you're downloading wine for 16.04, Xenial.
Code:
Get:1 http://us.archive.ubuntu.com/ubuntu xenial/universe i386 wine1.6-i386 i386 1:1.6.2-0ubuntu14 [15,8 MB]Code:
https://dl.winehq.org/wine-builds/ubuntu/ focal mainNot sure if that's going to help but it will get you the correct version. |
Be careful also, because you may have x86_64, but apt is capable of grabbing i386 packages and then the headaches start. If your OS is 64bit, you can only run x86_64 apps (e.g. wine-x86_64 and windows 64bit apps)which are few and far between)
|
Well, strictly speaking you can mix 64 and 32-bit packages in a Debian-based system, but the multiarch concept is more evolved there than say in Slackware, SUSE or RedHed-based distros where it's just the matter of /usr/lib vs. /usr/lib64, so you shouldn't attempt this without first understanding how it works.
In case you're wondering why Debian implements it in such a complicated way, that's all because of so many architectures Debian ships with: see the case for multiarch. |
| All times are GMT -5. The time now is 10:17 AM. |