Wine installer broken in non ahs version (Solved) [Solved]
Posted: Wed Mar 31, 2021 11:43 pm
MX Linux Forum
Support for MX and antiX Linux distros
http://www.forum.mxlinux.org/
Wine installer broken in non ahs version (Solved)
Page 1 of 1
Re: Wine installer broken in non ahs version
Posted: Wed Mar 31, 2021 11:50 pm
There's nothing wrong with MX Package Installer itself (there is no separate "wine installer.") The problem is on your system, but as you haven't posted your Quick System Info we couldn't say what that problem might be. I'm guessing your MX Repo mirror but I need the QSI to confirm this.
Re: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 12:45 am
this happend on two different computers using the non ahs iso provided on the mxlinux website
i tried to install it via synaptic package manager but than wanted to basically nuke the entire system
i then tried to manually add the repo provided from the winehq site and that would not work either
i don't understand how a repo problem falls into it's my computer
i tried to install it via synaptic package manager but than wanted to basically nuke the entire system
i then tried to manually add the repo provided from the winehq site and that would not work either
i don't understand how a repo problem falls into it's my computer
Re: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 12:46 am
Code: Select all
System:
Host: <filter> Kernel: 4.19.0-16-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-16-amd64
root=UUID=<filter> ro quiet splash
Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4
dm: LightDM 1.26.0 Distro: MX-19.3_x64 patito feo November 11 2020
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Desktop Mobo: ASRock model: N68C-GS FX serial: <filter>
BIOS: American Megatrends v: P1.40 date: 10/31/2012
CPU:
Topology: 6-Core model: AMD Phenom II X6 1055T bits: 64 type: MCP arch: K10
family: 10 (16) model-id: A (10) stepping: N/A microcode: 10000DC
L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 33755
Speed: 1141 MHz min/max: 800/2800 MHz boost: enabled Core speeds (MHz): 1: 916
2: 804 3: 872 4: 804 5: 804 6: 1278
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass status: Not affected
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA GM107 [GeForce GTX 750 Ti] vendor: eVga.com. driver: nvidia
v: 455.45.01 bus ID: 02:00.0 chip ID: 10de:1380
Display: x11 server: X.Org 1.20.4 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv resolution: 1366x768~60Hz
OpenGL: renderer: GeForce GTX 750 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 455.45.01
direct render: Yes
Audio:
Device-1: NVIDIA MCP61 High Definition Audio vendor: ASRock
driver: snd_hda_intel v: kernel bus ID: 00:05.0 chip ID: 10de:03f0
Device-2: NVIDIA vendor: eVga.com. driver: snd_hda_intel v: kernel
bus ID: 02:00.1 chip ID: 10de:0fbc
Device-3: N/A type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-2:2
chip ID: 534d:0021
Sound Server: ALSA v: k4.19.0-16-amd64
Network:
Device-1: NVIDIA MCP61 Ethernet vendor: ASRock 939NF6G-VSTA Board
type: network bridge driver: forcedeth v: kernel port: d080 bus ID: 00:07.0
chip ID: 10de:03ef
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 335.36 GiB used: 9.25 GiB (2.8%)
ID-1: /dev/sda model: SATA SSD size: 223.57 GiB block size: physical: 512 B
logical: 512 B speed: 3.0 Gb/s serial: <filter> rev: 61.3 temp: 33 C scheme: MBR
ID-2: /dev/sdb type: USB vendor: Seagate model: Expansion size: 111.79 GiB
block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0707
Partition:
ID-1: / raw size: 221.54 GiB size: 217.06 GiB (97.98%) used: 9.25 GiB (4.3%)
fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 2.00 GiB used: 1.2 MiB (0.1%) fs: swap
swappiness: 15 (default 60) cache pressure: 100 (default) dev: /dev/sda2
Sensors:
System Temperatures: cpu: 28.9 C mobo: N/A gpu: nvidia temp: 30 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 40%
Repos:
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo/ buster main non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info:
Processes: 257 Uptime: 4h 13m Memory: 3.85 GiB used: 1.59 GiB (41.4%)
Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8
Shell: quick-system-in running in: quick-system-in inxi: 3.0.36
Re: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 12:50 am
Your MX mirror hasn't been updated in almost a month. Upon installation MX tries to use a nearby mirror so all of your machines probably have the same (broken) one.
Run MX Repo Manager from the main menu and change your MX mirror to one of these:
in a terminal to load the new mirror's package list. After installing any updates that are found try installing wine from MX Package Installer, Popular Applications. Don't add any 3rd-party repos, use the version that's been tested to work in MX, from the package installer. I bet it will work.
Run MX Repo Manager from the main menu and change your MX mirror to one of these:
- Italy, Milan - http://it.mxrepo.com
- Netherlands, Alblasserdam - http://nl.mxrepo.com
- United States, Los Angeles CA - http://la.mxrepo.com
- United States, Salt Lake City UT - http://mxrepo.com
Code: Select all
sudo apt updateRe: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 1:15 am
Still the same problem
I might just switch over to the AHS version at this point this seems like a non ahs version iso defaults issue to me
I might just switch over to the AHS version at this point this seems like a non ahs version iso defaults issue to me
Re: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 1:35 am
Same problem with me .My desktop PC is back from the repair and I have reinstalled everything yesterday
And this morning, after about 60 updates, the same error message.
I use the mirror Netherlands, Alblasserdam
Curiously, the few Windows applications I use still work (I have a bad habit of ignoring error messages as long as everything is still running).
[/code]
And this morning, after about 60 updates, the same error message.
I use the mirror Netherlands, Alblasserdam
Curiously, the few Windows applications I use still work (I have a bad habit of ignoring error messages as long as everything is still running).
Code: Select all
[code]
Snapshot created on: 20210315_1348
System: Host: <filter> Kernel: 5.8.0-3-amd64 x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.8.0-3-amd64
root=UUID=<filter> ro quiet splash
Desktop: Fluxbox 1.3.7 info: tint2 dm: LightDM 1.26.0
Distro: MX-19.3_ahs_x64 patito feo November 11 2020
base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: Gigabyte model: B550M S2H v: x.x serial: <filter>
BIOS: American Megatrends v: F3 date: 08/20/2020
CPU: Topology: 12-Core model: AMD Ryzen 9 3900X bits: 64 type: MT MCP arch: Zen
family: 17 (23) model-id: 71 (113) stepping: N/A microcode: 8701021
L2 cache: 6144 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 182074
Speed: 2194 MHz min/max: 2200/3800 MHz boost: enabled Core speeds (MHz): 1: 2197
2: 2195 3: 2196 4: 2195 5: 2194 6: 2196 7: 2190 8: 2191 9: 2196 10: 2195 11: 2189
12: 2195 13: 2195 14: 2187 15: 2193 16: 2189 17: 2196 18: 2193 19: 2196 20: 2196
21: 2196 22: 2195 23: 2192 24: 2196
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Micro-Star MSI driver: nouveau
v: kernel bus ID: 09:00.0 chip ID: 10de:1c82
Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa
resolution: 1920x1200~60Hz
OpenGL: renderer: NV137 v: 4.3 Mesa 20.3.4 direct render: Yes
Audio: Device-1: NVIDIA GP107GL High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus ID: 09:00.1 chip ID: 10de:0fb9
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel
v: kernel bus ID: 0b:00.4 chip ID: 1022:1487
Sound Server: ALSA v: k5.8.0-3-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte
driver: r8169 v: kernel port: f000 bus ID: 08:00.0 chip ID: 10ec:8168
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 2.27 TiB used: 979.95 GiB (42.1%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO Plus 1TB size: 931.51 GiB
block size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 serial: <filter>
rev: 2B2QEXM7 scheme: GPT
ID-2: /dev/sda type: USB vendor: Samsung model: SSD 860 EVO 500G size: 465.76 GiB
block size: physical: 4096 B logical: 512 B serial: <filter> rev: 0223 scheme: MBR
ID-3: /dev/sdb type: USB vendor: Samsung model: SSD 850 EVO 1TB size: 931.51 GiB
block size: physical: 512 B logical: 512 B serial: <filter> scheme: MBR
Partition: ID-1: / raw size: 928.97 GiB size: 913.39 GiB (98.32%) used: 316.59 GiB (34.7%)
fs: ext4 dev: /dev/nvme0n1p2
ID-2: swap-1 size: 2.44 GiB used: 1.5 MiB (0.1%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/nvme0n1p3
Sensors: System Temperatures: cpu: 49.1 C mobo: N/A gpu: nouveau temp: 16 C
Fan Speeds (RPM): N/A
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian buster main contrib non-free
2: deb http://deb.debian.org/debian-security buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://nl.mxrepo.com/mx/repo/ buster main non-free
2: deb http://nl.mxrepo.com/mx/repo/ buster ahs
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 391 Uptime: 1h 39m Memory: 31.35 GiB used: 2.10 GiB (6.7%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in
running in: quick-system-in inxi: 3.0.36
Re: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 1:48 am
There is no WINE in AHS and there shouldn’t be anything in the AHS repo that “should” allow WINE to install if it won’t install in the Stable MX.
I would know I package almost everything in AHS and @mmikeinsantarosa packages WINE for both the Stable and Test repos.
Have you tried MX Package Installer > Popular Apps or are you just using Synaptic/apt-get?
You keep giving us console outputs but not everything.
Edit: looks like someone using AHS has a problem too, so it’s not something AHS repo is gonna fix
I would know I package almost everything in AHS and @mmikeinsantarosa packages WINE for both the Stable and Test repos.
Have you tried MX Package Installer > Popular Apps or are you just using Synaptic/apt-get?
You keep giving us console outputs but not everything.
Edit: looks like someone using AHS has a problem too, so it’s not something AHS repo is gonna fix
Re: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 1:57 am
Synaptic Package Manager -> Edit menu -> Fix broken packages. Then close Synaptic and try installing wine from MXPI again. If that still fails, open a terminal and run
then try again, in case your attempted installation from winehq's repo or the broken mirror left some junk behind. (I assume you've updated your apt package sources then installed all the updates you've been missing after changing mirrors?)
Code: Select all
sudo apt-get purge wine*Re: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 3:02 am
I use MXPI "popular applications" for Wine
About that I have now also uninstalled it and then reinstalled again, now without error message
About that I have now also uninstalled it and then reinstalled again, now without error message
Re: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 4:36 am
Can someone having problems do a simulation with aptitude and see what it has to say?
The error messages given by 'apt' in case of dependency problems are mostly useless
Code: Select all
aptitude -s install winehq-stagingRe: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 5:47 am
Okay, when I try to install wine from MXPI Popular Apps in a VirtualBox VM installation of MX-19.3, when I click on Show Details I get an empty details field. This is with both the LA mirror and the "mothership" in SLC. When I do the same an an MX-19.3 AHS VB installation I see a list of packages to be installed. So codydragonrude was right and I was wrong: there's something different about and broken in the non-AHS version. For one thing, /usr/share/mx-packageinstaller-packagelist/Wine.pm is missing in the non-AHS version.
(Crow doesn't taste too bad if you put enough ketchup on it.)
(Crow doesn't taste too bad if you put enough ketchup on it.)
Re: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 7:05 am
@JayM I don't have the same problem, so can you do the command from post 11 and see what it does?
Re: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 7:14 am
Code: Select all
jay@mx:~
$ aptitude -s install winehq-staging
The following NEW packages will be installed:
libaom0:i386{a} libasound2:i386{a} libasound2-plugins:i386{a} libasyncns0:i386{a}
libatomic1:i386{a} libavcodec58:i386{ab} libavresample4:i386{ab} libavutil56:i386{ab}
libblkid1:i386{a} libbsd0:i386{a} libcairo2:i386{a} libcap2:i386{a} libcodec2-0.8.1:i386{a}
libcroco3:i386{a} libcrystalhd3:i386{a} libdatrie1:i386{a} libdb5.3:i386{a}
libdbus-1-3:i386{a} libdrm2:i386{a} libexif12:i386{a} libexpat1:i386{a} libffi6:i386{a}
libflac8:i386{a} libfontconfig1:i386{a} libfreetype6:i386{a} libfribidi0:i386{a}
libgcrypt20:i386{a} libgd3:i386{a} libgdk-pixbuf2.0-0:i386{a} libglib2.0-0:i386{a}
libgmp10:i386{a} libgnutls30:i386{a} libgomp1:i386{a} libgpg-error0:i386{a}
libgphoto2-6:i386{a} libgphoto2-port12:i386{a} libgraphite2-3:i386{a} libgsm1:i386{a}
libgstreamer-plugins-base1.0-0:i386{a} libgstreamer1.0-0:i386{a} libharfbuzz0b:i386{a}
libhogweed4:i386{a} libice6:i386{a} libicu63:i386{a} libidn2-0:i386{a}
libjack-jackd2-0:i386{a} libjbig0:i386{a} libjpeg62-turbo:i386{a} liblcms2-2:i386{a}
libldap-2.4-2:i386{a} libltdl7:i386{a} liblz4-1:i386{a} liblzma5:i386{a} libmount1:i386{a}
libmp3lame0:i386{a} libmpg123-0:i386{a} libncurses5{a} libncurses5:i386{a} libnettle6:i386{a}
libnuma1:i386{a} libogg0:i386{a} libopenal1:i386{a} libopenjp2-7:i386{a} libopus0:i386{a}
liborc-0.4-0:i386{a} libp11-kit0:i386{a} libpango-1.0-0:i386{a} libpangocairo-1.0-0:i386{a}
libpangoft2-1.0-0:i386{a} libpcre3:i386{a} libpixman-1-0:i386{a} libpng16-16:i386{a}
libpulse0:i386{a} librsvg2-2:i386{a} libsamplerate0:i386{a} libsasl2-2:i386{a}
libsasl2-modules-db:i386{a} libselinux1:i386{a} libshine3:i386{a} libsm6:i386{a}
libsnappy1v5:i386{a} libsndfile1:i386{a} libsndio7.0:i386{a} libsoxr0:i386{a}
libspeex1:i386{a} libstdc++6:i386{a} libswresample3:i386{ab} libsystemd0:i386{a}
libtasn1-6:i386{a} libthai0:i386{a} libtheora0:i386{a} libtiff5:i386{a} libtinfo5{a}
libtinfo5:i386{a} libtwolame0:i386{a} libudev1:i386{a} libunistring2:i386{a}
libusb-1.0-0:i386{a} libuuid1:i386{a} libva-drm2:i386{ab} libva-x11-2:i386{ab}
libva2:i386{ab} libvdpau1:i386{a} libvkd3d1{a} libvkd3d1:i386{a} libvorbis0a:i386{a}
libvorbisenc2:i386{a} libvpx5:i386{a} libvulkan1:i386{a} libwavpack1:i386{a} libwebp6:i386{a}
libwebpmux3:i386{a} libwrap0:i386{a} libx11-6:i386{a} libx11-xcb1:i386{a} libx264-155:i386{a}
libx265-165:i386{a} libxau6:i386{a} libxcb-render0:i386{a} libxcb-shm0:i386{a}
libxcb1:i386{a} libxdmcp6:i386{a} libxext6:i386{a} libxfixes3:i386{a} libxi6:i386{a}
libxml2:i386{a} libxpm4:i386{a} libxrender1:i386{a} libxtst6:i386{a} libxvidcore4:i386{a}
libzstd1:i386{a} libzvbi0:i386{a} ocl-icd-libopencl1:i386{a} wine-gecko2.47.1{a}
wine-gecko2.47.1:i386{a} wine-mono5.1.0{a} wine-staging{a} wine-staging-amd64{a}
wine-staging-i386:i386{a} winehq-staging zlib1g:i386{a}
The following packages will be REMOVED:
libcrystalhd3{u} liblua5.3-0{u} libxcb-cursor0{u} libxcb-xtest0{u} libxdg-basedir1{u}
linux-headers-4.19.0-13-amd64{u} linux-headers-4.19.0-13-common{u} lua-lgi{u}
The following packages are RECOMMENDED but will NOT be installed:
gstreamer1.0-plugins-base:i386 i965-va-driver:i386 i965-va-driver-shaders:i386
intel-media-va-driver:i386 intel-media-va-driver-non-free:i386 libcapi20-3 libcapi20-3:i386
libcups2:i386 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-bin:i386 libgnutlsxx28 libgnutlsxx28:i386
libgpg-error-l10n libgphoto2-l10n libgpm2:i386 libgtk-3-0:i386 libodbc1 libodbc1:i386
libosmesa6 libosmesa6:i386 libpcap0.8:i386 librsvg2-common:i386 libsane:i386
libsasl2-modules:i386 libv4l-0:i386 libvdpau-va-gl1:i386 libxcomposite1:i386 libxcursor1:i386
libxinerama1:i386 libxrandr2:i386 libxslt1.1:i386 libxt6:i386 libxxf86vm1:i386
mesa-va-drivers:i386 mesa-vdpau-drivers:i386 nvidia-legacy-340xx-vdpau-driver:i386
nvidia-legacy-390xx-vdpau-driver:i386 nvidia-tesla-vdpau-driver:i386 nvidia-vdpau-driver:i386
uuid-runtime uuid-runtime:i386 va-driver-all:i386 vdpau-driver-all:i386 vdpau-va-driver:i386
0 packages upgraded, 141 newly installed, 8 to remove and 0 not upgraded.
Need to get 288 MB of archives. After unpacking 777 MB will be used.
The following packages have unmet dependencies:
libswresample3 : Breaks: libswresample3:i386 (!= 7:4.3.1-2~mx19+2) but 7:4.1.6-1~mx19+2 is to be installed
libswresample3:i386 : Breaks: libswresample3 (!= 7:4.1.6-1~mx19+2) but 7:4.3.1-2~mx19+2 is installed
libva2 : Breaks: libva2:i386 (!= 2.6.1-1mx19+1) but 2.4.0-1 is to be installed
libva2:i386 : Breaks: libva2 (!= 2.4.0-1) but 2.6.1-1mx19+1 is installed
libavcodec58 : Breaks: libavcodec58:i386 (!= 7:4.3.1-2~mx19+2) but 7:4.1.6-1~mx19+2 is to be installed
libavcodec58:i386 : Breaks: libavcodec58 (!= 7:4.1.6-1~mx19+2) but 7:4.3.1-2~mx19+2 is installed
libavutil56 : Breaks: libavutil56:i386 (!= 7:4.3.1-2~mx19+2) but 7:4.1.6-1~mx19+2 is to be installed
libavutil56:i386 : Breaks: libavutil56 (!= 7:4.1.6-1~mx19+2) but 7:4.3.1-2~mx19+2 is installed
libva-x11-2 : Breaks: libva-x11-2:i386 (!= 2.6.1-1mx19+1) but 2.4.0-1 is to be installed
libva-x11-2:i386 : Breaks: libva-x11-2 (!= 2.4.0-1) but 2.6.1-1mx19+1 is installed
libva-drm2 : Breaks: libva-drm2:i386 (!= 2.6.1-1mx19+1) but 2.4.0-1 is to be installed
libva-drm2:i386 : Breaks: libva-drm2 (!= 2.4.0-1) but 2.6.1-1mx19+1 is installed
libavresample4 : Breaks: libavresample4:i386 (!= 7:4.3.1-2~mx19+2) but 7:4.1.6-1~mx19+2 is to be installed
libavresample4:i386 : Breaks: libavresample4 (!= 7:4.1.6-1~mx19+2) but 7:4.3.1-2~mx19+2 is installed
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) libasound2-plugins:i386 [Not Installed]
2) libavcodec58:i386 [Not Installed]
3) libavresample4:i386 [Not Installed]
4) libavutil56:i386 [Not Installed]
5) libswresample3:i386 [Not Installed]
6) libva-drm2:i386 [Not Installed]
7) libva-x11-2:i386 [Not Installed]
8) libva2:i386 [Not Installed]
9) wine-staging [Not Installed]
10) wine-staging-i386:i386 [Not Installed]
11) winehq-staging [Not Installed]
Accept this solution? [Y/n/q/?]
Re: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 7:22 am
One possibility is that you installed libva packages from the test repo at some time and now the 32-bit packages would need to come from there too to stay compatibleJayM wrote: Thu Apr 01, 2021 7:14 am libva2 : Breaks: libva2:i386 (!= 2.6.1-1mx19+1) but 2.4.0-1 is to be installed
Or else this 2.6.1-1mx19+1 version of libva2 used to be in the MX stable repo, but has now disappeared
Re: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 8:01 am
No, this is a recent stock installation of MX in VB. All I've done AFAIR is the updates. I can blow the virtual machine away and reinstall from scratch though, just to make sure.
Re: Wine installer broken in non ahs version
Posted: Thu Apr 01, 2021 11:36 am
I'm going to mark this as solved because i switched to another distro
I just do not have the time to sit here and troubleshoot distro problems
I just do not have the time to sit here and troubleshoot distro problems
Re: Wine installer broken in non ahs version (Solved)
Posted: Thu Apr 01, 2021 8:28 pm
I remembered that I have another VM installation of MX-19.3 non-AHS, this one installed as UEFI, which I've never done anything with but updated and wine installs fine on it from MXPI, Pop Apps, Misc. The first VB installation is the one that I use to try to replicate peoples' problems and stuff so it's probably hosed and needs a reinstall. I'll wait and do MX-19.4 though.
So, to recap regarding the OP's original complaint:
1. There is no "wine installer." Wine is installed from MX Package Installer, Synaptic Package Manager, or apt from the command-line just like any other application.
2. Wine installs from MX Package Installer, Popular Applications, Misc. on a fresh installation of MX-19.3 with no problems. There is nothing the matter with the package installer or the distro.
It's possible that OP's repository mirror was in the middle of being updated at the time he tried to install wine, so if he'd just been a little more patient and waited a while it may have resolved itself. Or his "you have held broken packages" issue may have been caused by using a broken 3rd-party MX mirror all along which may have updated his system with broken packages. OP was too impatient and uncooperative to work with forum volunteers and his peers to try to fix it.
So, to recap regarding the OP's original complaint:
1. There is no "wine installer." Wine is installed from MX Package Installer, Synaptic Package Manager, or apt from the command-line just like any other application.
2. Wine installs from MX Package Installer, Popular Applications, Misc. on a fresh installation of MX-19.3 with no problems. There is nothing the matter with the package installer or the distro.
It's possible that OP's repository mirror was in the middle of being updated at the time he tried to install wine, so if he'd just been a little more patient and waited a while it may have resolved itself. Or his "you have held broken packages" issue may have been caused by using a broken 3rd-party MX mirror all along which may have updated his system with broken packages. OP was too impatient and uncooperative to work with forum volunteers and his peers to try to fix it.
Re: Wine installer broken in non ahs version (Solved)
Posted: Thu Apr 01, 2021 8:42 pm
@codydragonrude
Edit: maybe you can use the real way to mark a thread solved, then again you don't ever get on the forums much, so you probably missed that function exists now.
Nope, not even close, was in the works long before your post, enjoy Manjaro though its a good Distro.Codythdragonrude @codythedragonrude@linuxrocks.online
lol mxlinux dropping a 19.4 iso probably to fix that issue that's totally my problem LOL
Iol... you know what... nvm... it ain't even worth it for someone like thisCodythdragonrude @codythedragonrude@linuxrocks.online
the mx linux forum was pretty useless
they kept suggesting things that did not work and saying it's not a them but rather a me problem even though they are the ones who decided to have a custom repo wine installer which also breaks the repo by just doing it from the winehq site
mxlinux is a MessX https://linuxrocks.online/@codythedrag
Edit: maybe you can use the real way to mark a thread solved, then again you don't ever get on the forums much, so you probably missed that function exists now.
Re: Wine installer broken in non ahs version (Solved)
Posted: Fri Apr 02, 2021 5:23 am
I do think that at some point some packages (ffmpeg, libva) made it to the MX stable repo which shouldn't have done so. Maybe @JayM can check on his VB install where he had the problem when libva2 got updated:
But yes, on a new install (any new install, no 19.4 needed for this), there are no problems.
Code: Select all
apt-history libva2Re: Wine installer broken in non ahs version (Solved)
Posted: Fri Apr 02, 2021 5:50 am
I'll have to do that tomorrow. I had to reset my BIOS earlier and forgot to re-enable virtualization so I can't start 64-bit VMs and I can't reboot right now due to a process that's currently running.
Re: Wine installer broken in non ahs version (Solved)
Posted: Fri Apr 02, 2021 6:08 am
an attempted solution for problems as in post 14:
This should downgrade the ffmpeg and libva packages to the current stable version. Command can take 10-15 seconds to show results.
Now it is possible that apt will propose to remove a lot of packages that may depend on the newer versions of ffmpeg and libva. In that case I propose to use the versions from the mx test repo (instead of trying to downgrade), but since I suppose that people don't want the test version of wine (otherwise you just install wine from the test repo in MXPI), we'll have to write a preferences file:
You'll also have to enable the test repo for this and now you should be able to install Wine with MX Package Installer, or with:
Code: Select all
sudo apt install $(echo $(aptitude search '?source-package(^ffmpeg$) ?installed' -F %p | sed -n s/$/=$(apt-cache policy ffmpeg | grep -m1 ' 500' | awk '{print $(NF-1)}')/gp && aptitude search '?source-package(^libva$) ?installed' -F %p | sed -n s/$/=$(apt-cache policy libva2 | grep -m1 '500' | awk '{print $(NF-1)}')/gp))Now it is possible that apt will propose to remove a lot of packages that may depend on the newer versions of ffmpeg and libva. In that case I propose to use the versions from the mx test repo (instead of trying to downgrade), but since I suppose that people don't want the test version of wine (otherwise you just install wine from the test repo in MXPI), we'll have to write a preferences file:
Code: Select all
echo -e "Package: $(echo $(aptitude search '?source-package(^libva$)' '?source-package(^ffmpeg$)' -F %p))\nPin: release a=mx,c=test\nPin-Priority:500" | sudo tee /etc/apt/preferences.d/pin_ffmpeg_libvaCode: Select all
sudo apt update && sudo apt install winehq-stagingRe: Wine installer broken in non ahs version (Solved)
Posted: Fri Apr 02, 2021 8:22 am
@tony37 I think you guys are on to something. There is/was a known nuance, which would manifest under certain circumstances where if the ffmpeg libraries were installed (or pulled by another package) from the MX Test repo, and then a user manually tried to install ffmpeg from the AHS repo, this it would create broken packages that would need flipped.
When Stevo and I talked about it before the last AHS release cycle, we decided to stop chasing after it in part because it was hard to reproduce at the time and because the versions of the related -dev packages might have been needed by users. So we decide to stop more changes rather than cause more breakage.
Not sure if it’s related or make sense, it’s early lol.
If you guys determine the issue, where ever it is, we’ll fix it. Appreciate the extra effort by you two.
When Stevo and I talked about it before the last AHS release cycle, we decided to stop chasing after it in part because it was hard to reproduce at the time and because the versions of the related -dev packages might have been needed by users. So we decide to stop more changes rather than cause more breakage.
Not sure if it’s related or make sense, it’s early lol.
If you guys determine the issue, where ever it is, we’ll fix it. Appreciate the extra effort by you two.
Re: Wine installer broken in non ahs version (Solved)
Posted: Fri Apr 02, 2021 9:13 am
I think it's just a general problem that once you install a package from a certain repo, other packages from the same source-package should come from the same repo as well. But for newbies this is almost impossible to figure out, partly because the error messages from apt are not helpful.
Other recent examples: viewtopic.php?f=136&t=63769&p=628539#p628539 and viewtopic.php?f=127&t=63739&p=628211#p628211
In an ideal world, apt would at least propose to install from another repo if that would solve dependency problems.
Other recent examples: viewtopic.php?f=136&t=63769&p=628539#p628539 and viewtopic.php?f=127&t=63739&p=628211#p628211
In an ideal world, apt would at least propose to install from another repo if that would solve dependency problems.
Re: Wine installer broken in non ahs version (Solved)
Posted: Fri Apr 02, 2021 4:38 pm
The problem is not so difficult to reproduce: you start with a non-ahs iso (19.3 or 19.4 doesn't matter), then you go to MXPI > Test repo and upgrade (for example) libavcodec58. And then you try to install the default wine version.
Or more realistic example: install Kodi 19 from the test repo, and try installing Wine after that. Or: first install Blender from test repo... (or Streamlink, you get the point, anything that needs updated ffmpeg libraries, or that simply wants to install the ffmpeg package)
Or more realistic example: install Kodi 19 from the test repo, and try installing Wine after that. Or: first install Blender from test repo... (or Streamlink, you get the point, anything that needs updated ffmpeg libraries, or that simply wants to install the ffmpeg package)
Re: Wine installer broken in non ahs version (Solved)
Posted: Fri Apr 02, 2021 6:40 pm
I get what you are saying, but several weeks ago I was able to reproduce the same issue on AHS in our pre-release testing as well.tony37 wrote: Fri Apr 02, 2021 4:38 pm The problem is not so difficult to reproduce: you start with a non-ahs iso (19.3 or 19.4 doesn't matter), then you go to MXPI > Test repo and upgrade (for example) libavcodec58. And then you try to install the default wine version.
Or more realistic example: install Kodi 19 from the test repo, and try installing Wine after that. Or: first install Blender from test repo... (or Streamlink, you get the point, anything that needs updated ffmpeg libraries, or that simply wants to install the ffmpeg package)
What you said and what I said are the same, but now some people are saying its just the Stable MX, but not also AHS.
ffmpeg and friends are/were a lower version in AHS than in MX Test, so it makes sense both Stable and AHS would have the same issue.
ffmpeg was a bit higher in AHS than Stable for a bit off and on, which is why I believe the issue would come and go infrequently.
Re: Wine installer broken in non ahs version (Solved)
Posted: Fri Apr 02, 2021 7:18 pm
If ahs has a lower version of ffmpeg than the test repo, then it can happen there as well. The main problem is just that once the ffmpeg packages come from test, then the 32-bit versions (needed for wine) need to come from there as well. So how to solve this? Maybe doing a preinstall check which version is installed, and installing some packages from the test repo if needed? Could become complicated
Re: Wine installer broken in non ahs version (Solved)
Posted: Fri Apr 02, 2021 7:53 pm
Code: Select all
$ apt-history libva2
2021-01-29 14:11:43 upgrade libva2:amd64 2.4.0-1 2.6.1-1mx19+1
Re: Wine installer broken in non ahs version (Solved)
Posted: Fri Apr 02, 2021 7:59 pm
Ok, and what else did you install/upgrade that time?JayM wrote: Fri Apr 02, 2021 7:53 pmCode: Select all
$ apt-history libva2 2021-01-29 14:11:43 upgrade libva2:amd64 2.4.0-1 2.6.1-1mx19+1
Code: Select all
apt-history 2021-01-29Re: Wine installer broken in non ahs version (Solved)
Posted: Fri Apr 02, 2021 8:10 pm
See attachment.tony37 wrote: Fri Apr 02, 2021 7:59 pmOk, and what else did you install/upgrade that time?JayM wrote: Fri Apr 02, 2021 7:53 pmCode: Select all
$ apt-history libva2 2021-01-29 14:11:43 upgrade libva2:amd64 2.4.0-1 2.6.1-1mx19+1Code: Select all
apt-history 2021-01-29
Re: Wine installer broken in non ahs version (Solved)
Posted: Fri Apr 02, 2021 8:28 pm
So it must have been because you installed minitube from the test repo (version 3.6.5-0.1~mx19+1). That pulled in libavdevice58, so other ffmpeg packages got upgraded as well (and because of that, also the libva packages)
Re: Wine installer broken in non ahs version (Solved)
Posted: Fri Apr 02, 2021 8:44 pm
I don't remember if it was from the test repo or not, but if you're wondering why I installed it in a VM, this is why. I use the VM to test, check and try things without risking messing up the host system. That's why I said it's probably high time I reinstalled: there's a high level of cruft on it.
Re: Wine installer broken in non ahs version (Solved)
Posted: Sat Apr 03, 2021 12:17 pm
I couldn't help myself and tried to write a script for this. It may still be a bit amateurish, but it worked when I tested it. (update: I improved a few things and think it should be fine)tony37 wrote: Fri Apr 02, 2021 7:18 pm The main problem is just that once the ffmpeg packages come from test, then the 32-bit versions (needed for wine) need to come from there as well. So how to solve this? Maybe doing a preinstall check which version is installed, and installing some packages from the test repo if needed? Could become complicated
So I wrote a file called /usr/share/mx-packageinstaller-pkglist/wine_script.sh with following content:
Code: Select all
#!/bin/bash
# this list can be generated with: echo $(aptitude search '?source-package(^ffmpeg$)' -F %p)
ffmpeg_list="ffmpeg ffmpeg:i386 ffmpeg-doc libavcodec-dev libavcodec-dev:i386 libavcodec-extra libavcodec-extra:i386 libavcodec-extra58 libavcodec-extra58:i386 libavcodec58 libavcodec58:i386 libavdevice-dev libavdevice-dev:i386 libavdevice58 libavdevice58:i386 libavfilter-dev libavfilter-dev:i386 libavfilter-extra libavfilter-extra:i386 libavfilter-extra7 libavfilter-extra7:i386 libavfilter7 libavfilter7:i386 libavformat-dev libavformat-dev:i386 libavformat58 libavformat58:i386 libavresample-dev libavresample-dev:i386 libavresample4 libavresample4:i386 libavutil-dev libavutil-dev:i386 libavutil56 libavutil56:i386 libpostproc-dev libpostproc-dev:i386 libpostproc55 libpostproc55:i386 libswresample-dev libswresample-dev:i386 libswresample3 libswresample3:i386 libswscale-dev libswscale-dev:i386 libswscale5 libswscale5:i386"
# this list can be generated with: echo $(aptitude search '?source-package(^libva$)' -F %p)
libva_list="libva-dev libva-dev:i386 libva-drm2 libva-drm2:i386 libva-glx2 libva-glx2:i386 libva-wayland2 libva-wayland2:i386 libva-x11-2 libva-x11-2:i386 libva2 libva2:i386 va-driver-all va-driver-all:i386"
if [[ -n $(grep 'Package: libavutil56' /var/lib/dpkg/status) ]]; then
if [[ -n $(apt-cache policy libavutil56 | grep -m1 '/var/lib/dpkg/status\| 500 ' | grep status) ]]; then
echo -e "Package: $ffmpeg_list\nPin: release a=mx,c=test\nPin-Priority:500\n" >> /etc/apt/preferences.d/tmp_wine_preferences
fi
fi
if [[ -n $(grep 'Package: libva2' /var/lib/dpkg/status) ]]; then
if [[ -n $(apt-cache policy libva2 | grep -m1 '/var/lib/dpkg/status\| 500 ' | grep status) ]]; then
echo -e "Package: $libva_list\nPin: release a=mx,c=test\nPin-Priority:500\n" >> /etc/apt/preferences.d/tmp_wine_preferences
fi
fi
if [ -e /etc/apt/preferences.d/tmp_wine_preferences ]
then echo "deb http://mxrepo.com/mx/testrepo/ buster test">/etc/apt/sources.list.d/mxpitemp.list && apt-get update
fi
Code: Select all
rm -f /etc/apt/sources.list.d/mxpitemp.list /etc/apt/preferences.d/tmp_wine_preferencesedit: I decided it was better to have all packages from the ffmpeg/libva source package in the preferences list, because some could be in need of an update if the current test version is more recent than the originally installed test version.
Re: Wine installer broken in non ahs version (Solved)
Posted: Sat Apr 03, 2021 12:44 pm
I think the easier long term solution would be for the i386 packages to be installed with the amd64 packages when installing from the MX Test Repo.
Maybe I’m wrong, but any other option coming to mind means maintaining/updating other work arounds like your script.
Maybe I’m wrong, but any other option coming to mind means maintaining/updating other work arounds like your script.
Re: Wine installer broken in non ahs version (Solved)
Posted: Sat Apr 03, 2021 1:42 pm
One problem with installing the 32-bit packages automatically is that they pull in a lot of stuff: libavcodec58:i386 pulls in 77 other packages for me.
What you would have to maintain using my script would be: checking if more packages are needed when a newer Wine version comes out. But I did a check with the current 6.4 version in the test repo and I see no extra dependencies. (edit: although the way I have the script now, I think you wouldn't even need to check this, just every major release you'd have to check if 'buster' needs to be 'bullseye', or if some packages have changed names)
It's true that this would only solve the problem for Wine, not potential other conflicts. But then you'd need to have a general preferences file with all ffmpeg + libva packages from mx test pinned to 500, and the test repo would have to stay enabled then.
I think most non-Wine problems can be fairly easily solved, like "install ffmpeg from the test repo tab in MXPI" or "install this/that dev package from the test repo". But when someone doesn't want the test version of Wine, then it gets complicated.
What you would have to maintain using my script would be: checking if more packages are needed when a newer Wine version comes out. But I did a check with the current 6.4 version in the test repo and I see no extra dependencies. (edit: although the way I have the script now, I think you wouldn't even need to check this, just every major release you'd have to check if 'buster' needs to be 'bullseye', or if some packages have changed names)
It's true that this would only solve the problem for Wine, not potential other conflicts. But then you'd need to have a general preferences file with all ffmpeg + libva packages from mx test pinned to 500, and the test repo would have to stay enabled then.
I think most non-Wine problems can be fairly easily solved, like "install ffmpeg from the test repo tab in MXPI" or "install this/that dev package from the test repo". But when someone doesn't want the test version of Wine, then it gets complicated.
Re: Wine installer broken in non ahs version (Solved)
Posted: Sat Apr 03, 2021 2:18 pm
I’d have to look later, but if those i386 packages are going to get pulled in anyway sooner or later, than I don’t see an issue with it unless we are talking a ton of extra space being wasted. They may get used/be needed later anyway.
If someone is using the MX Test Repo to install anything, they should be expecting to deal with any consequences anyway. And they are probably going to pull in a done of different random amd64 and i386 packages either way.
We created this problem because we provide a tons of options for newer software for users, for sure don’t want to take that away, but I also don’t want to (or anyone else to have to) update a script of do extra work because we update something.
Mike does enough just packaging WINE and putting it through it’s paces before users get it. Stevo and I do enough with libva and ffmpeg every so often.
If anything I’d like to make things easier and faster for everyone, including users. The solution should be smarter, not harder. And by harder I mean no extra work or hassle for anyone.
This issue we have right now tells me we either need to slow down, test things more before putting them in the MX Test Repo, and probably pay attention to some details better.
We pride ourselves in the fact that the MX Test Repo is pretty much 99.99% stable and issue free. We try really hard to keep it that way, so when things like this pop up it’s depressing (to me at least) lol.
I’m going to defer to @Stevo, I’m game for whatever he decides.
If someone is using the MX Test Repo to install anything, they should be expecting to deal with any consequences anyway. And they are probably going to pull in a done of different random amd64 and i386 packages either way.
We created this problem because we provide a tons of options for newer software for users, for sure don’t want to take that away, but I also don’t want to (or anyone else to have to) update a script of do extra work because we update something.
Mike does enough just packaging WINE and putting it through it’s paces before users get it. Stevo and I do enough with libva and ffmpeg every so often.
If anything I’d like to make things easier and faster for everyone, including users. The solution should be smarter, not harder. And by harder I mean no extra work or hassle for anyone.
This issue we have right now tells me we either need to slow down, test things more before putting them in the MX Test Repo, and probably pay attention to some details better.
We pride ourselves in the fact that the MX Test Repo is pretty much 99.99% stable and issue free. We try really hard to keep it that way, so when things like this pop up it’s depressing (to me at least) lol.
I’m going to defer to @Stevo, I’m game for whatever he decides.
Re: Wine installer broken in non ahs version (Solved)
Posted: Sat Apr 03, 2021 3:30 pm
What would be wonderful of course is if you could simply eliminate these libraries from the test repo. And say to people: if you want newer ffmpeg packages, use ahs.
But I think Kodi 19 really needs the newer versions, haven't found other packages though.
But I think Kodi 19 really needs the newer versions, haven't found other packages though.
Re: Wine installer broken in non ahs version (Solved)
Posted: Sat Apr 03, 2021 4:24 pm
There are other packages, I found that out while testing the pre-release AHS stuff cause like I said it’s version is lower as well.
I think there is enough applications in the MX Test Repo that need the newer versions that moving it all into AHS only would negate what AHS is really just supposed to be for... newer hardware.
AHS isn’t meant to be a rolling version of MX, it’s not the goal, and we decided a long time ago to not make it that.
I think there is enough applications in the MX Test Repo that need the newer versions that moving it all into AHS only would negate what AHS is really just supposed to be for... newer hardware.
AHS isn’t meant to be a rolling version of MX, it’s not the goal, and we decided a long time ago to not make it that.
Re: Wine installer broken in non ahs version (Solved)
Posted: Sun Apr 04, 2021 5:20 am
just a last thought: If you would automatically install some extra packages if ffmpeg packages get installed from the test repo, then I'd propose to install just 'ffmpeg' and 'libavdevice58' (both 64-bit). That would already solve a lot of possible problems, with just two packages. Because from what I can see, the only use case for those 32-bit packages (libavcodec58:i386 etc.) is Wine, even Steam doesn't need them. So doing something Wine-specific makes sense to me. Only problem that would remain is dev packages, but starting to install those for everyone feels like a no-go zone.