docs-qa October 2015

docs-qa@lists.fedoraproject.org

1 participants
112 discussions

[Bug 1095945] New: RFE: disabling head parking on spinning drives
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=1095945 Bug ID: 1095945 Summary: RFE: disabling head parking on spinning drives Product: Fedora Documentation Version: devel Component: cookbook Assignee: docs(a)lists.fedoraproject.org Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: docs(a)lists.fedoraproject.org Some drives have aggressive APM, and the resulting frequent head parking can negatively impact access latency and produce an annoying clicking sound. Explain the theory, benefits, procedure, and risks of adjusting APM settings with hdparm. -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 982899] New: 7.3.1. Establishing a Wired (Ethernet) Connection
by Red Hat Bugzilla 11 Jul '17

11 Jul '17

https://bugzilla.redhat.com/show_bug.cgi?id=982899 Bug ID: 982899 Summary: 7.3.1. Establishing a Wired (Ethernet) Connection Product: Fedora Documentation Version: devel Component: system-administrator's-guide Severity: unspecified Priority: unspecified Assignee: jhradile(a)redhat.com Reporter: im_dracula(a)hotmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: jhradile(a)redhat.com Description of problem: In section 7.3.1: Default connection no longer called 'em1' No field for 'connection name' you can add new settings for the network under different profiles by selecting 'add profile...' you can remove/reset a profile by going to the 'options' button under the profile and selecting the 'reset' item on the left, and then choosing to either 'reset' or 'forget' -- You are receiving this mail because: You are the QA Contact for the bug.

2 6

[Bug 1198643] New: Append parameters to grub.cfg
by Red Hat Bugzilla 08 May '17

08 May '17

https://bugzilla.redhat.com/show_bug.cgi?id=1198643 Bug ID: 1198643 Summary: Append parameters to grub.cfg Product: Fedora Documentation Version: devel Component: virtualization-guide Assignee: docs(a)lists.fedoraproject.org Reporter: geanceretta(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: docs(a)lists.fedoraproject.org, lnovich(a)redhat.com, zach(a)oglesby.co Description of problem: The instructions[1] of how to append parameters to Grub's grub.config file is obsolete on recent releases of Fedora. The file /boot/grub/grub.conf doesn't exist anymore. The way to do it now is (tested on Fedora 20): 1 - Edit /etc/default/grub 2 - Append information at the line GRUBCMDLINELINUX=" ... console=tty0 console=ttyS0,115200 ... ") 3 - Regenerate the /boot/grub2/grub.cfg file with the command "grub2-mkconfig -o /boot/grub2/grub.cfg" Link: [1] http://docs.fedoraproject.org/en-US/Fedora/18/html/Virtualization_Administr… Additional info: The documentation is refered to version 18 where it should work, but as we don't have a documentation in a most atual release of Fedora for that subject, you can write a note for the users of most recent releases of Fedora that came with Grub2, where the procedure is according with that listed above. -- You are receiving this mail because: You are the QA Contact for the bug.

2 4

[Bug 1225034] New: Install guide edit of the first 25 PDF pages.
by Red Hat Bugzilla 08 May '17

08 May '17

https://bugzilla.redhat.com/show_bug.cgi?id=1225034 Bug ID: 1225034 Summary: Install guide edit of the first 25 PDF pages. Product: Fedora Documentation Version: devel Component: install-guide Assignee: pbokoc(a)redhat.com Reporter: lsatenstein(a)yahoo.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: pbokoc(a)redhat.com, zach(a)oglesby.co Created attachment 1029929 --> https://bugzilla.redhat.com/attachment.cgi?id=1029929&action=edit LibreOffice editing comments against the first 25 pages of the Install guide. Description of problem: There were many typos and statements that do not apply to Fedora 22. The attached libreoffice document details the editing I have performed for the first 25 pages of the PDF manual version. If you reject the errors or accept them, please respond to this bugzilla report so that I may know if it is worth doing the next 25 of the 200 pdf pages. Refer also to 100875 Version-Release number of selected component (if applicable): Install guide for Fedora 22 How reproducible: 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 3

[Bug 1232568] New: Clarification of VNCServer setup Requsted
by Red Hat Bugzilla 21 Nov '16

21 Nov '16

https://bugzilla.redhat.com/show_bug.cgi?id=1232568 Bug ID: 1232568 Summary: Clarification of VNCServer setup Requsted Product: Fedora Documentation Version: devel Component: system-administrator's-guide Assignee: swadeley(a)redhat.com Reporter: eckirchn(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: swadeley(a)redhat.com using: https://docs.fedoraproject.org/en-US/Fedora/21/html/System_Administrators_G… [in the below statements X = {1, 2, 3....10}] I was able to install and connect to a VNC session using "vncviewer -via XXXXX" however it was only after executing "systemctl start vncserver@:X.service' on the remote machine. Executing systemctl enable vncserver@:X.service results in: Failed to execute operation: No such file or directory Section 8.1.3. Starting VNC Server states: systemctl enable vncserver@:display_number.service however, unless one creates a file such as: vncserver@:X.service the command systemctl enable vncserver@:X.service does not work. After some time with the help of [coolmadmax] on IRC://#Fedora, I was able to understand this was where I was missing a step. I think it would help to add some clarifying statements here to help others. The guide [coolmadmax] suggested: https://stufs4u.wordpress.com/2014/02/25/install-and-configure-vnc-server-i… added this ounce of clarification. Help on this issue included [mutk] [fenrus02] [kendell] [devhen] and [_AnK] and I thank all. -- You are receiving this mail because: You are the QA Contact for the bug.

1 2

[Bug 1272433] New: A "short" table of contents would improve the document (IMO)
by Red Hat Bugzilla 23 Aug '16

23 Aug '16

https://bugzilla.redhat.com/show_bug.cgi?id=1272433 Bug ID: 1272433 Summary: A "short" table of contents would improve the document (IMO) Product: Fedora Documentation Version: devel Component: system-administrator's-guide Assignee: swadeley(a)redhat.com Reporter: nljlistbox2(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: swadeley(a)redhat.com Description of problem: The Fedora 21 System Administrator's Guide has a very detailed table of contents which is good, but it hinders quick navigation and makes it hard to grasp the scope of the document. IMO it would improve the document to add a "short" table of contents before the existing long table of contents. Something with the following level of detail would be good: Preface 1. Target Audience 2. How to Read this Book 3. Document Conventions 4. We Need Feedback! 5. Acknowledgments I. Basic System Configuration 1. Opening Graphical Applications 2. System Locale and Keyboard Configuration 3. Configuring the Date and Time 4. Managing Users and Groups II. Package Management 5. Yum III. Infrastructure Services 6. Services and Daemons 7. OpenSSH 8. TigerVNC IV. Servers 9. Web Servers 10. Mail Servers 11. Directory Servers 12. File and Print Servers 13. Configuring NTP Using the chrony Suite 14. Configuring NTP Using ntpd 15. Configuring PTP Using ptp4l V. Monitoring and Automation 16. System Monitoring Tools 17. Viewing and Managing Log Files 18. Automating System Tasks 19. OProfile VI. Kernel, Module and Driver Configuration 20. Working with the GRUB 2 Boot Loader 21. Manually Upgrading the Kernel 22. Working with Kernel Modules A. RPM B. Revision History Index Version-Release number of selected component (if applicable): Current version at https://docs.fedoraproject.org/en-US/Fedora/21/html-single/System_Administr… on 2015-10-16. Additional info: Thank you. -- You are receiving this mail because: You are the QA Contact for the bug.

1 3

[Bug 1001344] New: Allow kdump on secureboot machines
by Red Hat Bugzilla 19 Jul '16

19 Jul '16

https://bugzilla.redhat.com/show_bug.cgi?id=1001344 Bug ID: 1001344 Summary: Allow kdump on secureboot machines 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, vgoyal(a)redhat.com, zach(a)oglesby.co Depends On: 998565 +++ This bug was initially created as a clone of Bug #998565 +++ This is a tracking bug for Change: Allow kdump on secureboot machines For more details, see: http://fedoraproject.org//wiki/Changes/Kdump_with_secureboot Currently kexec/kdump is disabled on machines with secureboot enabled. This feature aims to enable kexec/kdump on such machines. --- Additional comment from Vivek Goyal on 2013-08-22 10:43:53 EDT --- I think first thing is to include a new package ima-evm-tools in F20. I am not sure how to do it. --- Additional comment from Jaroslav Reznik on 2013-08-26 10:28:07 EDT --- (In reply to Vivek Goyal from comment #1) > I think first thing is to include a new package ima-evm-tools in F20. I am > not sure how to do it. Vivek, create Package Review - http://fedoraproject.org/wiki/Package_Review_Process for ima-evm-tools and block this bug on the created review bug. After review, add it to comps. Thank you. Discussion at https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001179.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.

1 2

[Bug 1001343] New: Allow kdump on secureboot machines
by Red Hat Bugzilla 19 Jul '16

19 Jul '16

https://bugzilla.redhat.com/show_bug.cgi?id=1001343 Bug ID: 1001343 Summary: Allow kdump on secureboot machines 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, vgoyal(a)redhat.com, wb8rcr(a)arrl.net, zach(a)oglesby.co Depends On: 998565 +++ This bug was initially created as a clone of Bug #998565 +++ This is a tracking bug for Change: Allow kdump on secureboot machines For more details, see: http://fedoraproject.org//wiki/Changes/Kdump_with_secureboot Currently kexec/kdump is disabled on machines with secureboot enabled. This feature aims to enable kexec/kdump on such machines. --- Additional comment from Vivek Goyal on 2013-08-22 10:43:53 EDT --- I think first thing is to include a new package ima-evm-tools in F20. I am not sure how to do it. --- Additional comment from Jaroslav Reznik on 2013-08-26 10:28:07 EDT --- (In reply to Vivek Goyal from comment #1) > I think first thing is to include a new package ima-evm-tools in F20. I am > not sure how to do it. Vivek, create Package Review - http://fedoraproject.org/wiki/Package_Review_Process for ima-evm-tools and block this bug on the created review bug. After review, add it to comps. Thank you. Discussion at https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001179.h… Please create entries for this Change in the Release Notes. -- You are receiving this mail because: You are the QA Contact for the bug.

1 2

[Bug 977042] New: GUI examples presume GNOME without stating it is GNOME
by Red Hat Bugzilla 15 Jul '16

15 Jul '16

https://bugzilla.redhat.com/show_bug.cgi?id=977042 Bug ID: 977042 Summary: GUI examples presume GNOME without stating it is GNOME Product: Fedora Documentation Version: devel Component: system-administrator's-guide Severity: unspecified Priority: unspecified Assignee: jhradile(a)redhat.com Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: jhradile(a)redhat.com The System Administrator's Guide references a number of GUI utilities, many of which are specific to GNOME. It isn't immediately obvious to the uninitiated that this is the case, causing non-GNOME users to find fault with the guide. I suggest an admonition in the preface along the lines of "Some of the graphical procedures and menu locations are specific to GNOME, but most command line instructions will be universally applicable" Comprehensively differentiating between GNOME procedures, procedures for other DEs, and universal procedures would probably be prohibitively time consuming. --Pete -- You are receiving this mail because: You are the QA Contact for the bug.

1 7

[Bug 997219] New: No "Write to Disk" option for ISO images in Fedora 19
by Red Hat Bugzilla 15 Jul '16

15 Jul '16

https://bugzilla.redhat.com/show_bug.cgi?id=997219 Bug ID: 997219 Summary: No "Write to Disk" option for ISO images in Fedora 19 Product: Fedora Documentation Version: devel Component: readme-burning-isos Assignee: oglesbyzm(a)gmail.com Reporter: sirjake(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: oglesbyzm(a)gmail.com, stickster(a)gmail.com Description of problem: Guide says that you can right click on a ISO image and choose "Write to disc." This is not true, at least with Fedora 19. Version-Release number of selected component (if applicable): 19 How reproducible: Always, at least in 32 bit. Steps to Reproduce: 1. http://docs.fedoraproject.org/en-US/Fedora/19/html/Burning_ISO_images_to_di… 2. Insert a DVD. 3. Attempt to follow the directions above. No "Write to disk" option exists. Actual results: No obvious way to burn ISO images in Fedora Linux 19. Expected results: Directions to burn ISO disk in Fedora Linux 19 Additional info: I had a new-to-me computer that I assumed would not support 64 bit, but after installing 32 bit found out that 64 was supported by my processor. I downloaded 64 ( Fedora-Live-Desktop-x86_64-19-1.iso ), and wanted to burn a disk of it, but the option was not available and the directions online did not help. I had to go back to Windows on a different machine to burn it. Note: I do have a DVD burner on this machine. The same thing occurs with CD's in the burner. -- You are receiving this mail because: You are the QA Contact for the bug.

1 3

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

docs-qa October 2015