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_persiste…
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.
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.
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.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=1546559
Bug ID: 1546559
Summary: Hacked By KingSkrupellos CyBeRiZM.Org Digital Security
Technological Turkish Moslem Army
Product: Fedora Documentation
Version: devel
Component: accessibility-guide
Severity: low
Assignee: gerard(a)ryan.lt
Reporter: xvryhkw(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: gerard(a)ryan.lt, sparks(a)redhat.com, zach(a)oglesby.co
Created attachment 1397628
--> https://bugzilla.redhat.com/attachment.cgi?id=1397628&action=edit
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
Hacked By KingSkrupellos CyBeRiZM.Org Digital Security Technological Turkish
Moslem Army
--
You are receiving this mail because:
You are the QA Contact for the bug.
The following is a list of bugs or attachments to bugs in which a user has been
waiting more than 7 days for a response from you. Please take
action on these requests as quickly as possible. (Note that some of these bugs
might already be closed, but a user is still waiting for your response.)
We'll remind you again in another 7 days if these requests are still
outstanding, or if there are any new requests where users have been waiting
more than 7 days for your response.
review
------
Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (1245 days old)
https://bugzilla.redhat.com/show_bug.cgi?id=1124344https://bugzilla.redhat.com/attachment.cgi?id=942713&action=edit
To see all your outstanding requests, visit:
https://bugzilla.redhat.com/request.cgi?action=queue&requestee=docs-qa%40li…
The following is a list of bugs or attachments to bugs in which a user has been
waiting more than 7 days for a response from you. Please take
action on these requests as quickly as possible. (Note that some of these bugs
might already be closed, but a user is still waiting for your response.)
We'll remind you again in another 7 days if these requests are still
outstanding, or if there are any new requests where users have been waiting
more than 7 days for your response.
review
------
Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (1238 days old)
https://bugzilla.redhat.com/show_bug.cgi?id=1124344https://bugzilla.redhat.com/attachment.cgi?id=942713&action=edit
To see all your outstanding requests, visit:
https://bugzilla.redhat.com/request.cgi?action=queue&requestee=docs-qa%40li…
The following is a list of bugs or attachments to bugs in which a user has been
waiting more than 7 days for a response from you. Please take
action on these requests as quickly as possible. (Note that some of these bugs
might already be closed, but a user is still waiting for your response.)
We'll remind you again in another 7 days if these requests are still
outstanding, or if there are any new requests where users have been waiting
more than 7 days for your response.
review
------
Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (1231 days old)
https://bugzilla.redhat.com/show_bug.cgi?id=1124344https://bugzilla.redhat.com/attachment.cgi?id=942713&action=edit
To see all your outstanding requests, visit:
https://bugzilla.redhat.com/request.cgi?action=queue&requestee=docs-qa%40li…
The following is a list of bugs or attachments to bugs in which a user has been
waiting more than 7 days for a response from you. Please take
action on these requests as quickly as possible. (Note that some of these bugs
might already be closed, but a user is still waiting for your response.)
We'll remind you again in another 7 days if these requests are still
outstanding, or if there are any new requests where users have been waiting
more than 7 days for your response.
review
------
Bug 1124344: yum --security update doesn't work on non-fedora repos. This limitation is probably undocumented. (1224 days old)
https://bugzilla.redhat.com/show_bug.cgi?id=1124344https://bugzilla.redhat.com/attachment.cgi?id=942713&action=edit
To see all your outstanding requests, visit:
https://bugzilla.redhat.com/request.cgi?action=queue&requestee=docs-qa%40li…