Created attachment 1217316 [details]
Description of problem:
Just start mediawriter and click on "restore",and an error message will pop up, as shown in the attached picture.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 1217317 [details]
Please try running FMW with SELinux in Permissive mode (by using setenforce 0). This is probably a SELinux policy issue.
If running in Permissive mode helps, please use the SELinux Troubleshoot Application to report the issue.
Permissive mode dose not help,still get the same error message.
Can you please try with this build and post the output or journal, as you like?
Created attachment 1218800 [details]
It seems that the issue is still there.
Created attachment 1218801 [details]
Ok, I think I found it this time. Thank you for the report!
Fixed upstream, coming in the next release
mediawriter-4.0.4-0.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-239cdfbfd6
mediawriter-4.0.4-0.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-239cdfbfd6
Still got the same error with the newly mediawriter.
Created attachment 1220222 [details]
Created attachment 1220223 [details]
Hmm, the same happens to me too. Seems the problem is somewhere else than in mediawriter. Discussing it with one of the storaged developers so we see what to do about it.
mediawriter-4.0.4-0.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
This was actually a duplicate of #1393379 . It's now fixed in stable repositories.
Still see this error even though I have updated libblockdev to the latest version.
Created attachment 1221050 [details]
Did you reboot your system (ar at least restart udisks2.service) after installing the update, please?
Yes，I have rebooted my system after updated the libblockdev.And there is something else,not sure if mediawriter's bug:after "Custom image" with F25-workstation-live-RC1.3-x86_64,get a similar error popup :your drive is probably damaged.
Created attachment 1221455 [details]
Created attachment 1221456 [details]
Hmm, are you sure the flash drive is not, in fact, corrupted? I've tested writing and restoring three different drives on three systems, one of them a clean f25 install and it worked okay.
I have tested the newly 4.0.7,the error messages are gone.But just to be clear,It's pretty fine:after the "restore" error message pops up ,mediawriter still can recognize it,and after saw the "custom image" error message,I have created a virt-machine using it.