F43 upgrade and Wine or not yet?

Ask Fedora
1

Hi,

I have read on this forum that there is a problem with F43 and an installed Wine. If I understand this correctly this is caused by a packaging problem.

So for now, I don’t dare to upgrade to F43, because I have several winapps installed.

My questions are:

  1. How do I know that this packaging problem is solved? Discover only tells me that I can upgrade to F43.
  2. Possible solution is to remove Wine, upgrade to F43 and re-install Wine. If I do that, do I have to re-install my winapps?

Thanks; still finding my way in the Fedora/KDE Plasma world.

Paul

1 Like
2

Welcome!

The upgrade problem is not yet resolved, the wine package maintainer is still working on it. You can see new updates for the wine package appearing at the top of the list in the updates service (bodhi) when they’re published.

If you apply the workaround (uninstalling wine-core.x86_64 and wine-core.i686, do the upgrade, and reinstall wine), this will not affect your installed wine prefixes. Beware that if you have 32-bit Wine prefixes, they might need to be recreated with the new Wine version.

Arch Linux made a similar transition to “new WoW64 mode” Wine recently, and they note some caveats in their blog post: https://archlinux.org/news/transition-to-the-new-wow64-wine-and-wine-staging/

2 Likes
3

I saw this new version, published a week ago.

wine-10.18-2.eln152

Can I now safely install Fedora 43 in my kde/plasma desktop?

Thx for answering (still new in the Linux world…)

4

If you are on Gnome or KDE I would wait another month.
(However this if for reasons other that the Wine conflict you originally posted about)

5

Hi Fabio,
Regarding recreation of 32-bit wine prefixes, do you know if this applies to Proton prefixes as well? I’m assuming yes, but does Steam/Proton create 32-bit or 64-bit prefixes?

6

Proton from Steam is a separate Wine distribution that manges its on Wine prefixes, so it should be unaffected by this change. I don’t know when / if Valve will switch Proton to the “new Wow64 mode”, but it hasn’t happened yet.

7

There’s been some movement on Wow64 for Proton on Github, presumably in preparation for the Steam Frame since it uses ARM64. If they ever enable it by default, it likely won’t be until after that hardware launch.

1 Like
8

The bug seems officially fixed. Has anyone tried to upgrade to F43 with Wine installed?

Fedora Update System 2026-01-05 01:21:22 UTC
FEDORA-2025-4a2922869f (wine-10.20-5.fc43 and wine-dxvk-2.7.1-5.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=2401666

9

I just tried and got this error message. Unsure how to resolve:

Problem 1: wine-dxvk-2.6.2-1.fc42.i686 from @System has inferior architecture
  - wine-dxvk-2.6.2-1.fc42.x86_64 does not belong to a distupgrade repository
  - problem with installed package
 Problem 2: wine-dxvk-d3d10-2.6.2-1.fc42.i686 from @System has inferior architecture
  - wine-dxvk-d3d10-2.6.2-1.fc42.x86_64 does not belong to a distupgrade repository
  - problem with installed package
 Problem 3: wine-dxvk-d3d8-2.6.2-1.fc42.i686 from @System has inferior architecture
  - wine-dxvk-d3d8-2.6.2-1.fc42.x86_64 does not belong to a distupgrade repository
  - problem with installed package
 Problem 4: wine-dxvk-d3d9-2.6.2-1.fc42.i686 from @System has inferior architecture
  - wine-dxvk-d3d9-2.6.2-1.fc42.x86_64 does not belong to a distupgrade repository
  - problem with installed package
 Problem 5: wine-dxvk-dxgi-2.6.2-1.fc42.i686 from @System has inferior architecture
  - wine-dxvk-dxgi-2.6.2-1.fc42.x86_64 does not belong to a distupgrade repository
  - problem with installed package
1 Like
10

Not sure why this is still a problem, but 1) uninstall wine, 2) do the upgrade, 3) install wine again should provide a workaround.

2 Likes
11

Yeah I ended up doing that, I figured if it still isn’t fixed after all that work on the wine package, it likely can’t be fixed due to a limitation of dnf itself.

2 Likes
12

Same error message today.

I have sudo dnf remove wine as explained by @decathorpe, then upgraded to F43 and finally sudo dnf install wine.

Note that in Bugzilla, two people have already reported that their F42 was upgraded smoothly to F43 without removing wine. So I think you can first try to upgrade without removing wine (the error is quickly displayed before the process starts).