Description of problem: When I try to create a Fedora 28 Image on an SD card, mediawriter is unable to do so and throws out an error message. Version-Release number of selected component (if applicable): mediawriter 4.1.1.2.fc28 How reproducible: Always Steps to Reproduce: 1. Insert the SD card 2. Run the mediawriter. 3. Click on Create Live USB. 4. Check that SD card is the target 5. Click on Write to disk. Actual results: When you click "Write to disk", an error message (Writing failed: "Message recipient disconnected from message bus without replying") appears and you cannot write to the SD card. Expected results: The image is written without problems. Additional info: 1. In the messages put to console, I have found this: ==== W@16923ms: QBackingStore::endPaint() called with active painter on backingstore paint device W@16938ms: QBackingStore::endPaint() called with active painter on backingstore paint device W@16939ms: Writing failed: "Message recipient disconnected from message bus without replying" W@16940ms: QBackingStore::endPaint() called with active painter on backingstore paint device W@16941ms: Couldn't send a notification: "org.freedesktop.DBus.Error.ServiceUnknown" - "The name org.freedesktop.Notifications was not provided by any .service files" W@16951ms: QBackingStore::endPaint() called with active painter on backingstore paint device W@16954ms: QBackingStore::endPaint() called with active painter on backingstore paint device W@16958ms: QBackingStore::endPaint() called with active painter on backingstore paint device ==== 2. Mediawriter writes with no problems to USB devices and SD cards connected via SATA bus (they report as sdb) 3. Mediawriter does not write to a card connected through an internal reader (reports as mmcblk0) 4. Both dd and arm-image-installer are able to create the image on that SD card (mmcblk0)
Please try setenforce 0.
Yes, setenforce 0 does the trick, I can confirm. Shall we send this to SELinux people then?
Yes. This happens with every Fedora release for at least two years. Each time MMC access gets broken...
Is this issue still relevant?
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.