Bug 1704391 - Problem installing secondary flash drive after the media writer is running
Summary: Problem installing secondary flash drive after the media writer is running
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mediawriter
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Martin Bříza
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-29 16:06 UTC by Bill Sanford
Modified: 2020-11-24 18:04 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-11-24 18:04:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Bill Sanford 2019-04-29 16:06:47 UTC
Description of problem:

After the Media Writer is launched and extracting ISO to flash drive, if you insert a secondary flash drive, the UI takes the new flash drive as the present one covering over the one actually being written to. If you "X" out (Close) the new flash drive from this new UI screen, this closes the whole process and cancels the original extraction.

Version-Release number of selected component (if applicable):
Windows 10
MediaWriter 4.1.1 - from getfedora.org.

How reproducible:
100%

Steps to Reproduce:
1. Install Media Writer from getfedora.org.
2. Download F28, F29 or F30 ISO to HDD
3. Run Media Writer and insert Flash Drive and "Write to disk" selected Fedora
4. As that is extracting to Flash drive, insert secondary flash drive.

Actual results:
Media Writer accepts new Flash Drive as current while still writing first Flash Drive.

Expected results:
Media Writer should ignore new Flash Drive while still writing first Flash Drive. It could be added to drop-down list, but not show new UI during extraction phase.

Additional info:
If you remove the secondary Flash Drive that will clear the UI of that drive and show you the first Flash Drive that is still writing or done.

Comment 1 Bill Sanford 2019-04-29 16:10:40 UTC
The blocking bug that is EOL was from https://fedoraproject.org/wiki/Test_Day:2019-04-30_Fedora_Media_Writer.

I removed it since it is EOL.

Comment 2 Ben Cotton 2019-08-13 19:26:18 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 3 Ben Cotton 2020-11-03 17:02:44 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
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 '31'.

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 31 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.

Comment 4 Ben Cotton 2020-11-24 18:04:56 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.


Note You need to log in before you can comment on or make changes to this bug.