I cannot install Wine on neon dev unstable after updating to 22.04 because it needs i386 of poppler. STEPS TO REPRODUCE 1. apt install winehq-stable OBSERVED RESULT The following packages have unmet dependencies: libsane1:i386 : Depends: libpoppler-glib8:i386 (>= 0.18.0) but it is not installable But I cannot install libpoppler-glib8:i386 (which seems to come from Ubuntu) because that breaks skanlite, gimp. EXPECTED RESULT I can install wine as I could on 20.04 SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon dev unstable as of 2022-12-27 ADDITIONAL INFORMATION $ LC_ALL=en_US apt-cache policy libpoppler-glib8:i386 libpoppler-glib8:i386: Installed: (none) Candidate: 22.02.0-2ubuntu0.1 Version table: 22.02.0-2ubuntu0.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 22.02.0-2 500 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
Bump! I can confirm that this is still a problem (using User Edition). It should be noted that this only affects the 32-bit version of wine, but I can't think of any software that I might want to run in wine and is actually providing 64-bit binaries (it's sad, considering that 64-bit has been around for so long). So wine:i386 is the important one. Simply providing a 32-bit package of libpoppler-glib8 in the neon sources might fix the problem. I tried to build one via apt-get (source|build-dep) and dpkg-buildpackage --target-arch=i386, but that failed. A workaround that I have seen recomended is to downgrade libpoppler to the ubuntu-jammy version, but I'm not sure if this will break anything. (versions of this package can not have different versions per arch)
Thank you for your bug report! However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since before 01/01/2025. Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's. Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report. Thanks for understanding!