Bug 2425832

Summary: Upgrade from Fedora 42 to 43 failed.
Product: [Fedora] Fedora Reporter: Al Dunstan <dunstan8986>
Component: wineAssignee: Michael Cronenworth <mike>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 43CC: besser82, mike, suraj.ghimire7
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-12-30 21:09:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Al Dunstan 2025-12-29 17:04:13 UTC
Description of problem:

    Upgrade from Fedora 42 to 43 failed.

Version-Release number of selected component (if applicable):
    Currently at Fedora 42, trying to get to 43.

How reproducible:
    Very.

Steps to Reproduce:
1. Try to upgrade from 42 to 43, using the "There's a new version available" popup.  After much waiting with little to no feedback, it "fails".  If I click on the window with the "it failed" popup (to bring the window to the foreground) the popup goes away and I have to try the upgrade again.  That kind of thing happens in more than one place, too.

Actual results:
    Didn't upgrade.

Expected results:
    Upgrade.

Additional info:
    (none)

Reported error is:

<html>Internal error:<br/><br/>Error running transaction: file /usr/lib/wine/i386-windows/urlmon.dll conflicts between attempted installs of wine-core-10.20-2.fc43.i686 and wine-core-10.20-2.fc43.x86_64
file /usr/lib/wine/i386-windows/windows.devices.bluetooth.dll conflicts between attempted installs of wine-core-10.20-2.fc43.i686 and wine-core-10.20-2.fc43.x86_64
file /usr/lib/wine/i386-windows/wined3d.dll conflicts between attempted installs of wine-core-10.20-2.fc43.i686 and wine-core-10.20-2.fc43.x86_64</html>

Comment 1 Jerry James 2025-12-29 17:08:38 UTC
This has nothing to do with the 0install package.  If you don't know what component to file a bug against, you are probably better off asking for help on https://discussion.fedoraproject.org/ instead.  Although in this case, the wine package seems to be implicated.  Please change the component from 0install to wine.

Comment 2 Michael Cronenworth 2025-12-30 21:09:39 UTC

*** This bug has been marked as a duplicate of bug 2401666 ***