docs-qa February 2019

docs-qa@lists.fedoraproject.org

1 participants
15 discussions

[Bug 1662306] New: TigerVNC Configuration Page out of date
by bugzilla＠redhat.com 21 May '24

21 May '24

https://bugzilla.redhat.com/show_bug.cgi?id=1662306 Bug ID: 1662306 Summary: TigerVNC Configuration Page out of date Product: Fedora Documentation Version: devel Hardware: x86_64 OS: Linux Status: NEW Component: system-administrator's-guide Severity: medium Assignee: pbokoc(a)redhat.com Reporter: colin.henry(a)gmail.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: swadeley(a)redhat.com Target Milestone: --- Classification: Fedora Description of problem: Documentation does not reflect current file configuration Version-Release number of selected component (if applicable): Fedora 29 How reproducible: Try and follow the instructions on the configuration page, it tells you to change settings that aren't there. For instance, users are told to edit the and change: ExecStart=/sbin/runuser -l USER -c "/usr/bin/vncserver %i -geometry 1280x1024" PIDFile=/home/USER/.vnc/%H%i.pid Whereas the actual file contains: ExecStart=/usr/bin/vncserver -autokill %i PIDFile=/home/<USER>/.vnc/%H%i.pid Steps to Reproduce: 1. Go to the documentation page: https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide… 2. Install tigervnc-server 3. Look at the configuration file /lib/systemd/system/vncserver@.service Actual results: The files differ significantly, also following the instructions in the configuration file fails to start vnc successfully, but I'll file a bug for that separately. Expected results: Configuration documentation should match the files on the host Additional info: -- You are receiving this mail because: You are the QA Contact for the bug.

1 1

[Bug 1162045] Power Mgmt Guide needs to Address Howto Suppress Sleep State
by bugzilla＠redhat.com 28 Feb '19

28 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1162045 PnT Account Manager <pnt-expunge(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|amelicha(a)redhat.com |pbokoc(a)redhat.com -- You are receiving this mail because: You are the QA Contact for the bug.

1 0

[Bug 1080006] Incorrect command for multi-core power saving
by bugzilla＠redhat.com 28 Feb '19

28 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1080006 PnT Account Manager <pnt-expunge(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|amelicha(a)redhat.com |pbokoc(a)redhat.com -- You are receiving this mail because: You are the QA Contact for the bug.

1 0

[Bug 1036886] Incorrect command to start tuned at boot in Power Management Guide
by bugzilla＠redhat.com 28 Feb '19

28 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1036886 PnT Account Manager <pnt-expunge(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|amelicha(a)redhat.com |pbokoc(a)redhat.com -- You are receiving this mail because: You are the QA Contact for the bug.

1 0

[Bug 1008872] CPUfreq documentation for F19 lacks information on the new intel_pstate driver and its governors
by bugzilla＠redhat.com 28 Feb '19

28 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1008872 PnT Account Manager <pnt-expunge(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|amelicha(a)redhat.com |pbokoc(a)redhat.com -- You are receiving this mail because: You are the QA Contact for the bug.

1 0

[Bug 994167] typo in servicectl enable command
by bugzilla＠redhat.com 28 Feb '19

28 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=994167 PnT Account Manager <pnt-expunge(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|amelicha(a)redhat.com |pbokoc(a)redhat.com -- You are receiving this mail because: You are the QA Contact for the bug.

1 0

[Bug 973950] Type in Chapter 1.2
by bugzilla＠redhat.com 28 Feb '19

28 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=973950 PnT Account Manager <pnt-expunge(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|amelicha(a)redhat.com |pbokoc(a)redhat.com -- You are receiving this mail because: You are the QA Contact for the bug.

1 0

[Bug 842190] CPUfreq governor
by bugzilla＠redhat.com 28 Feb '19

28 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=842190 PnT Account Manager <pnt-expunge(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|amelicha(a)redhat.com |pbokoc(a)redhat.com -- You are receiving this mail because: You are the QA Contact for the bug.

1 0

[Bug 832179] Power management guide is wrong for frequency scaling in Fedora 17
by bugzilla＠redhat.com 28 Feb '19

28 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=832179 PnT Account Manager <pnt-expunge(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|amelicha(a)redhat.com |pbokoc(a)redhat.com -- You are receiving this mail because: You are the QA Contact for the bug.

1 0

[Bug 1683125] New: no clear way how to report a problem at docs.fedoraproject.org
by bugzilla＠redhat.com 27 Feb '19

27 Feb '19

https://bugzilla.redhat.com/show_bug.cgi?id=1683125 Bug ID: 1683125 Summary: no clear way how to report a problem at docs.fedoraproject.org Product: Fedora Documentation Version: devel Status: NEW Component: docs-requests Assignee: pbokoc(a)redhat.com Reporter: kparal(a)redhat.com QA Contact: docs-qa(a)lists.fedoraproject.org CC: nobody(a)fedoraproject.org, sparks(a)redhat.com, stickster(a)gmail.com, zach(a)oglesby.co Target Milestone: --- Classification: Fedora I found a broken link in https://docs.fedoraproject.org/en-US/packaging-guidelines/ . I wanted to report that, but... I have no idea where! The page doesn't contain any indication whatsoever (in a header/footer) where to report such issues. That is a big problem, because we'll never know about docs failures if we don't tell users where to report them. I then went to https://docs.fedoraproject.org/en-US/docs/ and it's the same story. Again, no contact, no tracker link, nothing. I found this bugzilla entry and I hope somebody will notice this report, but even here, I couldn't find a component that would be "general issues for docs.fp.o". Please fix this. Provide a clear link for reporting issues/contact on every page that is displayed at docs.fp.o (in a header/footer). Make sure the homepage has relevant info as well. It is critical for keeping our docs usable. Thank you! -- You are receiving this mail because: You are the QA Contact for the bug.

1 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

docs-qa February 2019