[Bug 1358932] New:
How to create an USB stick with overlay persistence with graphical tools?
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1358932
Bug ID: 1358932
Summary: How to create an USB stick with overlay persistence
with graphical tools?
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: cspicer(a)redhat.com
Reporter: razvan.sandu(a)mobexpert.ro
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Hello,
Description of problem:
The online guide at
https://fedoraproject.org/wiki/How_to_create_and_use_Live_USB#Data_persis...
which is installation-related, describes how to create a Fedora bootable USB
stick using the graphical tool liveusb-creator with overlay persistence.
However, the current graphical tool available in Fedora (called "Fedora Media
Writer") offers no obvious option (button, slider, etc.) for adding an overlay
persistence space to the official .iso image.
Actual results:
The current graphical tool offers no option of adding overlay persistence to an
.iso image that is written on an USB stick.
Expected results:
The tool should offer such an option, in order to easily create USB bootable
sticks with persistence. The existing documentation should be consistent with
the actual tool.
Additional info:
IMHO, adopting and documenting a STANDARD set of tools (graphical & CLI), as
DISTRO-INDEPENDENT (cross-distro) as possible, for the (easy) creation of
bootable USB sticks (including overlay) is the way to go.
--
You are receiving this mail because:
You are the QA Contact for the bug.
5 years, 12 months
[Bug 1314499] New: Typo in Section 5.4.8: Installation Destination
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1314499
Bug ID: 1314499
Summary: Typo in Section 5.4.8: Installation Destination
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: cspicer(a)redhat.com
Reporter: hrusjos(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
There is, apparently, a word missing before "Add a disk button" in the para
starting with "The Specialized & Network Disks section below shows advanced
network storage..."
Version-Release number of selected component (if applicable):
How reproducible:
Please see line #39 of the StorageSpoke.xml
Steps to Reproduce:
1.
2.
3.
Actual results:
to search for network storage devices <guilabel>Add a disk</guilabel> button
Expected results:
to search for network storage devices press <guilabel>Add a disk</guilabel>
button and proceed with <xref
linkend="sect-installation-gui-installation-destination" />.
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 1 month
[Bug 1344465] New:
Copyright should be 2016 - can we also have translation of license ?
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1344465
Bug ID: 1344465
Summary: Copyright should be 2016 - can we also have
translation of license ?
Product: Fedora Documentation
Version: devel
Component: release-notes
Assignee: relnotes(a)fedoraproject.org
Reporter: jb.holcroft(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
when building f24 release notes, the result is "Copyright © 2014 Fedora
Project Contributors."
the result should be " © 2016"
btw, is there any reason not to translate this license ?
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 2 months
[Bug 1426560] New: vnc boot fails to find metacity
by bugzilla＠redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1426560
Bug ID: 1426560
Summary: vnc boot fails to find metacity
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: high
Assignee: cspicer(a)redhat.com
Reporter: mkolman(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: anaconda-maint-list(a)redhat.com,
extras-qa(a)fedoraproject.org, g.kaviyarasu(a)hotmail.com,
jonathan(a)jonmasters.org, lior3.1415(a)gmail.com,
mkolman(a)redhat.com, pbokoc(a)redhat.com,
vanmeeuwen+fedora(a)kolabsys.com, vponcova(a)redhat.com,
zach(a)oglesby.co
Depends On: 1425589
+++ This bug was initially created as a clone of Bug #1425589 +++
Description of problem:
Attempting to install Fedora 25 from a live image on a USB flash drive on a
Lenovo Thinkpad T60. Wayland can't handle the video card so trying the vnc
install. This fails, and running anaconda manually from a command line shows
the problem is that the anaconda scripts expect Metacity to be available.
Version-Release number of selected component (if applicable):
anaconda-25.20.8
How reproducible:
Every time
Steps to Reproduce:
1. Boot live image
2. Switch to console tty and log on
3. Run "anaconda --vnc"
Actual results:
VNC server starts (can remotely connect to it) but anaconda fails to start (so
get blank screen and can't install system)
Expected results:
Anaconda starts as expected
Additional info:
--- Additional comment from Lior on 2017-02-21 21:17 CET ---
--- Additional comment from Lior on 2017-02-23 09:55:47 CET ---
I've now read the anaconda sources and it seems the choice of metacity is
hard-coded (see the function doStartupX11Actions()). On the other hand,
metacity hasn't been a default OS component for a long time (since the
transition from GNOME 2 to GNOME 3).
Given that, in my (uneducated) opinion it seems one of the following must be
done:
1. Deprecate VNC installation.
2. Have the anaconda-core package depend on the metacity package.
3. Give anaconda a fallback when metacity is unavailable.
If I'm totally off the mark I apologize and would love an explanation.
--- Additional comment from Martin Kolman on 2017-02-23 10:42:55 CET ---
In general it is expected Anaconda will be started as a graphical application
in the live environment via a desktop icon or via the liveinst script - using
the anaconda command directly might or might not work. But I agree it should
provide a better error message/warning in such a case.
As for Metacity missing - it's not needed for the expected use case (graphical
installation from the live environment), so Metacity and its dependencies are
not part of the live image, which can then be smaller.
I understand this sucks if the graphical environment does not work in your
case, but there is a possible solution - the network installation image:
https://download.fedoraproject.org/pub/fedora/linux/releases/25/Workstati...
The netinst image still uses X & Metacity and should have working VNC
installation (as the network installation image is the expected usecase for
it).
You can even tell it to boot directly to VNC installation via boot options:
http://anaconda-installer.readthedocs.io/en/latest/boot-options.html#inst...
--- Additional comment from Lior on 2017-02-23 11:59:20 CET ---
Of course I started by trying VNC installation via boot options -- I only used
the command directly in order to investigate the problem after the inst.vnc
boot option didn't work.
Now this use case (appending inst.vnc to the boot options) is specifically
suggested by the <A
HREF="https://docs.fedoraproject.org/en-US/Fedora/25/html/Installation_Guide/se...">Fedora
25 Installation Guide</A>, so I don't think you can fairly dismiss it as
"unexpected".
I'll try netinst, but I think that either the installation guide needs to be
changed to conform to what the LiveCD can do, or the LiveCD needs to be changed
so that procedures suggested by the installation guide actually work.
--- Additional comment from Lior on 2017-02-23 12:10:18 CET ---
For example, the installation guide can say at the beginning of Section 11 that
VNC installation is only supported by the netinst image, not by the LiveCD.
--- Additional comment from Martin Kolman on 2017-02-24 10:59:55 CET ---
(In reply to Lior from comment #5)
> For example, the installation guide can say at the beginning of Section 11
> that VNC installation is only supported by the netinst image, not by the
> LiveCD.
Yes - that really looks like an omission in the docs. I'll clone this bug &
assign it to the docs component so it can be fixed.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1425589
[Bug 1425589] vnc boot fails to find metacity
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 2 months
[Bug 1409295] New: Errors in Chapter 10 "Setting Up an Installation
Server
"
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1409295
Bug ID: 1409295
Summary: Errors in Chapter 10 "Setting Up an Installation
Server"
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: cspicer(a)redhat.com
Reporter: frank(a)crawford.emu.id.au
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
There are two separate errors I've notice in Chapter 10 "Setting Up an
Installation Server" of the Installation Guide for F25, and probably earlier
editions.
Version-Release number of selected component (if applicable):
Installation Guide for Fedora 25
How reproducible:
100%
Steps to Reproduce:
1. Read page, follow link ...
2.
3.
Actual results:
Section 10.2, item 4, the example box refers to RFC4758 for details of the arch
option. It should be RFC4578.
Secondly, section 10.4 item 2, says "Create a boot menu for UEFI cleints at
/var/lib/tftpboot/pxelinux/uefi", but that is a non-existent path/file. I
suspect it should be "/var/lib/tftpboot/uefi/grub.cfg", but cannot be sure.
Expected results:
Correct information.
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 2 months
[Bug 1409148] New: Are we using liveusb-creator or Fedora Media
Writer?
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1409148
Bug ID: 1409148
Summary: Are we using liveusb-creator or Fedora Media Writer?
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: cspicer(a)redhat.com
Reporter: puiterwijk(a)redhat.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
In Fedora 25 Install guide
(https://docs.fedoraproject.org/en-US/Fedora/25/html/Installation_Guide/se...):
On Fedora 24 or later, you can download Fedora Image Writer with the command:
$ sudo dnf install liveusb-creator
You can call Fedora Media Writer by issuing the command:
$ sudo liveusb-creator
While Media Writer provides liveusb-creator, we might want to provide "dnf
install mediawriter".
However, that is just a small annoyance, the big painpoint is with "sudo
liveusb-creator", which is NOT a binary provided by mediawriter.
Which means one has to manually figure out they are supposed to run "sudo
mediawriter".
Also, do we really want to suggest this method of starting and running?
First off, I think GNOME software might have it listed, so mentioning that as
the primary method might be more user-friendly?
Second, please do not teach people to just randomly slap "sudo" in front of
commands. As far as I know, mediawriter can be started as normal user perfectly
fine, and it'll ask for permissions as soon as they are needed.
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 2 months
[Bug 1409016] New: Errors in pxe-bootloader page
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1409016
Bug ID: 1409016
Summary: Errors in pxe-bootloader page
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: cspicer(a)redhat.com
Reporter: redhat(a)lfcode.ca
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
*
`ks=https://git.fedorahosted.org/cgit/spin-kickstarts.git/plain/fedora-install-server.ks?h=f21`
is in the uefi cmdline for Server. f21 should read f25.
* `append f25/initrd=initrd.img` is under the uefi rescue configuration. It
should probably read `append initrd=f25/initrd.img`.
* inconsistent use of `linuxefi` vs `kernel`. In the section for the
installation of Fedora server, it uses `kernel`, whereas for Workstation, it
uses `linuxefi`. One of these is almost certainly an error.
Additional info:
Errors found on f25 page
(https://docs.fedoraproject.org/en-US/Fedora/25/html/Installation_Guide/px...)
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 2 months
[Bug 1397670] New: Log consoles are not on Ctrl+Alt+F1 anymore (F25)
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1397670
Bug ID: 1397670
Summary: Log consoles are not on Ctrl+Alt+F1 anymore (F25)
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: cspicer(a)redhat.com
Reporter: damien(a)cassou.me
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Install guide says to use Ctrl+Alt+F1 to view the consoles, but in F25, this
doesn't work anymore. This is probably related to Wayland.
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 2 months
[Bug 1387891] New: dd command in Creating USB Media requires root or
sudo
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1387891
Bug ID: 1387891
Summary: dd command in Creating USB Media requires root or sudo
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: low
Assignee: cspicer(a)redhat.com
Reporter: info(a)skierpage.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
https://docs.fedoraproject.org/en-US/Fedora/24/html/Installation_Guide/se...
says
Use the dd utility to write the image. _Make sure you have the right drive!_
# dd if=/path/to/Fedora-Live-Security-x86_64-21.iso of=/dev/sdd
as the '#' prompt hints, you need to be root tin order to run this command. It
would be better to be explicit, saying something like
Use the dd utility to write the image onto the USB drive. You need to be root
to do this, hence the example uses `sudo`. _Make sure you have the right
drive!_
$ sudo dd if=/path/to/Fedora-Live-Security-x86_64-21.iso of=/dev/sdd
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 2 months