Red Hat Bugzilla – Bug 1310542
LiveUSBCreator as Primary Downloadable
Last modified: 2018-07-17 08:43:32 EDT
This is a tracking bug for Change: LiveUSBCreator as Primary Downloadable
For more details, see: https://fedoraproject.org//wiki/Changes/LUCasPrimaryDownloadable
The new Fedora Live USB Creator that is being finished has an overhauled, more user friendly interface. Because USB sticks are the most common way to install Fedora, it should be the primary download option. It cover the whole installation media creation, it lets the user pick the right flavor of Fedora, downloads its image, and copies it to a USB drive.
On 2016-Feb-23, we have reached Fedora 24 Change Checkpoint: Completion deadline (testable).
At this point, all accepted changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be so enabled at Change Completion deadline.
Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness.
Incomplete and non testable Changes will be reported to FESCo on 2016-Feb-26 meeting. Contingency plan for System Wide Changes, if planned for Alpha (or in case of serious doubts regarding Change completion), will be activated.
The testing package is currently included in Fedora 24 and 25. I will import it in Fedora 23 and 22 updates-testing repositories, too if there is neutral or positive feedback.
liveusb-creator-3.90.0-1.fc24.noarch.rpm on Fedora 23 installs without error but fails to launch.
Mar 16 21:44:30 f23m.localdomain liveusb-creator.desktop: Error accessing /usr/sbin/liveusb-creator: No such file or directory
# find /usr -name liveusb*
sudo /usr/bin/liveusb-creator does work (on X, probably not on wayland)
Currently "use dd to write" is not selected by default in options, while "reset the mbr" is checked. Seems these should be reversed, so I'm not sure this is the right version to test?
Since testers will mainly want to test Fedora 23 or 22 + Live USB Creator to mimick how users will actually create Fedora 24 installation media, I think the package needs to be built for at least F23 and available to download in koji.
I'm currently building 3.91.0-1 pre-release of the liveusb-creator (now called Fedora Media Writer). It will be done in a few minutes.
I'll let it go to the stable repository for Fedora 24 after being in updates-testing. In Fedora 23 and 22 it will stay in updates-testing indefinitely (until there's a final release).
It solves problems you numbered 2 and 3. Problem number 1 is to be solved in a future update. For now, please run the tool using the `sudo liveusb-creator` command.
Ok, so far only F22 and F23 builds are done due to an error in Qt packaging. Newer ones are coming in a few days.
I notice that this isn't the primary downloadable for the alpha. Do we have a plan to make it so for the beta?
I use liveusb-creator for soas. Have used it for years.
I suggest that the existing GUI interface is fine but should:
1) default to (X) dd (overwrite) mode and have a ( )reset-mbr checkbox to replace of the old non-working persistence default.
2) It would be nice to add the f24 alpha and beta builds to the listing of downloadable .iso's as they are voted for go/no-go .
3) The default download directory in now / ;it should be the users /download direcory for consistency.
liveusb-creator 3.90.0-1.fc24.noarch is present in a HD install of Fedora-KDE-Live-x86_64-24_Alpha-7.iso
liveusb-creator does not start in Fedora-KDE-Live-x86_64-24_Alpha-7.iso install to HD (updated 6 april 2016)unless called from terminal.
Only f23.iso's are offered (Downloaded to Home)
Only Fedora Workstation and Fedora Server are offered in first screen
Custom OS does not work crashes LUC; error:"Qwidget: cannot create a Qwidget without QApplication"
Other spins are partially hidden behind [----] (Including Fedora KDE Plasma Desktop)
satellite you should be testing 3.91 as mentioned in comment 4. That version is not in bodhi, it's only in koji right now.
The download failed, but from the repository info I was able to proceed to the directory and install the F23 version on F23.
Note:The bar that fills up the screen moves slowly, so that we are unable to tell if the program has started.
Note: Having started the download, I switched back to the main screen. There was no indicator on this screen that the dl was under way.
There was no selection option to specify where I would like the download to be placed.
(My Download/ISO/F24 is the directory I want to use for downloads.
To which directory is the download being written? I could not find the dl'd file.
As documented, the program will perform a
dd if=media.writer.location/selected_iso, of=device_id
With/For some flashdrives, this command alone is dangerous.
I most highly recommended is to include a sync command with dd
dd if=media.writer.location/selected_iso of=device_id && sync
better yet add the bs=1M
dd if=media.writer.location/selected_iso of=device_id bs=1M && sync
Not all flashdrives have indicator lights.
Not all flashdrives have indicator lights
Not all flashdrives have indicator ligthts
How do I know when I can eject the flashdrive? Unless the sync command is present as part of the dd command line.
Without the sync command there is a chance that the "dd" buffers contents will not be fully written to the flashdrive before I pull the drive from the USB socket.
The sync command is to necessary to insure that the complete transfer to the flashdrive has completed before proceeding to the next step in the program
The program needs a message to state that the flashdrive is ready.
Some additional bugs to this tracker bug are reported here:
Leslie, please stop reporting into tracker bugs, and file a new report for each issue. This is not a chat.
On 2016-Apr-19 we reached the "Change Checkpoint: 100% Code Complete Deadline" milestone for Fedora 24 release. At this point all the Changes not at least in in "ON_QA" state should be brought to FESCo for review. Please update the state of this bug to "ON_QA" if it is already 100% completed. Please let me know in case you have any trouble with the implementation and the Change needs any help or review.
We consider the Live USB Creator feature complete for F24 release. However, yesterday's testing day discovered several bugs which were even proposed as beta blockers. Martin's currently addressing them.
He had a meeting with releng yesterday and agreed on a way to build the Windows version. But it needs an approval by FESCo. Dennis Gilmore is currently in the process of writing up a ticket.
Here's a ticket (not sure if it's "the" ticket):
Created attachment 1149471 [details]
A list of the bugs found during testing.
A list of Bugs detected and come user feedback.
Many problems shown and documented.
Use libreOffice to read the document.
Postponed to Fedora 25.
(In reply to Leslie Satenstein from comment #18)
> Created attachment 1149471 [details]
> A list of the bugs found during testing.
> A list of Bugs detected and come user feedback.
> Many problems shown and documented.
> Use libreOffice to read the document.
thanks for the report.
First I'd like to point out you were using an outdated version of the creator. The most recent one was in the updates-testing repository during the process of testing the tool. Now there is a recent-ish version in stable Fedora branches and I'm going to push a newer one to testing today or some time next week.
There is only one point valid to the recent versions: the necessity to enter the password when you start the tool and not when you're writing the image. This is a result of the architecture of the tool - in future, if it is rewritten, this could be a subject to change, however it adds unnecessary complexity to the codebase.
I'll se what I can do about that in the future.
Also, please create future bug reports as real separate bugs in the bugzilla, reported against the liveusb-creator component. Having a report as a comment below some other report makes it hard for me to track all open issues.
The security team was asked to look at the build process of this tool. I asked in https://fedorahosted.org/fedora-security-team/ticket/1 for more details about what is done to build the executables, but have not heard anything. Can someone here fill me in.
I just tried to use
in Windows 10
Program loads but resulting usb does not boot in bios-boot or win 10 EFI
(In reply to satellitgo from comment #22)
> I just tried to use
with f24 Soas x86_64 release
> in Windows 10
> Program loads but resulting usb does not boot in bios-boot
Get flashing cursor on blank screen
EFI boot works after setting the USB boot flag in gparted in fedora.
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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'
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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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
Thank you for reporting this bug and we are sorry it could not be fixed.