docs-qa April 2016

docs-qa@lists.fedoraproject.org

1 participants
83 discussions

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

16 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 1318103] New: LiveUSB Creator as primary downloadable
by Red Hat Bugzilla 31 Jan '18

31 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=1318103 Bug ID: 1318103 Summary: LiveUSB Creator as primary downloadable 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: Currently LiveUSB Creator is not mentioned at all in official documentation for any platform. https://docs.fedoraproject.org/en-US/Fedora/23/html/Installation_Guide/sect… First, the two Windows platform recommendations in the documentation are odd because they're neither created nor tested within Fedora. Second, Live USB Creator is planned to be the primary/most prominent download method for Fedora 24 for Fedora (maybe other Linux distros as well), Windows, and possibly OS X if it arrives in time. So documentation should be updated to reflect this. Change description: https://fedoraproject.org/wiki/Releases/24/ChangeSet#LiveUSBCreator_as_Prim… Bug tracking: https://bugzilla.redhat.com/show_bug.cgi?id=1310542 -- You are receiving this mail because: You are the QA Contact for the bug.

2 3

[Bug 1312621] New: dhcpd instructions are unclear for PXE boot
by Red Hat Bugzilla 31 Jan '18

31 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=1312621 Bug ID: 1312621 Summary: dhcpd instructions are unclear for PXE boot Product: Fedora Documentation Version: devel Component: install-guide Assignee: cspicer(a)redhat.com Reporter: danofsatx(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: pbokoc(a)redhat.com, zach(a)oglesby.co Section 10.2 of the Installation Guide gives the example setup for dhcpd to enable a PXE boot / network installation. The example is unclear between paragraphs 2 and 4 in that the text in paragraph 4 does not match up with the text in paragraph 2, and there are no clear instructions as to where it goes in the example file. After trial and error and comparing with the F20 instructions, I was able to get dhcpd started again. I suggest modifying paragraph 4 to include the whole file as such: option arch code 93 = unsigned integer 16; subnet 192.168.1.0 netmask 255.255.255.0 { option domain-name-servers 192.168.1.1; option routers 192.168.1.1; range 192.168.1.11 192.168.1.50; authoritative; default-lease-time 600; max-lease-time 7200; ddns-update-style none; if option arch = 00:07 { filename "uefi/shim.efi"; } else { filename "pxelinux.0"; } next-server 192.168.1.2; } -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 1309111] New: Package environment ID required in kickstart
by Red Hat Bugzilla 31 Jan '18

31 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=1309111 Bug ID: 1309111 Summary: Package environment ID required in kickstart Product: Fedora Documentation Version: devel Component: install-guide Assignee: cspicer(a)redhat.com Reporter: dgallowa(a)redhat.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: pbokoc(a)redhat.com, zach(a)oglesby.co Description of problem: Documentation states a package environment's name can be specified in a kickstart when the ID is required instead. https://docs.fedoraproject.org/en-US/Fedora/22/html/Installation_Guide/sect… @^Infrastructure Server <- does not work @^infrastructure-server-environment <- works Version-Release number of selected component (if applicable): Fedora 22 How reproducible: Every time Steps to Reproduce: 1. Create kickstart specifying @^Infrastructure Server in %packages 2. Start install Actual results: You have specified that the group 'Infrastructure Server' should be installed. This group does not exist. Would you like to ignore this group and continue with installation? Please respond 'yes' or 'no': Expected results: Group/Environment get installed Additional info: -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 1162045] New: Power Mgmt Guide needs to Address Howto Suppress Sleep State
by Red Hat Bugzilla 30 Jan '18

30 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=1162045 Bug ID: 1162045 Summary: Power Mgmt Guide needs to Address Howto Suppress Sleep State Product: Fedora Documentation Version: devel Component: power-management-guide Severity: low Assignee: yruseva(a)redhat.com Reporter: redzilla.coralnut(a)xoxy.net QA Contact: docs-qa(a)lists.fedoraproject.org CC: ddomingo(a)redhat.com, yruseva(a)redhat.com, zach(a)oglesby.co Description of problem: F20 Power Management Guide does not address the hooks into the sleep system provided by systemd. Ever since p,m-utils was deprecated there have been no Fedora/RHAT resources available that discuss how to utilize the hooks into the sleep system to prevent entry into the sleep state. Example: in the era of pm-utils (going back to what, F15?) one could write scripts to suppress the transition to S3 if a desirable network connection were established that should not be interrupted. All that was required was to place the script in /etc/pm/sleep.d/ and have it issue a non-zero exit code if sleep should be suppressed. When the goto sleep process prepared for sleep by executing the script, the script could deliver a non-zero exit code and prevent entry into the sleep state. Now that pm-utils has been deprecated and replaced with systemd, Fedora now ignores any/all scripts in /etc/pm/*. That isn't a problem. What *IS* a problem, though, is that for the past 5 releases of Fedora, the Power Management Guide has completely ignored the topic of how to use custom scripts to prevent entry into the sleep state. As a result, our only options are to look for help and examples in other distributions. Version-Release number of selected component (if applicable): F20, F21 How reproducible: N/A. The documentation doesn't address the problem. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 1080006] New: Incorrect command for multi-core power saving
by Red Hat Bugzilla 30 Jan '18

30 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=1080006 Bug ID: 1080006 Summary: Incorrect command for multi-core power saving Product: Fedora Documentation Version: devel Component: power-management-guide Assignee: yruseva(a)redhat.com Reporter: fedorabugs(a)aylett.co.uk QA Contact: docs-qa(a)lists.fedoraproject.org CC: ddomingo(a)redhat.com, yruseva(a)redhat.com, zach(a)oglesby.co Description of problem: In section 4.2 [https://docs.fedoraproject.org/en-US/Fedora/20/html/Power_Management_Guide/…] there's a list of commands that can be executed to save some power. The command listed for "enable multi-core power-saving (part of the laptop-battery-powersave profile)" is a duplicate of the previous command and is therefore incorrect. Version-Release number of selected component (if applicable): 1.1-0 The command is given as: echo Y > /sys/module/snd_ac97_codec/parameters/power_save Which is the command for enabling audio codec power saving, not for enabling multi-core power saving. -- You are receiving this mail because: You are the QA Contact for the bug.

2 2

[Bug 1036886] New: Incorrect command to start tuned at boot in Power Management Guide
by Red Hat Bugzilla 30 Jan '18

30 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=1036886 Bug ID: 1036886 Summary: Incorrect command to start tuned at boot in Power Management Guide Product: Fedora Documentation Version: devel Component: power-management-guide Assignee: yruseva(a)redhat.com Reporter: stevenhrosenberg(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: ddomingo(a)redhat.com, yruseva(a)redhat.com, zach(a)oglesby.co Description of problem: On this page -- http://docs.fedoraproject.org/en-US/Fedora/19/html/Power_Management_Guide/s… -- the command to start the tuned utility at boot has two words transposed: Specifically right here -- http://docs.fedoraproject.org/en-US/Fedora/19/html/Power_Management_Guide/s…: How it reads: To enable tuned to start every time the machine boots, type the following command: systemctl tuned enable But it should be: To enable tuned to start every time the machine boots, type the following command: systemctl enable tuned As you can see, the last two words of the command need to be transposed. -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 1008872] New: CPUfreq documentation for F19 lacks information on the new intel_pstate driver and its governors
by Red Hat Bugzilla 30 Jan '18

30 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=1008872 Bug ID: 1008872 Summary: CPUfreq documentation for F19 lacks information on the new intel_pstate driver and its governors Product: Fedora Documentation Version: devel Component: power-management-guide Assignee: yruseva(a)redhat.com Reporter: mail2benny(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: ddomingo(a)redhat.com, yruseva(a)redhat.com, zach(a)oglesby.co https://docs.fedoraproject.org/en-US/Fedora/19/html/Power_Management_Guide/… only documents governors for the acpi-cpufreq driver but not for the new intel_pstate driver. -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 994167] New: typo in servicectl enable command
by Red Hat Bugzilla 30 Jan '18

30 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=994167 Bug ID: 994167 Summary: typo in servicectl enable command Product: Fedora Documentation Version: devel Component: power-management-guide Assignee: yruseva(a)redhat.com Reporter: joseignacio.quintana(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com, yruseva(a)redhat.com Description of problem: >>> F19, power-management-guide, Section: 2.5.3. Installation and Usage >>> command "systemctl tuned enable" should be "systemctl enable tuned" Version-Release number of selected component (if applicable): >>> F19 doc of power management guide How reproducible: # systemctl tuned enable # ERR: Unknown operation 'tuned'. # systemctl enable tuned # OK: ln -s '/usr/lib/systemd/system/tuned.service' '/etc/systemd/system/multi-user.target.wants/tuned.service' Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 973950] New: Type in Chapter 1.2
by Red Hat Bugzilla 30 Jan '18

30 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=973950 Bug ID: 973950 Summary: Type in Chapter 1.2 Product: Fedora Documentation Version: devel Component: power-management-guide Severity: low Priority: unspecified Assignee: r.landmann(a)redhat.com Reporter: swierckx(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com, r.landmann(a)redhat.com Description of problem: In chapter 1.2 of the power management guide there is a type in the fedora version mentioned "The kernel used in releases of Fedora prior to Fedora 8 used a periodic timer for each CPU. This timer prevents the CPU from truly going idle ..." should probably be ""The kernel used in releases of Fedora prior to Fedora 18 used a periodic timer for each CPU. This timer prevents the CPU from truly going idle ..."" I deducted this from the sentence a little further where it is mentioned that only from Fedora 18 the idle CPU state is tickles -- You are receiving this mail because: You are the QA Contact for the bug.

2 3

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

docs-qa April 2016