Summary: | Problems install of Wine in KDE NEON Bionic | ||
---|---|---|---|
Product: | [KDE Neon] neon | Reporter: | ssergio-ll <sergio> |
Component: | Packages Testing Edition | Assignee: | Neon Bugs <neon-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | epost.kde, jr, maxi.cass11, neon-bugs, neousr, ole, sitter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
ssergio-ll
2018-08-15 23:30:14 UTC
Did you enable 32-bit architecture as per the instructions? (In reply to Øystein Steffensen-Alværvik from comment #1) > Did you enable 32-bit architecture as per the instructions? Yes Someone found a temporary fix her: https://forum.kde.org/viewtopic.php?f=309&t=154066 It's a problem with libblkid1 I found using aptitude easier to get wine-staging installed, I must admit it is a bit annoying that you must do this to make wine-staging work. Using wine-staging is way too common these days. Could maybe check for a snap package or something thoug. Install aptitude if it isn't already, then type: sudo aptitude install wine-staging Then skip to the solution where it want to downgrade the -one- package "libblkid1" - if you accidentally bypass it, just exit aptitude and start over. Install "wine-staging-compat" if wine-staging is your only Wine and you want it to be the default. May be fixed in dev editions now. I don't have a bionic install to test just now. On bionic neon unstable was able to install wine-devel with out a problem. Seems to be fixed. Bug 398506 seems relevant/duplicate |