Fedora Account System
Red Hat Associate
Red Hat Customer
Starting from the command line with "mediawriter" as documented at: https://docs.fedoraproject.org/en-US/fedora/latest/preparing-boot-media/#_fedora_media_writer I get the following warning messages: W@267ms: qrc:/qml/DeviceWarningDialog.qml:54: TypeError: Cannot read property 'size' of null (qrc:/qml/DeviceWarningDialog.qml:54) W@415ms: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID") The application does start up and appears to work normally. Applications should not emit text unless they are malfunctioning; it's unclear to me whether this is a malfunction or a nuisance message. This happens if I close the application and restart it the same way. The first time I close, after writing an ISO, I get an additional warning: W@8762848ms: qrc:/qml/main.qml:168:5: QML DeviceWarningDialog: Binding loop detected for property "x": qrc:/qml/DeviceWarningDialog.qml:34:5 (qrc:/qml/main.qml:168) Closing a second time after not writing an ISO does not emit a warning at close time. mediawriter-5.2.9-1.fc43.x86_64 Reproducible: Always
FEDORA-2026-34c944bd4c (mediawriter-5.3.0-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-34c944bd4c
FEDORA-2026-34c944bd4c has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-34c944bd4c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-34c944bd4c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-34c944bd4c (mediawriter-5.3.0-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
With mediawriter-5.3.0-1.fc43.x86_64, I now get on startup from the command line: W@429ms: Failed to register with host portal QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app ID: Connection already associated with an application ID") W@604ms: Url "https://download.fedoraproject.org/pub/fedora/linux/releases/test/44_Beta/COSMIC-Atomic/x86_64/iso/Fedora-COSMIC-Atomic-ostree-x86_64-44_Beta-1.2.iso" changed to "https://download.fedoraproject.org/pub/fedora/linux/releases/test/44_Beta/Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-44_Beta-1.2.iso"
(In reply to Christopher Beland from comment #4) > With mediawriter-5.3.0-1.fc43.x86_64, I now get on startup from the command > line: > > W@429ms: Failed to register with host portal > QDBusError("org.freedesktop.portal.Error.Failed", "Could not register app > ID: Connection already associated with an application ID") > W@604ms: Url > "https://download.fedoraproject.org/pub/fedora/linux/releases/test/44_Beta/ > COSMIC-Atomic/x86_64/iso/Fedora-COSMIC-Atomic-ostree-x86_64-44_Beta-1.2.iso" > changed to > "https://download.fedoraproject.org/pub/fedora/linux/releases/test/44_Beta/ > Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-44_Beta-1.2.iso" The portal warning is from Qt itself, nothing we can do about. The other one appears to be a bug, I'm now investigating and trying to fix. Thanks for spotting this.
FEDORA-2026-e7e3dfa782 (mediawriter-5.3.1-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-e7e3dfa782
FEDORA-2026-e7e3dfa782 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-e7e3dfa782` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-e7e3dfa782 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-e7e3dfa782 (mediawriter-5.3.1-1.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.