June 2013 - docs-qa - Fedora Mailing-Lists

by Red Hat Bugzilla

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.

6 years, 2 months

2
3
0 / 0

[Bug 842190] New: Cpufreq governor

by Red Hat Bugzilla

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.

6 years, 2 months

2
4
0 / 0

[Bug 832179] New: Power management guide is wrong for frequency scaling in Fedora 17

by Red Hat Bugzilla

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_Guid... 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.

6 years, 2 months

2
8
0 / 0

[Bug 915751] New: Remove BuildArch: noarch from the meta package example

by Red Hat Bugzilla

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/ht... (Changed in scl-utils-20121110.) -- You are receiving this mail because: You are the QA Contact for the bug.

6 years, 4 months

2
1
0 / 0

[Bug 769438] New: [PATCH] Fix syntax of code examples within rpm-guide-programming-python.xml

by Red Hat Bugzilla

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.

6 years, 4 months

2
5
0 / 0

[Bug 959626] New: config_name mismatch in mock example

by Red Hat Bugzilla

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

6 years, 4 months

2
1
0 / 0

[Bug 977042] New: GUI examples presume GNOME without stating it is GNOME

by Red Hat Bugzilla

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.

7 years, 9 months

1
7
0 / 0

[Bug 948823] New: Need a search solution for docs.fedoraproject.org

by Red Hat Bugzilla

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.

7 years, 10 months

1
7
0 / 0

[Bug 979158] New: Windows Virtio Drivers version 1-59 blue screens windows when you hot add virtio drives

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=979158 Bug ID: 979158 Summary: Windows Virtio Drivers version 1-59 blue screens windows when you hot add virtio drives Product: Fedora Documentation Version: devel Component: virtualization-deployment-guide Severity: high Priority: unspecified Assignee: lbailey(a)redhat.com Reporter: robert.rupert(a)servicemesh.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: lbailey(a)redhat.com Description of problem: Windows Blue Screens in KVM when using the latest virtio driver 1-59. When hot adding scsi drive Version-Release number of selected component (if applicable): How reproducible: fresh install with virtio scsi driver 1-59,=. Then hot add virtio scsi driver in windows 7, 2008r2 and 2012 Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: using the previose version 1-52 works fine -- You are receiving this mail because: You are the QA Contact for the bug.

8 years, 6 months

1
2
0 / 0

[Bug 846864] New: Need a list of toolsets and when they are appropriate in the virt Getting Started guide

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=846864 Bug ID: 846864 QA Contact: docs-qa(a)lists.fedoraproject.org Severity: unspecified Version: devel Priority: unspecified CC: docs(a)lists.fedoraproject.org Assignee: laine(a)redhat.com Summary: Need a list of toolsets and when they are appropriate in the virt Getting Started guide Regression: --- Story Points: --- Classification: Fedora OS: Unspecified Reporter: laine(a)redhat.com Type: Bug Documentation: --- Hardware: Unspecified Mount Type: --- Status: NEW Component: virtualization-getting-started-guide Product: Fedora Documentation The Getting Started Guide needs an overview of all the different toolsets, and when each would be appropriate. In particular I'm talking about the following: 1) gnome-boxes 2) virt-manager 3) virsh, virt-install 4) ovirt 5) Should we point some people to OpenStack? I will write up a first draft of this, and hand it to a qualified docs person to edit and correctly place in the guide. -- You are receiving this mail because: You are the QA Contact for the bug.

8 years, 10 months

1
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

docs-qa June 2013