[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.
6 years
[Bug 1525400] New:
Pictures that illustrate the System Monitor tool are henceforth obsolete.
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1525400
Bug ID: 1525400
Summary: Pictures that illustrate the System Monitor tool are
henceforth obsolete.
Product: Fedora Documentation
Version: devel
Component: system-administrator's-guide
Severity: low
Assignee: swadeley(a)redhat.com
Reporter: ricky.tigg(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: swadeley(a)redhat.com
Description of problem:
Pictures that illustrate the System Monitor tool are henceforth obsolete.
Version-Release number of selected component (if applicable):
gnome-system-monitor-3.26.0-1.fc27.x86_64
Steps to Reproduce:
1. Home | Fedora 27 | Fedora System Administration Guide | Monitoring and
Automation | System Monitoring Tools.
2. Launch System Monitor.
Actual results:
In the on-line documentation, in pictures that illustrate the tool, a System
tab is visible. Such tab is no longer implemented in current component.
Expected results:
Update regarding the pictures are needed.
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 1 month
[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, 2 months
[Bug 1492509] New:
Boot logo not showing up and many lines of command show up on boot
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1492509
Bug ID: 1492509
Summary: Boot logo not showing up and many lines of command
show up on boot
Product: Fedora Documentation
Version: devel
Component: install-guide
Severity: low
Assignee: cspicer(a)redhat.com
Reporter: nelsonleiva8(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
When I boot my system, instead of the Fedora logo showing up while booting, I
get lots of commands showing on black screen:
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node
ffff8e820d0ce5c8), AE_NOT_FOUND (20160831/psparse-543)
> ata3.00: ATA-8: TOSHIBA DT01ACA100, MS2OA750, max UDMA/133
> ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
> ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
>ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff8e820d0ce410), AE_NOT_FOUND (20160831/psparse-543)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20160831/psargs-359)
> ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8e820d0cea78), AE_NOT_FOUND (20160831/psparse-543)
>l: ata2.00: ATAPI: TSSTcorp CDDVDW SH-224BB, SB00, max UDMA/100
> ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
>ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff8e820d0ce5c8), AE_NOT_FOUND (20160831/psparse-543)
ata1.00: supports DRM functions and may not be fully accessible
>ata3.00: configured for UDMA/133
ata1.00: NCQ Send/Recv Log not supported
ata1.00: ATA-9: Samsung SSD 840 EVO 120GB, EXT0BB6Q, max UDMA/133
>ata1.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
> ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node
ffff8e820d0cea78), AE_NOT_FOUND (20160831/psparse-543)
>ata2.00: configured for UDMA/100
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT0._GTF] (Node
ffff8e820d0ce410), AE_NOT_FOUND (20160831/psparse-543)
the system runs fine after this process, lets me log in and I've had no errors
while using it. But is there a way to have a normal boot up with just a Fedora
logo while it loads then take me to the login screen?
Version-Release number of selected component (if applicable):
Fedora 26 Kernel 4.12
How reproducible:
Every time it boots.
Steps to Reproduce:
1.
2.
3.
Actual results:
CPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node
ffff8e820d0ce5c8), AE_NOT_FOUND (20160831/psparse-543)
> ata3.00: ATA-8: TOSHIBA DT01ACA100, MS2OA750, max UDMA/133
> ata3.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
> ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
>ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT0._GTF] (Node ffff8e820d0ce410), AE_NOT_FOUND (20160831/psparse-543)
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND
(20160831/psargs-359)
> ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node ffff8e820d0cea78), AE_NOT_FOUND (20160831/psparse-543)
>l: ata2.00: ATAPI: TSSTcorp CDDVDW SH-224BB, SB00, max UDMA/100
> ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
>ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT2._GTF] (Node ffff8e820d0ce5c8), AE_NOT_FOUND (20160831/psparse-543)
ata1.00: supports DRM functions and may not be fully accessible
>ata3.00: configured for UDMA/133
ata1.00: NCQ Send/Recv Log not supported
ata1.00: ATA-9: Samsung SSD 840 EVO 120GB, EXT0BB6Q, max UDMA/133
>ata1.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 31/32), AA
> ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT1._GTF] (Node
ffff8e820d0cea78), AE_NOT_FOUND (20160831/psparse-543)
>ata2.00: configured for UDMA/100
ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
ACPI Error: Method parse/execution failed [\_SB.PCI0.SAT0.SPT0._GTF] (Node
ffff8e820d0ce410), AE_NOT_FOUND (20160831/psparse-543)
Expected results:
The Fedora Icon while loading and the login screen
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 2 months
[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, 3 months
[Bug 1538310] New: "Network Based Installation Guide"
tells user to install grub2-efi, which doesn't contain bootx64.efi
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1538310
Bug ID: 1538310
Summary: "Network Based Installation Guide" tells user to
install grub2-efi, which doesn't contain bootx64.efi
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:
On the "Network Based Installation Guide" page:
https://docs.fedoraproject.org/f27/install-guide/advanced/Network_based_I...
The user is instructed to install grub2-efi to a custom installroot. Then, they
are told to copy $installroot/boot/efi/EFI/fedora/grubx64.efi to their tftp
directory. However, grub2-efi does not contain grubx64.efi, so the given
command fails.
On the page, references to "grub2-efi" should read "grub2-efi-x64".
How reproducible:
100%, the page consistently contains incorrect instructions.
Steps to Reproduce:
1. Go to the page.
2. Follow the instructions to get the EFI executables.
3. Attempt to copy them and fail.
Actual results:
File doesn't exist due to incorrect package being installed.
Expected results:
File is copied successfully.
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 3 months
[Bug 1434185] New:
The instructions for running the liveusb-creator are wrong.
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1434185
Bug ID: 1434185
Summary: The instructions for running the liveusb-creator are
wrong.
Product: Fedora Documentation
Version: devel
Component: install-guide
Assignee: cspicer(a)redhat.com
Reporter: joe(a)zeff.us
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Description of problem:
The page
https://docs.fedoraproject.org/en-US/Fedora/25/html/Installation_Guide/se...
says that you're supposed to use sudo dnf install liveusb-creator to install
the software and sudo liveusb-creator to run it, but the second command is
wrong. You need to use sudo mediawriter to run the program.
Version-Release number of selected component (if applicable):
N/A
How reproducible:
100%
Steps to Reproduce:
1.Install liveusb-creator
2.Try to run it with sudo liveusb-creator
3.
Actual results:
-bash: liveusb-creator: command not found
Expected results:
The program starts.
Additional info:
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 3 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, 3 months