September 2017 - docs-qa - Fedora mailing-lists

[Bug 1021605] New: No Default Syslog
by Red Hat Bugzilla 30 Nov '18

30 Nov '18

https://bugzilla.redhat.com/show_bug.cgi?id=1021605 Bug ID: 1021605 Summary: No Default Syslog Product: Fedora Documentation Version: devel Component: install-guide Keywords: Tracking Assignee: pbokoc(a)redhat.com Reporter: pbokoc(a)redhat.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: brentrbrian(a)gmail.com, johannbg(a)gmail.com, jreznik(a)redhat.com, kvolny(a)redhat.com, mattdm(a)redhat.com, pbokoc(a)redhat.com, yjcoshc(a)gmail.com, zach(a)oglesby.co, zbyszek(a)in.waw.pl Depends On: 967521, 998573 Blocks: 1001355, 1001356 +++ This bug was initially created as a clone of Bug #998573 +++ This is a tracking bug for Change: No Default Syslog For more details, see: http://fedoraproject.org//wiki/Changes/NoDefaultSyslog No longer install a traditional syslog service by default. (Specifically, remove rsyslog from the @core or @standard groups in comps.) --- Additional comment from Zbigniew Jędrzejewski-Szmek on 2013-10-08 15:22:54 EDT --- http://cgit.freedesktop.org/systemd/systemd/commit/?id=2b8f6883a17b --- Additional comment from Jaroslav Reznik on 2013-10-11 04:44:57 EDT --- This message is a reminder that Fedora 20 Accepted Changes 100% Completed Deadline is on 2013-10-15 [1]. All Accepted Changes has to be code complete and ready to be validated in the Beta release (optionally by Fedora QA). Required bug state at this point is ON_QA. As for several System Wide Changes, Beta Change Deadline is a point of contingency plan, all incomplete Changes will be reported to FESCo for 2013-10-16 meeting. In case of any questions, don't hesitate to ask Wrangler (jreznik). [1] https://fedoraproject.org/wiki/Releases/20/Schedule --- Additional comment from Matthew Miller on 2013-10-15 14:38:53 EDT --- The basic change to implement this went in, although quite a few packages still bring in rsyslogd as a dependency. I think this feature is fine as it is, and we'll detangle that as part of making separate, targeted Fedora products. --- Additional comment from Jaroslav Reznik on 2013-10-16 06:56:42 EDT --- Ok, thanks, moving to ON_QA. --- Additional comment from Karel Volný on 2013-10-21 08:27:14 EDT --- just FTR, journal brings bug #967521 - how could we switch to this nonsense if that one is still unresolved? well, in fact, how could we even have this activated by default, maybe I'm just out of luck googling, but I see no approval for journal to be used? --- Additional comment from Jóhann B. Guðmundsson on 2013-10-21 08:59:21 EDT --- Just an FYI This feature is not as simple as no default syslog. We need to fix the entire syslog ( journal/rsyslog/syslog-ng ) implementation in the distribution, come up with virtual provide ( to sub package or not to sub package rsyslog/syslog-ng ) as well as fix roughly 600 packages. Now the proposal on how to do so has been stuck with FPC for 2 years now and until that has been done and fixed this feature can never be considered 100% complete... --- Additional comment from Matthew Miller on 2013-10-21 09:10:10 EDT --- (In reply to Jóhann B. Guðmundsson from comment #6) > Just an FYI This feature is not as simple as no default syslog. We need to > fix the entire syslog ( journal/rsyslog/syslog-ng ) implementation in the > distribution, come up with virtual provide ( to sub package or not to sub > package rsyslog/syslog-ng ) as well as fix roughly 600 packages. Now the > proposal on how to do so has been stuck with FPC for 2 years now and until > that has been done and fixed this feature can never be considered 100% > complete... I agree that that's the target, and also that it will continue to be slow-moving. This feature was intentionally meant to slice off and accomplish a small portion of that. --- Additional comment from Brent R Brian on 2013-10-21 09:42:27 EDT --- My comments are not intended to be a remedy, fix, enoursement of a fix/remedy or anything other than a "data point". If you guys need a "lab rat", let me know. B --- Additional comment from Jóhann B. Guðmundsson on 2013-10-21 11:10:22 EDT --- (In reply to Matthew Miller from comment #7) > (In reply to Jóhann B. Guðmundsson from comment #6) > > Just an FYI This feature is not as simple as no default syslog. We need to > > fix the entire syslog ( journal/rsyslog/syslog-ng ) implementation in the > > distribution, come up with virtual provide ( to sub package or not to sub > > package rsyslog/syslog-ng ) as well as fix roughly 600 packages. Now the > > proposal on how to do so has been stuck with FPC for 2 years now and until > > that has been done and fixed this feature can never be considered 100% > > complete... > > I agree that that's the target, and also that it will continue to be > slow-moving. This feature was intentionally meant to slice off and > accomplish a small portion of that. That is one of the core problem people really as in that feature and related work are just implemented up to the point it serves the feature requester need ( and is labelled as 100% feature completed ) as opposed to the actual work required to implement properly into the distribution. What we need to do is to keep distribute wide changes as these in a separated branch and switch all the components at the same time when the feature actually is 100% feature complete Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=967521 [Bug 967521] /var/log/journal breaks system startup https://bugzilla.redhat.com/show_bug.cgi?id=998573 [Bug 998573] No Default Syslog https://bugzilla.redhat.com/show_bug.cgi?id=1001355 [Bug 1001355] No Default Syslog https://bugzilla.redhat.com/show_bug.cgi?id=1001356 [Bug 1001356] No Default Syslog -- You are receiving this mail because: You are the QA Contact for the bug.

2 5

[Bug 1175759] New: Checksum validation in PowerShell is wrong
by Red Hat Bugzilla 05 Nov '18

05 Nov '18

https://bugzilla.redhat.com/show_bug.cgi?id=1175759 Bug ID: 1175759 Summary: Checksum validation in PowerShell is wrong Product: Fedora Documentation Version: devel Component: install-guide Assignee: pbokoc(a)redhat.com Reporter: gliverma(a)westga.edu QA Contact: docs-qa(a)lists.fedoraproject.org CC: pbokoc(a)redhat.com, zach(a)oglesby.co Description of problem: I tried to use the info at http://docs.fedoraproject.org/en-US/Fedora/21/html/Installation_Guide/sect-… and found that the commands did not work due to missing quotes and case sensitivity. Version-Release number of selected component (if applicable): Fedora 21 How reproducible: Every time for me. Steps to Reproduce: 1. Download ISO 2. Download checksum file 3. Use code on http://docs.fedoraproject.org/en-US/Fedora/21/html/Installation_Guide/sect-… Actual results: PS D:\Downloads> $image = "Fedora-Live-Workstation-x86_64-21-5.iso" PS D:\Downloads> $checksum_file = "Fedora-Workstation-21-x86_64-CHECKSUM.md5" PS D:\Downloads> $sha256 = New-Object -TypeName System.Security.Cryptography.sha256CryptoSer viceProvider PS D:\Downloads> $exepected_checksum = ((Get-Content $checksum_file | Select-String -Pattern $image) -split " ")[0] PS D:\Downloads> $download_checksum = [System.BitConverter]::ToString($sha256.ComputeHash([S ystem.IO.File]::ReadAllBytes($PWD\$image))) At line:1 char:109 + ... adAllBytes($PWD\$image))) + ~ Missing ')' in method call. At line:1 char:109 + ... adAllBytes($PWD\$image))) + ~~~~~~~ Unexpected token '\$image' in expression or statement. At line:1 char:116 + ... tes($PWD\$image))) + ~ Unexpected token ')' in expression or statement. At line:1 char:117 + ... es($PWD\$image))) + ~ Unexpected token ')' in expression or statement. At line:1 char:118 + ... s($PWD\$image))) + ~ Unexpected token ')' in expression or statement. + CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException + FullyQualifiedErrorId : MissingEndParenthesisInMethodCall Expected results: No errors in console Additional info: I fixed the code and made the output more readable. Below is what I think should be posted on that page of the docs: $image = "Fedora-Live-Workstation-x86_64-21-5.iso" $checksum_file = "Fedora-Workstation-21-x86_64-CHECKSUM" $sha256 = New-Object -TypeName System.Security.Cryptography.sha256CryptoServiceProvider $expected_checksum = ((Get-Content $checksum_file | Select-String -Pattern $image) -split " ")[0].ToLower() $download_checksum = [System.BitConverter]::ToString($sha256.ComputeHash([System.IO.File]::ReadAllBytes("$PWD\$image"))).ToLower() -replace '-', '' if ( "$download_checksum" -eq "$expected_checksum" ) { echo "Checksum test passed!" } else { echo "Checksum test failed." } echo "Download Checksum: $download_checksum" echo "Expected Checksum: $expected_checksum" -- You are receiving this mail because: You are the QA Contact for the bug.

2 4

[Bug 1220155] New: gnome-system-monitor Network Rates are off by order of magnitude
by Red Hat Bugzilla 13 Aug '18

13 Aug '18

https://bugzilla.redhat.com/show_bug.cgi?id=1220155 Bug ID: 1220155 Summary: gnome-system-monitor Network Rates are off by order of magnitude Product: Fedora Documentation Version: devel Component: amateur-radio-guide Severity: low Assignee: wb8rcr(a)arrl.net Reporter: bugzilla_fedora(a)couldbe.securecoffee.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: sparks(a)redhat.com, wb8rcr(a)arrl.net, zach(a)oglesby.co Description of problem: gnome-system-monitor Network Rates display as 2 - 3 times higher than reality. I noticed when torrenting a Linux ISO that maxed out my connection speed that gnome-system-monitor was claiming a transfer rate that was 2-3 times what the torrent client said as well as 2-3 times my FIOS bandwidth availability. Version-Release number of selected component (if applicable): 3.19.3-100.fc20.x86_64 How reproducible: Easily. Steps to Reproduce: 1. Download a large file 2. Compare gnome-system-monitor Network History speeds to another tool 3. Actual results: gnome-system-monitor Network History speeds are 2-3 times reality. Expected results: Accurate values. Additional info: -- You are receiving this mail because: You are the QA Contact for the bug.

2 2

[Bug 1008207] New: FreeIPA OTP UI
by Red Hat Bugzilla 10 Aug '18

10 Aug '18

https://bugzilla.redhat.com/show_bug.cgi?id=1008207 Bug ID: 1008207 Summary: FreeIPA OTP UI Product: Fedora Documentation Version: devel Component: docs-requests Keywords: Tracking Assignee: nobody(a)fedoraproject.org Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: jreznik(a)redhat.com, nathaniel(a)natemccallum.com, nobody(a)fedoraproject.org, sparks(a)redhat.com, stickster(a)gmail.com, tbabej(a)redhat.com, zach(a)oglesby.co Depends On: 998526 +++ This bug was initially created as a clone of Bug #998526 +++ This is a tracking bug for Change: FreeIPA OTP UI For more details, see: http://fedoraproject.org//wiki/Changes/IPAv3OTPUI FreeIPA will gain a user interface for managing users' OTP tokens. --- Additional comment from Tomas Babej on 2013-08-28 10:24:59 EDT --- This feature is self-contained and not in a testable state yet. It is planned for FreeIPA 3.4 Beta release which is aligned with the F20 schedule. ------------------------------------------------------------------ Discussion at https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001200.h… Please assess existing documentation for the impact of this Change. -- You are receiving this mail because: You are the QA Contact for the bug.

2 3

[Bug 1008206] New: FreeIPA OTP UI
by Red Hat Bugzilla 10 Aug '18

10 Aug '18

https://bugzilla.redhat.com/show_bug.cgi?id=1008206 Bug ID: 1008206 Summary: FreeIPA OTP UI Product: Fedora Documentation Version: devel Component: release-notes Keywords: Tracking Assignee: relnotes(a)fedoraproject.org Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: jreznik(a)redhat.com, nathaniel(a)natemccallum.com, relnotes(a)fedoraproject.org, tbabej(a)redhat.com, wb8rcr(a)arrl.net, zach(a)oglesby.co Depends On: 998526 +++ This bug was initially created as a clone of Bug #998526 +++ This is a tracking bug for Change: FreeIPA OTP UI For more details, see: http://fedoraproject.org//wiki/Changes/IPAv3OTPUI FreeIPA will gain a user interface for managing users' OTP tokens. --- Additional comment from Tomas Babej on 2013-08-28 10:24:59 EDT --- This feature is self-contained and not in a testable state yet. It is planned for FreeIPA 3.4 Beta release which is aligned with the F20 schedule. ---------------------------------------------------------------------- Discussion at https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001200.h… Please document this Change in the Release Notes. -- You are receiving this mail because: You are the QA Contact for the bug.

2 3

[Bug 1008191] New: Apache OpenOffice
by Red Hat Bugzilla 10 Aug '18

10 Aug '18

https://bugzilla.redhat.com/show_bug.cgi?id=1008191 Bug ID: 1008191 Summary: Apache OpenOffice Product: Fedora Documentation Version: devel Component: docs-requests Keywords: Tracking Assignee: nobody(a)fedoraproject.org Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: jreznik(a)redhat.com, nobody(a)fedoraproject.org, sparks(a)redhat.com, stickster(a)gmail.com, zach(a)oglesby.co Depends On: 998511 +++ This bug was initially created as a clone of Bug #998511 +++ This is a tracking bug for Change: Apache OpenOffice For more details, see: http://fedoraproject.org//wiki/Changes/ApacheOpenOffice Add Apache OpenOffice, the free productivity suite, to Fedora. -- You are receiving this mail because: You are the QA Contact for the bug.

2 3

[Bug 1008190] New: Apache OpenOffice
by Red Hat Bugzilla 10 Aug '18

10 Aug '18

https://bugzilla.redhat.com/show_bug.cgi?id=1008190 Bug ID: 1008190 Summary: Apache OpenOffice Product: Fedora Documentation Version: devel Component: release-notes Keywords: Tracking Assignee: relnotes(a)fedoraproject.org Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: jreznik(a)redhat.com, relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net, zach(a)oglesby.co Depends On: 998511 +++ This bug was initially created as a clone of Bug #998511 +++ This is a tracking bug for Change: Apache OpenOffice For more details, see: http://fedoraproject.org//wiki/Changes/ApacheOpenOffice Add Apache OpenOffice, the free productivity suite, to Fedora. -- You are receiving this mail because: You are the QA Contact for the bug.

2 4

[Bug 1021570] New: OS Installer Support for LVM Thin Provisioning
by Red Hat Bugzilla 10 Aug '18

10 Aug '18

https://bugzilla.redhat.com/show_bug.cgi?id=1021570 Bug ID: 1021570 Summary: OS Installer Support for LVM Thin Provisioning Product: Fedora Documentation Version: devel Component: install-guide Keywords: Tracking Assignee: pbokoc(a)redhat.com Reporter: pbokoc(a)redhat.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: dlehman(a)redhat.com, jreznik(a)redhat.com, pbokoc(a)redhat.com, zach(a)oglesby.co Depends On: 998527 Blocks: 998532, 1008211, 1008212 +++ This bug was initially created as a clone of Bug #998527 +++ This is a tracking bug for Change: OS Installer Support for LVM Thin Provisioning For more details, see: http://fedoraproject.org//wiki/Changes/InstallerLVMThinProvisioningSupport LVM has introduced thin provisioning technology, which provides greatly improved snapshot functionality in addition to thin provisioning capability. This change will make it possible to configure thin provisioning during OS installation. --- Additional comment from David Lehman on 2013-08-27 11:28:33 EDT --- The only missing piece is a way to select a usage profile in anaconda. You specify metadata size and chunk size via kickstart. The bug to add profiles to lvm2 for common thinp usage patterns is bug 958464. --- Additional comment from Jaroslav Reznik on 2013-10-11 04:45:46 EDT --- This message is a reminder that Fedora 20 Accepted Changes 100% Completed Deadline is on 2013-10-15 [1]. All Accepted Changes has to be code complete and ready to be validated in the Beta release (optionally by Fedora QA). Required bug state at this point is ON_QA. As for several System Wide Changes, Beta Change Deadline is a point of contingency plan, all incomplete Changes will be reported to FESCo for 2013-10-16 meeting. In case of any questions, don't hesitate to ask Wrangler (jreznik). [1] https://fedoraproject.org/wiki/Releases/20/Schedule --- Additional comment from Jaroslav Reznik on 2013-10-21 10:13:43 EDT --- I see 958464 in POST state but probably without profiles. Is it acceptable to consider this Change completed without it or not? FESCo asked me to finish review of Changes this week. Thanks. Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=998527 [Bug 998527] OS Installer Support for LVM Thin Provisioning https://bugzilla.redhat.com/show_bug.cgi?id=998532 [Bug 998532] Snapshot and Rollback Tool https://bugzilla.redhat.com/show_bug.cgi?id=1008211 [Bug 1008211] OS Installer Support for LVM Thin Provisioning https://bugzilla.redhat.com/show_bug.cgi?id=1008212 [Bug 1008212] OS Installer Support for LVM Thin Provisioning -- You are receiving this mail because: You are the QA Contact for the bug.

2 3

[Bug 1008211] New: OS Installer Support for LVM Thin Provisioning
by Red Hat Bugzilla 10 Aug '18

10 Aug '18

https://bugzilla.redhat.com/show_bug.cgi?id=1008211 Bug ID: 1008211 Summary: OS Installer Support for LVM Thin Provisioning Product: Fedora Documentation Version: devel Component: release-notes Keywords: Tracking Assignee: relnotes(a)fedoraproject.org Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: dlehman(a)redhat.com, jreznik(a)redhat.com, relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net, zach(a)oglesby.co Depends On: 998527 Blocks: 998532 +++ This bug was initially created as a clone of Bug #998527 +++ This is a tracking bug for Change: OS Installer Support for LVM Thin Provisioning For more details, see: http://fedoraproject.org//wiki/Changes/InstallerLVMThinProvisioningSupport LVM has introduced thin provisioning technology, which provides greatly improved snapshot functionality in addition to thin provisioning capability. This change will make it possible to configure thin provisioning during OS installation. --- Additional comment from David Lehman on 2013-08-27 11:28:33 EDT --- The only missing piece is a way to select a usage profile in anaconda. You specify metadata size and chunk size via kickstart. The bug to add profiles to lvm2 for common thinp usage patterns is bug 958464. -------------------------------- Discussion at https://lists.fedoraproject.org/pipermail/devel/2013-July/185803.html Please document this Change in the Release Notes -- You are receiving this mail because: You are the QA Contact for the bug.

2 4

[Bug 1008212] New: OS Installer Support for LVM Thin Provisioning
by Red Hat Bugzilla 10 Aug '18

10 Aug '18

https://bugzilla.redhat.com/show_bug.cgi?id=1008212 Bug ID: 1008212 Summary: OS Installer Support for LVM Thin Provisioning Product: Fedora Documentation Version: devel Component: docs-requests Keywords: Tracking Assignee: nobody(a)fedoraproject.org Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: dlehman(a)redhat.com, jreznik(a)redhat.com, nobody(a)fedoraproject.org, sparks(a)redhat.com, stickster(a)gmail.com, zach(a)oglesby.co Depends On: 998527 Blocks: 998532 +++ This bug was initially created as a clone of Bug #998527 +++ This is a tracking bug for Change: OS Installer Support for LVM Thin Provisioning For more details, see: http://fedoraproject.org//wiki/Changes/InstallerLVMThinProvisioningSupport LVM has introduced thin provisioning technology, which provides greatly improved snapshot functionality in addition to thin provisioning capability. This change will make it possible to configure thin provisioning during OS installation. --- Additional comment from David Lehman on 2013-08-27 11:28:33 EDT --- The only missing piece is a way to select a usage profile in anaconda. You specify metadata size and chunk size via kickstart. The bug to add profiles to lvm2 for common thinp usage patterns is bug 958464. -------------------------------------- Discussion at https://lists.fedoraproject.org/pipermail/devel/2013-July/185803.html Please assess existing documentation for the impact of this Change. -- You are receiving this mail because: You are the QA Contact for the bug.

2 4

[Bug 1358932] New: How to create an USB stick with overlay persistence with graphical tools?
by Red Hat Bugzilla 30 Apr '18

30 Apr '18

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.

2 3

[Bug 1314499] New: Typo in Section 5.4.8: Installation Destination
by Red Hat Bugzilla 15 Mar '18

15 Mar '18

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.

2 2

[Bug 1492509] New: Boot logo not showing up and many lines of command show up on boot
by bugzilla＠redhat.com 08 Mar '18

08 Mar '18

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.

1 2

[Bug 1344465] New: Copyright should be 2016 - can we also have translation of license ?
by Red Hat Bugzilla 19 Feb '18

19 Feb '18

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.

2 2

[Bug 1471433] New: deadlink to cobbler manual
by bugzilla＠redhat.com 30 Jan '18

30 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=1471433 Bug ID: 1471433 Summary: deadlink to cobbler manual Product: Fedora Documentation Version: devel Component: install-guide Severity: low Assignee: cspicer(a)redhat.com Reporter: peter.klassen(a)apbox.de QA Contact: docs-qa(a)lists.fedoraproject.org CC: pbokoc(a)redhat.com, zach(a)oglesby.co Description of problem: Documentaion subsection 10.7. Advanced network installations with Cobbler links to http://www.cobblerd.org/manuals/2.6.0/ this url is a deadlink and should be replaced by https://cobbler.github.io/manuals/2.8.0/ or https://cobbler.github.io/manuals/ cheers PK -- You are receiving this mail because: You are the QA Contact for the bug.

1 1

[Bug 1434185] New: The instructions for running the liveusb-creator are wrong.
by bugzilla＠redhat.com 30 Jan '18

30 Jan '18

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/sect… 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.

1 1

[Bug 1426560] New: vnc boot fails to find metacity
by bugzilla＠redhat.com 30 Jan '18

30 Jan '18

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/Workstation… 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-v… --- 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/sect…">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.

1 3

[Bug 1409295] New: Errors in Chapter 10 "Setting Up an Installation Server "
by Red Hat Bugzilla 30 Jan '18

30 Jan '18

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.

2 1

[Bug 1409148] New: Are we using liveusb-creator or Fedora Media Writer?
by Red Hat Bugzilla 30 Jan '18

30 Jan '18

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/sect…) 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.

2 1

[Bug 1409016] New: Errors in pxe-bootloader page
by Red Hat Bugzilla 30 Jan '18

30 Jan '18

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/pxe-…) -- You are receiving this mail because: You are the QA Contact for the bug.

2 3

[Bug 1397670] New: Log consoles are not on Ctrl+Alt+F1 anymore (F25)
by Red Hat Bugzilla 30 Jan '18

30 Jan '18

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.

2 1

[Bug 1387891] New: dd command in Creating USB Media requires root or sudo
by Red Hat Bugzilla 30 Jan '18

30 Jan '18

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/sect… 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.

2 1

[Bug 1374064] New: Booting Your Computer in Rescue Mode
by Red Hat Bugzilla 30 Jan '18

30 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=1374064 Bug ID: 1374064 Summary: Booting Your Computer in Rescue Mode Product: Fedora Documentation Version: devel Component: install-guide Assignee: cspicer(a)redhat.com Reporter: bugzilla(a)colorremedies.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: pbokoc(a)redhat.com, zach(a)oglesby.co Created attachment 1198832 --> https://bugzilla.redhat.com/attachment.cgi?id=1198832&action=edit screenshot Description of problem: This section doesn't apply to live media, as it's a graphical boot and the Anaconda rescue mode is text based so it won't work in graphical boot. Therefore inst.rescue doesn't apply, and also there is no "Rescue a Fedora System" option on lives. What they can do is include a boot parameter: init=/bin/bash The problem with using rescue.target or emergency.target is Fedora lives don't set a root user password, and systemd requires a root password to use those targets. https://docs.fedoraproject.org/en-US/Fedora/23/html/Installation_Guide/sect… https://docs.fedoraproject.org/en-US/Fedora/24/html/Installation_Guide/sect… -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 1356760] New: Installation guide contains irrelevant statement.
by Red Hat Bugzilla 30 Jan '18

30 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=1356760 Bug ID: 1356760 Summary: Installation guide contains irrelevant statement. Product: Fedora Documentation Version: devel Component: install-guide Severity: low Assignee: cspicer(a)redhat.com Reporter: worley(a)theworld.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: pbokoc(a)redhat.com, zach(a)oglesby.co Description of problem: In the installation guide for Fedora 24, chapter 2, section "Media Types", there is the statement "In Fedora 21, the DVD option is only available in the Fedora Server flavor." As this installation guide is for Fedora 24, this sentence is irrelevant. Version-Release number of selected component (if applicable): Fedora 24 How reproducible: always Steps to Reproduce: 1. Go to https://docs.fedoraproject.org/en-US/Fedora/24/html/Installation_Guide/chap… 2. Go to section "Media Types", subsection "DVD Image". 3. This is the 2nd sentence in the subsection. Actual results: Contains the sentence "In Fedora 21, the DVD option is only available in the Fedora Server flavor." Expected results: There is no sentence concerning Fedora 21. Additional info: -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 1354201] New: SUSE Studio ImageWriter probably shouldn' t be recommended
by Red Hat Bugzilla 30 Jan '18

30 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=1354201 Bug ID: 1354201 Summary: SUSE Studio ImageWriter probably shouldn't be recommended Product: Fedora Documentation Version: devel Component: install-guide Assignee: cspicer(a)redhat.com Reporter: bugzilla(a)colorremedies.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: pbokoc(a)redhat.com, zach(a)oglesby.co Description of problem: https://docs.fedoraproject.org/en-US/Fedora/24/html/Installation_Guide/sect… Version-Release number of selected component (if applicable): Fedora 23 Fedora 24 Actual results: Docs says "Download and run the SUSE Studio ImageWriter or Rawrite32." The ImageWriter link URL is https://github.com/downloads/openSUSE/kiwi/ImageWriter.exe The problems are: - I can't verify the provenance of the binary downloaded from that link. I get 404 errors when I try to get to each parent directory, so I have no idea what this binary really is, who produced it, how old it is, what version it is, etc. I think recommending users download an almost random binary on Windows of all OS's probably isn't good advice. - openSUSE considers ImageWriter unmaintained. "We used to have SUSE Studio ImageWriter compiled for windows, but this is not maintained anymore." https://en.opensuse.org/SDB:Create_a_Live_USB_stick_using_Windows And they point to a different URL for that project than we do, which hasn't had a pull request or issue responded to in over a year. Nevertheless the code there is probably newer than the binary we're offering to download. http://www.github.com/openSUSE/imagewriter Expected results: Let's just recommend Rawrite32, it's recently updated and it looks like the binaries are signed. http://www.netbsd.org/~martin/rawrite32/ Additional info: -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

docs-qa September 2017