June 2015 - 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 1162045] New: Power Mgmt Guide needs to Address Howto Suppress Sleep State
by Red Hat Bugzilla 29 Jan '18

29 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 29 Jan '18

29 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 29 Jan '18

29 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 29 Jan '18

29 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 29 Jan '18

29 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 29 Jan '18

29 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

[Bug 842190] New: Cpufreq governor
by Red Hat Bugzilla 29 Jan '18

29 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=842190 Bug ID: 842190 QA Contact: docs-qa(a)lists.fedoraproject.org Severity: unspecified Version: devel Priority: unspecified CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com Assignee: r.landmann(a)redhat.com Summary: Cpufreq governor Regression: --- Story Points: --- Classification: Fedora OS: Unspecified Reporter: h479627(a)rtrtr.com Type: Bug Documentation: --- Hardware: Unspecified Mount Type: --- Status: NEW Component: power-management-guide Product: Fedora Documentation Description of problem: Version-Release number of selected component (if applicable): 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 4

[Bug 832179] New: Power management guide is wrong for frequency scaling in Fedora 17
by Red Hat Bugzilla 29 Jan '18

29 Jan '18

https://bugzilla.redhat.com/show_bug.cgi?id=832179 Bug ID: 832179 QA Contact: docs-qa(a)lists.fedoraproject.org Severity: medium Version: devel Priority: unspecified CC: ddomingo(a)redhat.com, oglesbyzm(a)gmail.com Assignee: r.landmann(a)redhat.com Summary: Power management guide is wrong for frequency scaling in Fedora 17 Regression: --- Story Points: --- Classification: Fedora OS: Linux Reporter: jnm11(a)cam.ac.uk Type: Bug Documentation: --- Hardware: All Mount Type: --- Status: NEW Component: power-management-guide Product: Fedora Documentation Description of problem: Power management guide is wrong https://docs.fedoraproject.org/en-US/Fedora/17/html/Power_Management_Guide/… Version-Release number of selected component (if applicable): Fedora 17 the location of the cpufreq directory is misspecified it is /lib/modules/3.4.0-1.fc17.x86_64/kernel/drivers/cpufreq There are no modules acpi-cpufreq or p4-clockmod available is acpi-cpufreq directly compiled in. the cpuspeed package is mentioned for the userspace governor but no package exists in fedora 17. I have been completely unable to figure out the following use case. My laptop overheats and powers off if the cpu load is high for too long. There should be a cpu governor or userspace daemon that reduces frequency when the temperature gets too high. -- You are receiving this mail because: You are the QA Contact for the bug.

2 8

[Bug 915751] New: Remove BuildArch: noarch from the meta package example
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

Product: Fedora Documentation https://bugzilla.redhat.com/show_bug.cgi?id=915751 Bug ID: 915751 Summary: Remove BuildArch: noarch from the meta package example Product: Fedora Documentation Version: devel Component: software-collections-guide Severity: high Priority: high Reporter: pkovar(a)redhat.com Remove BuildArch: noarch from the meta package example in: http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html… (Changed in scl-utils-20121110.) -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 769438] New: [PATCH] Fix syntax of code examples within rpm-guide-programming-python.xml
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: [PATCH] Fix syntax of code examples within rpm-guide-programming-python.xml https://bugzilla.redhat.com/show_bug.cgi?id=769438 Summary: [PATCH] Fix syntax of code examples within rpm-guide-programming-python.xml Product: Fedora Documentation Version: devel Platform: Unspecified OS/Version: Unspecified Status: NEW Severity: unspecified Priority: unspecified Component: rpm-guide AssignedTo: bcotton+fedora(a)gmail.com ReportedBy: dmalcolm(a)redhat.com QAContact: docs-qa(a)lists.fedoraproject.org CC: oglesbyzm(a)gmail.com, pkovar(a)redhat.com Classification: Fedora Story Points: --- Type: --- Regression: --- Mount Type: --- Documentation: --- Created attachment 548940 --> https://bugzilla.redhat.com/attachment.cgi?id=548940 Patch to Rpm Guide to fix rpm-guide-programming-python.xml Unfortunately the examples of Python code within the RPM guide have been thoroughly broken since the initial conversion to DocBook, due to the way Python treats leading whitespace as significant. I'm attaching a patch which overhauls this page, so that the code examples are syntactically valid. See the notes in the patch -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

2 5

[Bug 1163568] New: POSIX capabilities "%caps" macro not mentioned anyhwere
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1163568 Bug ID: 1163568 Summary: POSIX capabilities "%caps" macro not mentioned anyhwere Product: Fedora Documentation Version: devel Component: rpm-guide Severity: medium Assignee: bcotton+fedora(a)gmail.com Reporter: matt(a)nightrealms.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com, zach(a)oglesby.co The RPM guide doesn't mention the "%caps" macro which can be used to set a file's POSIX capabilities (see http://linux.die.net/man/7/capabilities). It should go in chapter 9, section 5.4, at URL http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM… -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 1115469] New: Link to full documentation is incorrect
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1115469 Bug ID: 1115469 Summary: Link to full documentation is incorrect Product: Fedora Documentation Version: devel Component: rpm-guide Assignee: bcotton+fedora(a)gmail.com Reporter: msuchy(a)redhat.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com, zach(a)oglesby.co Description of problem: This page: http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM… links to /usr/share/doc/rpm-devel-4.1/apidocs/html/group__python.html Which does not exist on recent Fedoras. RPM API is documented at: /usr/share/doc/rpm-apidocs/index.html And I did not find documentation for rpm-python itself. -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 1025475] New: typo in yum update for kexi-mysql
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1025475 Bug ID: 1025475 Summary: typo in yum update for kexi-mysql Product: Fedora Documentation Version: devel Component: rpm-guide Assignee: bcotton+fedora(a)gmail.com Reporter: admin(a)velusuniverse.co.uk QA Contact: docs-qa(a)lists.fedoraproject.org CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com, zach(a)oglesby.co Description of problem: calligra-kexi-driver-mysql summary says mysqwl driver for kexi but shouldnt it say mysql driver for kexi ?? Version-Release number of selected component (if applicable): How reproducible: use the yum extender andd look up calligra-kexi-driver-mysql Steps to Reproduce: 1. 2. 3. Actual results: ummary says mysqwl driver for kexi Expected results: mysql driver for kexi Additional info: -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 1017792] New: %verify doesn't know symlink, maj min
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1017792 Bug ID: 1017792 Summary: %verify doesn't know symlink, maj min Product: Fedora Documentation Version: devel Component: rpm-guide Assignee: bcotton+fedora(a)gmail.com Reporter: jskarvad(a)redhat.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com, zach(a)oglesby.co Description of problem: In the "Verifying the %files section" chapter of the RPM guide [1], there is written "symlink", but it seems RPM uses "link" instead. Also I had trouble with the "maj" and "min", I guess there is "rdev" used instead. Version-Release number of selected component (if applicable): 0.1 How reproducible: Always Steps to Reproduce: 1. See the "Verifying the %files section" chapter Actual results: There are symlink, maj and min Expected results: The link and probably rdev Additional info: [1] http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM… -- You are receiving this mail because: You are the QA Contact for the bug.

2 2

[Bug 1003962] New: RPM scriptlet -p option not documented
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1003962 Bug ID: 1003962 Summary: RPM scriptlet -p option not documented Product: Fedora Documentation Version: devel Component: rpm-guide Assignee: bcotton+fedora(a)gmail.com Reporter: daniel.neuberger(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com, zach(a)oglesby.co The fedora RPM guide does not document the -p option that can be passed to the RPM scriptlets. It should probably be located here http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM…, but I looked through the entire guide and couldn't find it. The only only place I could find it documented is here https://fedoraproject.org/wiki/Packaging:ScriptletSnippets, but what it says is wrong. It says: "The basic syntax is similar to the %build, %install, and other sections of the rpm spec file. The scripts support a special flag, -p which allows the scriptlet to invoke a single program directly rather than having to spawn a shell to invoke the programs. (ie: %post -p /sbin/ldconfig)" A more accurate description is: "The basic syntax is similar to the %build, %install, and other sections of the rpm spec file. The scripts support a special flag, -p which specifies the interPreter that should be used to run the script (the default is /bin/sh). Sometimes the -p option is used with no body in order to run a single command directly rather than having to spawn a shell to invoke the programs (i.e. %post -p /sbin/ldconfig). Note that this form requires that there be nothing but white space (not even comments) until the next section begins." -- You are receiving this mail because: You are the QA Contact for the bug.

2 7

[Bug 1057882] New: Fedora - Installation Quick Start Guide - An update of the Czech translation ready
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1057882 Bug ID: 1057882 Summary: Fedora - Installation Quick Start Guide - An update of the Czech translation ready Product: Fedora Documentation Version: devel Component: publishing-requests Assignee: docs-publishers-members(a)fedoraproject.org Reporter: josef.hruska(a)upcmail.cz QA Contact: docs-qa(a)lists.fedoraproject.org CC: docs-publishers-members(a)fedoraproject.org Description of problem: Please publish an updated Czech version of the F20 Installation Quick Start Guide Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Mostly grammar errors found in current version. Expected results: An updated Czech translation published - missing translation(s) added, translation revision and precision. Additional info: If the bug BZ#1056196 is a serious obstacle, publish this update once the bug is resolved. -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 1050903] New: Fedora - burning ISO images to disc - Updated Czech translation
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=1050903 Bug ID: 1050903 Summary: Fedora - burning ISO images to disc - Updated Czech translation Product: Fedora Documentation Version: devel Component: publishing-requests Assignee: docs-publishers-members(a)fedoraproject.org Reporter: josef.hruska(a)upcmail.cz QA Contact: docs-qa(a)lists.fedoraproject.org CC: docs-publishers-members(a)fedoraproject.org Description of problem: Please publish an update of the Czech translation of Burning ISO images to disc guide Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Translation update - missing translation, revision and precision. Additional info: -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 985020] New: explain types of rpm packages (what are they for)
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

https://bugzilla.redhat.com/show_bug.cgi?id=985020 Bug ID: 985020 Summary: explain types of rpm packages (what are they for) Product: Fedora Documentation Version: devel Component: packager-guide Severity: unspecified Priority: unspecified Assignee: pkovar(a)redhat.com Reporter: bvoperdf21(a)mt2014.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: pkovar(a)redhat.com Description of problem: First I'd like to thank for the awesome documentaions available. Also +1 for the export function (PDF,html-single,...). Looking at the packagers guide I missed some information. It would be nice if you also tell what kind of rpm packages are out there. What I found so far: .rpm .src.rpm .debugsource.... .debuginfo.... For example I still don't know if the debugsource is needed when using gdb for debugging or if the debuginfo package is enough. Version-Release number of selected component (if applicable):Edition 18.0.1 How reproducible: Steps to Reproduce: 1.go to http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Pac… 2.read everything Actual results: no description of the defferent types of rpm packages Expected results: find description of the defferent types of rpm packages and what they are used for/by. Additional info: would be nice to have this -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 959626] New: config_name mismatch in mock example
by Red Hat Bugzilla 14 Dec '17

14 Dec '17

Product: Fedora Documentation https://bugzilla.redhat.com/show_bug.cgi?id=959626 Bug ID: 959626 Summary: config_name mismatch in mock example Product: Fedora Documentation Version: devel Component: packager-guide Severity: low Priority: unspecified Assignee: pkovar(a)redhat.com Reporter: axilleas(a)archlinux.gr QA Contact: docs-qa(a)lists.fedoraproject.org CC: fnadge(a)redhat.com Category: --- Description of problem: In section 2.4.3. Testing a Package with Mock, the last example uses the epel-6-x86_64 config whereas Fedora 18 is referenced above. According to the preamble, the example should read: mock -r fedora-18-x86_64 ~/rpmbuild/SRPMS/eject-2.1.5-0.1.fc18.src.rpm Link: https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Pa… -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 1198984] New: firewalld: please improve documentation on using it on a RedHat/Fedora/CentOS router
by Red Hat Bugzilla 01 Sep '17

01 Sep '17

https://bugzilla.redhat.com/show_bug.cgi?id=1198984 Bug ID: 1198984 Summary: firewalld: please improve documentation on using it on a RedHat/Fedora/CentOS router Product: Fedora Documentation Version: devel Component: cookbook Assignee: docs(a)lists.fedoraproject.org Reporter: razvan.sandu(a)mobexpert.ro QA Contact: docs-qa(a)lists.fedoraproject.org CC: docs(a)lists.fedoraproject.org Hello, Description of problem: Even using the rich-language feature, it is still rather difficult to figure out how to use firewalld on a RedHat/Fedora/CentOS system that is used as a router (a "transparent" system). That's because: a. administrators will need *different* sets of rules/restrictions for access to the router itself and to the various services that run beyond the router (using or non using NAT). b. It is not very clear how/where the predefined firewalld zones implement their policies (ACCEPT or DROP) and when these policies apply to traffic bounded *to* the router system or to traffic that *traverses* the router. For example, an administrator needs an *easy* method to restrict VNC access *to* the router itself (INPUT), but may want free VNC access to some server located *behind* the router (FORWARD). In the second case, forwarding may (or may not) imply NAT, depending if he goes on the Internet via the external interface or simply goes in another LAN segment beyond the router. c. It is not very clear how/where the predefined firewalld zones implement their trafic rules ( *exceptions* to ACCEPT or DROP default policies) and when these rules apply to traffic bounded *to* the router system or to traffic that *traverses* the router. Additional info: Even it is not dynamic, the Shorewall application (http://shorewall.net/) acts as a higher-level language over iptables, offering the same concepts of "zones" for interfaces. Much of its conceptual architecture is directly applicable ("portable") to firewalld, if accepted by developers. Somewhat different from conceptual point of view, the "zones" are "levels of trust surrounding the router", including thr FW zone for the router itself. (unlike firewalld, the shorewall zones have no "sources" or "services" embedded in them). IPv4 and IPv6 zones are completely separated (they actually represent different levels of trust). Administrators may directly define policies, i.e. allow *default* actions to be done when an packet travels from a zone to another (ACCEPT, REJECT). The most sane policy between any two zones is REJECT (with further exceptions defined as rules, see below). Rules are *exceptions to policies* , explicitly defined (based on various criteria such as source IP, destination IP, ports, etc.) Rules may be expressed via predefined (or customised) "macros" (which are the direct equivalent of firewalld's "services"). IPv4 and IPv6 policy and rules are completely separated (IMHO that's good, since the use of global IPv6 addresses pose completely different security problems than NATted & externally firewalled IPv4). Best regards, Răzvan -- You are receiving this mail because: You are the QA Contact for the bug.

2 2

[Bug 1008227] New: SSD cache
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=1008227 Bug ID: 1008227 Summary: SSD cache 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: agk(a)redhat.com, i.gnatenko.brain(a)gmail.com, jeremy(a)goop.org, jreznik(a)redhat.com, kzak(a)redhat.com, nobody(a)fedoraproject.org, rdieter(a)math.unl.edu, rolf(a)rolffokkens.nl, sparks(a)redhat.com, stickster(a)gmail.com, zach(a)oglesby.co Depends On: 998543, 999690, 1000817, 1001120, 1003208, 1000078, 1003207 +++ This bug was initially created as a clone of Bug #998543 +++ This is a tracking bug for Change: SSD cache For more details, see: http://fedoraproject.org//wiki/Changes/SSD_cache Using recent kernel (3.9 and later) features for (fast) SSD caching of (slow) ordinary hard disks. --- Additional comment from Rolf Fokkens on 2013-08-21 13:35:33 EDT --- I'll build a bcache-tools RPM and a dm-cache-utils rpm (actually bcache-tools is already available here: bcache-tools-20130820-0.1.fc19.src.rpm). I'll follow the procedure as described here: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers --- Additional comment from Rolf Fokkens on 2013-08-24 11:51:34 EDT --- Tried to create a dmcache-utils package as well (Bug 1000078) but it doesn't look really useful. So I'll focus on bcache-tools first. For that I still need a sponsor. --- Additional comment from Rolf Fokkens on 2013-08-27 06:52:40 EDT --- I closed Bug 1000078 since good userland support requires LVM2 to support dm-cache. Which will happen 'in the future', but F20 doesn't look feasible to me. --- Additional comment from Rolf Fokkens on 2013-08-31 16:21:30 EDT --- Create Bug 1003207 (bcache support for dracut) which is not blocking for F20, but probably will be blocking for F21. --- Additional comment from Rolf Fokkens on 2013-08-31 16:25:06 EDT --- Create Bug 1003208 (bcache support for anaconda) which is not blocking for F20, but probably will be blocking for F21. --- Additional comment from Rolf Fokkens on 2013-09-09 04:18:18 EDT --- Test day planned: https://fedorahosted.org/fedora-qa/ticket/415 -------------------------------------------------------------- Discussion at https://lists.fedoraproject.org/pipermail/devel/2013-July/185336.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 6

[Bug 1058066] New: new virt-xml functionality coming from upstream libvirt should be documented
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=1058066 Bug ID: 1058066 Summary: new virt-xml functionality coming from upstream libvirt should be documented Product: Fedora Documentation Version: devel Component: virtualization-deployment-and-administrative-guide Assignee: lnovich(a)redhat.com Reporter: me(a)petetravis.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: lnovich(a)redhat.com There is a new tool called `virt-xml` that will end up in Fedora soon[1]. It looks very useful, and should be documented. [1] https://www.redhat.com/archives/libvir-list/2014-January/msg01226.html -- You are receiving this mail because: You are the QA Contact for the bug.

2 2

[Bug 980931] New: The Virtualization Administration Guide Still Uses UNIX System V Commands
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=980931 Bug ID: 980931 Summary: The Virtualization Administration Guide Still Uses UNIX System V Commands Product: Fedora Documentation Version: devel Component: virtualization-administration-guide Keywords: Documentation Severity: medium Priority: unspecified Assignee: lnovich(a)redhat.com Reporter: jhradile(a)redhat.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: lnovich(a)redhat.com, me(a)petetravis.com Description of problem: The Virtualization Administration Guide for Fedora 18 [1] still uses UNIX System V commands “service” and “chkconfig”. Although these commands still work and will continue to work in the foreseeable future, users are strongly advised to learn and use the new command that is shipped with systemd and is part of the Fedora distribution since version 15. Version-Release number of selected component (if applicable): Fedora-Virtualization_Administration_Guide-18-en-US-1.0-1 How reproducible: Always. Steps to Reproduce: Read section 14.3, “Starting and stopping the daemon” [2], to learn how to configure the vhostmd service to start automatically at boot time. Actual results: /sbin/chkconfig vhostmd on Expected results: systemctl enable vhostmd.service Additional info: http://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet ----- [1] http://docs.fedoraproject.org/en-US/Fedora/18/html-single/Virtualization_Ad… [2] http://docs.fedoraproject.org/en-US/Fedora/18/html-single/Virtualization_Ad… -- You are receiving this mail because: You are the QA Contact for the bug.

2 2

[Bug 1095977] New: RFE: static IP assignment
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=1095977 Bug ID: 1095977 Summary: RFE: static IP assignment 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 Static IP addresses are crucial for applications like DHCP servers or other infrastructure that can't rely on external assignment. They're also helpful for home users that want to predictably locate their Fedora installation. Explain the use case for this and some alternative methods, then the procedure for setting a setting a static IP using both ifcfg files and graphical methods. Each method could be explained in a separate article; ie "... on the command line" and "... with GNOME" and "... with KDE" and so on. -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 1101798] New: RFE: Captive portal
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=1101798 Bug ID: 1101798 Summary: RFE: Captive portal 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 Create a recipe for configuring a simple captive portal with Fedora that will require users to acknowledge a terms of use message before allowing connections to pass. -- You are receiving this mail because: You are the QA Contact for the bug.

2 1

[Bug 1101796] New: RFE: NAT router
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=1101796 Bug ID: 1101796 Summary: RFE: NAT router 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 Create a recipe for using Fedora as a NAT router using Firewalld and NetworkManager. -- You are receiving this mail because: You are the QA Contact for the bug.

2 2

[Bug 1096394] New: RFE: Thin Client (Tracking Bug)
by Red Hat Bugzilla 31 Aug '17

31 Aug '17

https://bugzilla.redhat.com/show_bug.cgi?id=1096394 Bug ID: 1096394 Summary: RFE: Thin Client (Tracking Bug) 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 Fedora can be used as a server and client environment for a thin client deployment. Document the required procedures to do this. Because of the broad scope and number of procedures involved, this should be split up into recipes addressing component tasks. This bug will be used to track the overall progress; please block this bug with any new bugs created for the purpose. -- You are receiving this mail because: You are the QA Contact for the bug.

2 2

[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 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 14 Jul '16

14 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

[Bug 948823] New: Need a search solution for docs.fedoraproject.org
by Red Hat Bugzilla 10 Jun '16

10 Jun '16

Product: Fedora Documentation https://bugzilla.redhat.com/show_bug.cgi?id=948823 Bug ID: 948823 Summary: Need a search solution for docs.fedoraproject.org Product: Fedora Documentation Version: devel Component: project-tracking Severity: unspecified Priority: unspecified Assignee: nobody(a)fedoraproject.org Reporter: sparks(a)redhat.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: oglesbyzm(a)gmail.com, sparks(a)redhat.com, stickster(a)gmail.com Category: --- Description of problem: Due to the removal of Google search feature (see bug 616876) we no longer have a search solution for docs.fp.o. We need to investigate an alternate solution and bring the search feature back. -- You are receiving this mail because: You are the QA Contact for the bug.

1 7

[Bug 1220066] New: grub2-install suggestion doesn't distinguish between BIOS and UEFI installs
by Red Hat Bugzilla 09 Jun '16

09 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=1220066 Bug ID: 1220066 Summary: grub2-install suggestion doesn't distinguish between BIOS and UEFI installs Product: Fedora Documentation Version: devel Component: system-administrator's-guide Assignee: swadeley(a)redhat.com Reporter: bugzilla(a)colorremedies.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: swadeley(a)redhat.com ttps://docs.fedoraproject.org/en-US/Fedora/21/html/System_Administrators_Gu… Section 20.4 and 20.4.1 apply only to BIOS computers, not UEFI. On UEFI: 1. grub2-install fails https://bugzilla.redhat.com/show_bug.cgi?id=1101352 2. If grub2-efi-modules is installed, grub2-install succeeds but then: 2a. This will break UEFI Secure Boot systems because the core.img/grubx64.efi binary that gets created isn't signed and therefore UEFI Secure Boot will reject it. 2b. On UEFI systems without Secure Boot, GRUB behavior is different in a number of ways including that it will no longer look to /boot/efi/EFI/fedora/grub.cfg but rather to /boot/grub2/grub.cfg. Two ways to fix the documentation: a.) A side bar that says this section doesn't apply to systems with UEFI firmware (maybe a link to where we give them a hint "how to find out what kind of firmware you have"), and/or that this section is effectively done by 20.4.2 step 3. b.) Reorganize 20.4 into discreet BIOS and UEFI sections. -- You are receiving this mail because: You are the QA Contact for the bug.

1 18

[Bug 1002573] New: Enable SELinux Labeled NFS Support
by Red Hat Bugzilla 07 Jun '16

07 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=1002573 Bug ID: 1002573 Summary: Enable SELinux Labeled NFS Support Product: Fedora Documentation Version: devel Component: security-guide Keywords: Tracking Assignee: sparks(a)redhat.com Reporter: sparks(a)redhat.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: jreznik(a)redhat.com, me(a)petetravis.com, nobody(a)fedoraproject.org, pkennedy(a)redhat.com, security-guide-list(a)redhat.com, sparks(a)redhat.com, steved(a)redhat.com, stickster(a)gmail.com, zach(a)oglesby.co Depends On: 984718, 998566, 1001346 +++ This bug was initially created as a clone of Bug #1001346 +++ +++ This bug was initially created as a clone of Bug #998566 +++ This is a tracking bug for Change: Enable SELinux Labeled NFS Support For more details, see: http://fedoraproject.org//wiki/Changes/LabeledNFS The Linux Kernel has grown support for passing SELinux labels between a client and server using NFS. Discussion at https://lists.fedoraproject.org/pipermail/devel-announce/2013-July/001216.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 4

[Bug 982914] New: 7.4.1. Configuring 802.1x Security
by Red Hat Bugzilla 07 Jun '16

07 Jun '16

https://bugzilla.redhat.com/show_bug.cgi?id=982914 Bug ID: 982914 Summary: 7.4.1. Configuring 802.1x Security 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.4.1 under 'Procedure 7.8. For a wired connection...', ' Procedure 7.9. For a wireless connection...': The 'Network Connections' dialogue can be accessed via: activities --> applications --> sundry --> network connections, or via nm-connection-editor This is not specified at all in this section. -- You are receiving this mail because: You are the QA Contact for the bug.

1 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

docs-qa June 2015