[Bug 1080006] New: Incorrect command for multi-core power saving
by Red Hat Bugzilla
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_Guid...],
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.
6 years, 3 months
[Bug 994167] New: typo in servicectl enable command
by Red Hat Bugzilla
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.
6 years, 3 months
[Bug 973950] New: Type in Chapter 1.2
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, 3 months
[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, 3 months
[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, 3 months
[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
[Bug 1253462] New: Error in http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch16s03s05.html
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1253462
Bug ID: 1253462
Summary: Error in
http://docs.fedoraproject.org/en-US/Fedora_Draft_Docum
entation/0.1/html/RPM_Guide/ch16s03s05.html
Product: Fedora Documentation
Version: devel
Component: rpm-guide
Severity: low
Assignee: bcotton+fedora(a)gmail.com
Reporter: nbasanes(a)cisco.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: bcotton+fedora(a)gmail.com, pkovar(a)redhat.com,
zach(a)oglesby.co
Created attachment 1062752
--> https://bugzilla.redhat.com/attachment.cgi?id=1062752&action=edit
This attachment is a screenshot of a more readable result.
Description of problem:
The Python code section at
http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/R...
has an error in the following code:
# Dependencies
print "Provides:"
print h.dsFromHeader('providename')
print "Requires:"
print h.dsFromHeader('requirename')
if h.dsFromHeader('obsoletename'):
print "Obsoletes:"
print h.dsFromHeader('obsoletename')
if h.dsFromHeader('conflictname'):
print "Conflicts:"
print h.dsFromHeader('conflictname')
print h.dsFromHeader('conflictname') outputs <rpm.ds object at 0xb77584b8>.
h.dsFromHeader('conflictname'), without the "print" word, outputs it right.
Version-Release number of selected component (if applicable):
0.1
How reproducible:
Steps to Reproduce:
1. Copy the python code from the page to a file called rpminfo.py on a computer
that has the older version of Python, Python 2.
2. Run the Python code, by running the "cd" command until you get to the folder
that contains rpminfo.py.
3. Run rpminfo.py by entering the command python rpminfo.py.
Actual results:
Provides:
<rpm.ds object at 0xb77584b8>
Requires:
<rpm.ds object at 0xb77584b8>
Expected results:
Provides:
P config(httpd) = 2.2.15-39.el6.centos
Requires:
R libapr-1.so.0
Additional info:
The members of the object returned by dsFromHeader have integer indexes, since
the following code produces a more readable result:
# Dependencies
print "Provides:"
print h.dsFromHeader('providename')[0]
print "Requires:"
print h.dsFromHeader('requirename')[0]
--
You are receiving this mail because:
You are the QA Contact for the bug.
6 years, 4 months